LBRYCommunity/lbry.tech
1
0
Fork 0
Code Issues 13 Pull requests 8 Projects Releases Packages Wiki Activity

Update consensus.md #213

Merged
AdamZWinter merged 2 commits from patch-1 into master 2019-01-17 14:43:37 +01:00
Conversation 4 Commits 2 Files changed 1 +2 -6
AdamZWinter commented 2019-01-12 20:48:33 +01:00 (Migrated from github.com)
Copy link
No description provided.
tzarebczan commented 2019-01-14 17:59:51 +01:00 (Migrated from github.com)
Copy link

Thanks for this PR @AdamZWinter . @lyoshenka / @kauffj will be beefing up some of the docs on lbry.tech this week, so I'll let them review to see if anything else needs to be added here (though it does look like it talks about both the targeting + difficulty).

Thanks for this PR @AdamZWinter . @lyoshenka / @kauffj will be beefing up some of the docs on lbry.tech this week, so I'll let them review to see if anything else needs to be added here (though it does look like it talks about both the targeting + difficulty).
lyoshenka commented 2019-01-16 14:59:40 +01:00 (Migrated from github.com)
Copy link

That whole article should just be replaced with a link to https://spec.lbry.io/#consensus

That whole article should just be replaced with a link to https://spec.lbry.io/#consensus
AdamZWinter commented 2019-01-16 17:49:48 +01:00 (Migrated from github.com)
Copy link

@lyoshenka I found that page very helpful with the way it presented the structure of the hash algorithm. This is the first/only page I've found that explained this at this level. I like that it's somewhere between vaguely saying its a combination of some hash functions and having to decipher the source code. That said, I've edited the other part to just link directly to the white paper, like you've suggested.

@lyoshenka I found that page very helpful with the way it presented the structure of the hash algorithm. This is the first/only page I've found that explained this at this level. I like that it's somewhere between vaguely saying its a combination of some hash functions and having to decipher the source code. That said, I've edited the other part to just link directly to the white paper, like you've suggested.
lyoshenka commented 2019-01-17 14:43:43 +01:00 (Migrated from github.com)
Copy link

👍

:+1:
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area: devops

   
area: discovery

   
area: docs

   
area: livestream

   
area: proposal

Work is part of a proposal

  
campaign-blocker

   
consider soon

Discuss this issue at the next planning meeting, then remove this label

  
Content

   
dependencies

Pull requests that update a dependency file

  
Epic

   
good first issue

Good for newcomers

  
hacktoberfest

Welcome to Hacktoberfest

  
help wanted

Extra attention is needed

  
icebox

Long-term storage

  
level: 1

No knowledge of the existing code required

  
level: 2

Some knowledge of the existing code is recommended

  
level: 3

Significant knowledge of the existing code is recommended

  
level: 4

Intimate knowledge of the existing code is recommended

  
needs: exploration

Solution unclear, needs research

  
needs: grooming

Issue needs to be groomed before work can start

  
needs: priority

Priority level needs to be defined

  
needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  
needs: tech design

Needs technical design signoff before implementation can begin

  
on hold

Temporarily paused

  
priority: blocker

Issue is blocking release, do ASAP

  
priority: high

Work needs to be moved into sprint ASAP

  
priority: low

Work should be done but can stay in the backlog for now

  
priority: medium

Work needs to be done within 2-3 sprints

  
resilience

   
Tom's Wishlist

   
type: bug

Existing functionality is wrong or broken

  
type: discussion

A conversation. No specific changes requested

  
type: improvement

Existing (or partially existing) functionality needs to be changed

  
type: new feature

New functionality that does not exist yet

  
type: refactor

Minimal user-visible changes, but significant internal work

  
type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  
type: testing

Solution needs additional user testing

  
unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
campaign-blocker
consider soon
Content
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.tech#213
No description provided.
Delete branch "patch-1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?