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

spec links / glossary audit #258

Merged
tzarebczan merged 14 commits from links into master 2019-02-19 19:11:46 +01:00
Conversation 0 Commits 14 Files changed 8 +1 -1
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 3b94ab8ffd - Show all commits

2
documents/partials/overview/lbrycrd.md
View file

@ -4,7 +4,7 @@ LBRY uses a public, proof-of-work blockchain that is very similar to Bitcoin. Th
The most salient feature of the LBRY blockchain is the association of a normalized string of characters (a "name") with a structured set of metadata. This coupling is called a [[claim]]. The content referenced by a claim can be accessed as a LBRY URL, e.g. [lbry://hellolbry](/playground?url=hellolbry). The most salient feature of the LBRY blockchain is the association of a normalized string of characters (a "name") with a structured set of metadata. This coupling is called a [[claim]]. The content referenced by a claim can be accessed as a LBRY URL, e.g. [lbry://hellolbry](/playground?url=hellolbry).
The LBRY blockchain stores names and metadata in a parallel [[Merkle tree]], separate from the tree used to store transaction data. This allows LBRY URLs to be trustfully resolved even without a full copy of the blockchain. The LBRY blockchain stores names and metadata in a parallel [Merkle tree](/resources/claimtrie), separate from the tree used to store transaction data. This allows LBRY URLs to be trustfully resolved even without a full copy of the blockchain.
kauffj commented 2019-02-18 23:47:03 +01:00 (Migrated from github.com)
Review
Copy link

I think glossary is correct here, and the glossary can link to the expanded article

I think glossary is correct here, and the glossary can link to the expanded article
The metadata contains information about the content, such as the title, creator, price (if any), and a unique signature allowing the actual content to be fetched from the data network, the next level in the LBRY stack. The metadata contains information about the content, such as the title, creator, price (if any), and a unique signature allowing the actual content to be fetched from the data network, the next level in the LBRY stack.