Skip to main content

LBRY

LBRY (Library Credits) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

LBRY — an Infra project on the LBRY network, token (symbol: LBC).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a protocol and network for publishing and accessing digital content, where the blockchain stores the index of available content and transactions (per Tier‑1).
  • Who it’s for: users/content creators and application developers who work with the LBRY protocol.
  • Why onchain/token: onchain records the index/publications and transactions; the LBC token is used for payments (tips/purchases/paid content).

How it works (very briefly)

  1. The user does: publishes or watches/downloads content via applications that work with the LBRY protocol.
  2. The system does: content is hosted on a P2P network of hosts, and the blockchain stores the index of “what is available and how to download it”.
  3. The user gets: access to content for free or for payment/tips.
  4. Where the blockchain is: publications (claims/index) and financial transactions are recorded on the LBRY blockchain.
  5. Token role: LBC is used for tips and purchases/paid content (per Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name LBRY
Also known as (aliases) Library Credits, LBC
Logo (logo) ../assets/676_library-credits_logo.svg
Token symbol (ticker) LBC
Category Infra
Primary chain (chain) LBRY
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Tier‑1: LBC is used for tips and purchases/paid content; supply/issuance details are not established.
Governance —
Admins/keys —
Audit —
Bug bounty yes
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) publish + access content via protocol
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 3 / token_score 1 / evidence_score 1
Last verified 2026-02-11

General project overview

In the Tier‑1 materials, LBRY is described as a protocol/network that allows applications to publish and retrieve digital content via P2P hosting, while the blockchain stores the index of available content and download instructions, as well as transactions. LBC (LBRY Credits) is used as the currency. No AI component was found in Tier‑1, so DecAI Fit = 0/6.

Features/modules

  • Publishing protocol (claims/index): recording the fact of publication on the blockchain.
  • P2P content hosting: files are delivered via a network of hosts.
  • Payments/tips: transactions in LBC (tips/purchases) are recorded on the blockchain.

Typical scenarios

  • Scenario 1: a creator publishes content → a record (claim/index) appears on the blockchain → the content is available via applications.
  • Scenario 2: a user watches/downloads content → in the case of paid access/tips makes a transaction in LBC.

Getting started (wallet/network)

  • What you need: an application/client that works with LBRY (for example, LBRY Desktop or web clients).
  • Network/chain: LBRY.
  • Fees: network fees for transactions (tips/purchases/publish) on LBRY.

Architecture/tech (non‑AI)

  • Components: the LBRY blockchain (index/transactions), a P2P network of content hosts, client applications.
  • Participant roles: content creators, users, hosts/network nodes.
  • Where logic runs: onchain — index/transactions; offchain — file delivery via P2P.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: tips and purchases/paid access to content (per Tier‑1).
  • Protocol necessity drivers: the token is the means of settlement for content‑related transactions.
  • Who pays fees: users who make transactions.
  • Where fees go: — (not established).
  • Issuance/burn: — (not established).
  • Security/incentive mechanisms: — (not established).
  • Distribution and token issuance schedule: — (not established).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established).
  • How protocol parameters change: — (not established).
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: see links_* (there is a link to the security/bug bounty page).
  • Incidents: — (not established).
  • Threat model: typical risks of P2P hosting/client software and protocol vulnerabilities; details — in the documentation/security section.

Project status and timeline

  • Current status: mainnet.
  • Key releases/milestones: there are GitHub Releases for the client (see links_*).
  • Roadmap: see links_*.

Ecosystem/integrations

  • Integrations: applications on top of the protocol (for example, web clients and the desktop client).
  • Partners: — (not established).
  • Where it’s actually used: the presence of content and transactions can be checked via the blockchain explorer (see links_*).

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component was found.
  • What is truly onchain? the index of available content (claims) and financial transactions (tips/purchases) on the LBRY blockchain.
  • Why is a token needed? LBC is used for tips and purchases/paid content.
  • Red flags (based on the information found): AI‑washing (if the project is positioned somewhere as AI without Tier‑1); centralization/moderation risks depend on the specific clients/hosting (one needs to read the specification and threat model).

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity high 3
Token necessity medium 1
Evidence Tier‑1 present 1
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 declaration of AI intent was found.
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): Tier‑1 describes a content protocol, not an AI roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI features are not described in Tier‑1.
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): There is no description of an AI module/model.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No demo of an AI component was found (an AI component is not established).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): AI_2 requires a demo surface of AI.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): AI metrics are not applicable (an AI component is not established).
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): No tech description of an AI component was found (an AI component is not established).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): The tech description relates to the content protocol, not to AI.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: LBRY
  • Addresses/identifiers: explorer for transactions/claims: https://explorer.lbry.com
  • Evidence: Tier‑1 — https://explorer.lbry.com ; https://lbry.tech/spec
  • Why sufficient / why not (one line): The existence of the protocol specification and a blockchain explorer confirms the onchain network.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: recording of publications/the content index (claims) and financial transactions (tips/purchases).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): Tier‑1 explains that the blockchain stores the content index and transactions, not just the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the public uncontrolled index of publications/transactions breaks down (it can be censored/rewritten centrally).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): Tier‑1 explains that it is the blockchain that makes the content index and transactions uncensorable, similarly to the Bitcoin model.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a currency/token, LBC (LBRY Credits).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): Tier‑1 names LBC (LBRY Credits) as the currency for transactions.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): LBC is used for tips and purchases/paid content (payment for access/an action).
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): Tier‑1 describes payment for paid content and tips via LBC.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): Staking/slashing/rewards with the token as a protocol mechanism are not established in Tier‑1.
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): 1 requires specific rules of incentives/penalties.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): A governance role of LBC is not established in Tier‑1.
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): No description of voting/governance via the token was found.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established.
  • Evidence: Tier‑1 — https://lbry.com/faq/what-is-lbry
  • Why sufficient / why not (one line): TK_4=1 requires a separate justification of replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://lbry.com/faq/what-is-lbry Tier‑1: LBRY as a protocol; the blockchain stores the content index and transactions; LBC is used for tips/purchases.
Tier‑1 https://lbry.tech/ Tier‑1: LBRY Tech as navigation to the specification/resources.
Tier‑1 https://lbry.tech/spec Tier‑1: the formal specification of the protocol (technical proof of its protocol nature).
Tier‑1 https://explorer.lbry.com Onchain fact: a blockchain explorer for transactions/claims.
Tier‑1 — No Tier‑1 source for claim “the project’s AI component” was found.

No comments to display

Back to top