This glossary will help you understand the exact meaning of LBRY and blockchain related terms.
We encourage the submission of changes and additions to this glossary.
- Blob Exchange Protocol
- Block Header
- Block Height
- Claim Sequence
- Cold Storage
- Confirmed Transaction
- Content Blob
- Effective Amount
- Full Node
- Genesis Block
- Hard Fork
- LBRY Credits
- Resolve (or URL Resolution)
- Simplified Payment Verification
- Stream Descriptor
- Stream Hash
- Stream Key
- Transaction Fee
The smallest unit of data in LBRY. Each blob is referenced by its blob hash, a SHA-384 hash of the blob contents. When files are uploaded to LBRY, they are split into blobs, which are then shared with other peers. See Encoding for more details.
Blob Exchange Protocol
The peer-to-peer protocol that LBRY nodes use to upload and download blobs from each other. It handles data transfer, availability checking, and data price negotiation. The name is sometimes shortened to “BlobEx” or “blobex”. The spec has more info.
A data structure that consists of a block header and a list of transactions. Each block references one previous block, thus forming an ordered list called the blockchain.
The fields included at the top of each block. They are
- block version number
- hash of the previous block header
- hash of the transactions in the block
- root hash of the claimtrie, after all operations in the current block have been applied
- current timestamp in seconds
- current target
The sequence number of a block in the blockchain. The first block is at height 0, the second is at height 1, and so on. Block 0 is called the genesis block.
An open, distributed ledger that records transactions in a verifiable and change-resistant way. The LBRY blockchain serves as an index of the content available on the network, a payment system and record of purchases for priced content, and a source if cryptographic publisher identities.
A tool that stores blockchain data in an SQL database, keeps the database up-to-date as the blockchain grows, and provides an API to access the data using standard SQL queries.
The unit of identity in LBRY. A channel is established by publishing a special type of claim that contains a public key. Once a channel is created, content can be published “into” a channel by signing a piece of content with the private key that goes with a channel’s public key. Channels allow publishers to build a brand and notify subscribers when new content is published. For details, see Channels.
A claimtrie is a data structure used to store the set of all claims and prove the correctness of URL resolution. Full details at Claimtrie.
The order in which a claim for a particular name was created. Claim sequence is used in URLs to reference claims by their order. For example, the third claim for the name
hello can be referenced by
lbry://hello:3. See Claim Sequence for more details.
A way to securely store digital information (e.g. private keys) by storing them on a medium that is not connected to the internet. This can take the form of an offline computer, USB key, hardware wallet, or even writing the data on a piece of paper.
Transaction that has been included in the blockchain. Probability of transaction being rejected is measured in a number of confirmations. See Confirmation.
Transactions are confirmed when they have been included in a block that is part of the current “best” chain (the one with the highest total proof-of-work). A transaction in the most recent block of the chain is said to have 1 confirmation. A transaction in the previous block has 2 confirmations, and so on. A transaction that has not yet been included has zero confirmations, or is unconfirmed. Confirmation is not a guarantee that a transaction is final. Rather, the number describes the probability that a confirmation is final. Higher numbers increase the probability exponentially.
A set of rules that are used by blockchain nodes to determine whether a block is valid.
A blob that contains part of a published file.
The name of the smallest unit of currency in LBRY. 1 LBRY Credit (LBC) is equal to 100 million deweys. The name comes from the classification system used by libraries to organize their collections.
The sum of the amount of an active claim and all of its active supports. The effective amount affects which claim is controlling for a name. Claims that are not active have an effective amount of 0.
The price, set by the publisher, that must be paid before a piece of content can be downloaded. Free content has a fee of 0.
A node which can definitively decide whether a transaction is valid or not, without having to trust another source. Full nodes usually implement the full LBRY blockchain protocol and possess a full copy of the blockchain data. Compare with SPV node.
The first block in the blockchain. The genesis block is not mined, but is hard-coded into the protocol. It has no reference to a previous block. The LBRY genesis block was released on 28 Oct 2015. The first real block was mined was on 23 Jun 2016.
A change to the consensus rules such that a block that would have been considered invalid under the old rules is now considered valid under the new rules. Nodes that choose to adopt the hard fork will have to upgrade to the new rules in order to stay on the network. Nodes that refuse to adopt the new rules may continue to use the old rules. If a significant number of nodes are running both versions of the rules at once, the chain may split into two incompatible chains.
A measure of mining hardware performance expressed in hashes per second (GH/s). Click here for more details.
The currency code for LBRY Credit.
The SDK is three things:
- an implementation of the full LBRY protocol specification, except the blockchain protocol.
- components that are not part of the spec but are useful for developing applications using the protocol
- a daemon that participates in the LBRY data network and provides an API for interacting with the protocol
LBRY Credits are the cryptocurrency used to make digital transactions on the blockchain.
Main LBRY network and its blockchain. The term is mostly used in comparison to testnet.
The first blob in a stream. The manifest contains information necessary to find the content blobs and decode them into a file. See Streams in the specification.
The collection of unconfirmed transactions stored by a node until they either expire or get included in the blockchain.
A node, or client, is a program that implements LBRY. LBRY has two types of nodes: blockchain node and dht nodes. A single program may be both at once.
The combination of a transaction ID and an index which refers to a particular transaction output. An outpoint is the most specific way to refer to a version of a claim. In contrast, the claim ID is used to refer to the latest version of a claim.
A node that is connected to the global network and is responding to protocol requests. LBRY is a peer-to-peer network, which means that nodes connect to each other to perform network operations. A single node may sometimes act as a client and sometimes as a server.
A system is permissionless if it can be joined, interacted with, or used without the explicit authorization of any party, nor can any party revoke the ability to use the system.
An open system with no centralized control is permissionless. Examples include HTTP and Bitcoin.
A file included with each LBRY project that contains basic information about that project. More in (/resources/repository-standards).
A long-running node that accepts blobs for upload and rehosts them on the network.
Resolve (or URL Resolution)
The process of translating a URL into the associated claim ID and metadata. See Resolution for details.
A definition of the structure of the metadata that is stored in claims in the blockchain. See Metadata for more information.
Simplified Payment Verification
A scheme to validate transactions without storing the whole blockchain.
SPV is an abbreviation for Simplified Payment Verification.
A set of blobs that can be reassembled into a file. Every stream has one or more content blobs which contain the published file, and a manifest blob which contains a list of the content blob hashes.
A deprecated term that means the same thing as the manifest.
The SHA-384 hash of the stream manifest. The stream hash is a unique identifier for the stream.
The cryptographic key needed to decrypt the content blobs of a stream. The stream key may be stored in the stream manifest, or may be stored by a third party and made available to a client in exchange for proof that the content was purchased.
A parallel LBRY blockchain, used for testing and development. Testnet is like mainnet, but has a different genesis block and uses a slightly different address format to avoid confusion with main LBRY addresses. The testnet currency has no realworld value.
A change to the state of the blockchain. Transactions move credits from one address to another. They may also make changes to the claimtrie, such as creating or updating a claim.
The fee paid to a miner for including a transaction in a block. Miners are incentivized to include transactions with higher fees. When blocks are full, lower-fee transactions may have to wait longer to be included.
An application or a service that stores private keys and generates and signs transactions. Wallets do not store LBRY credits themselves (those are recorded as transactions in the global blockchain). “Storing LBC” usually means storing the private keys that control the credits.