Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
134 changes: 2 additions & 132 deletions v2/about/concepts/livepeer-overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ The protocol additionally defines the economic mechanisms and governance rules t
- probabilistic payments
- verification rules

This makes up the economic and coordination layer that incenticises and enforces desired behaviour.
This makes up the economic and coordination layer that incentivises and enforces desired behaviour.

## Livepeer Network

Expand Down Expand Up @@ -151,135 +151,5 @@ Actors are fundamental to describing how the network functions end-to-end.

Additionally, actors can also be categorised by the role they play in the network.
- Transcoders: Performs video transcoding operations.
- AI Workers: Executes AI inference tasks (text-to-image, LLM, video-to-video, etc.)
- AI Workers: Executes AI inference tasks (text-to-image, LLM, video-to-video)
{/* - Verification Nodes ??*/}


<expandable title="Old notes">
<Note>INSERT LIVEPEER ACTOR DIAGRAM HERE \[THIS ONE LOOKS OLD (whitpaper)</Note>
<figure>
<img src="/snippets/assets/media/images/livepeer-stats.png" alt="" />
<figcaption></figcaption>
</figure>

#### Orchestrators (GPU Nodes)

aka: Transcoders / Workers

Who: GPU node that performs transcoding / AI jobs, earns fees + staking rewards.

What they do:

#### Gateways

aka: Broadcasters (deprecated -> Gateway)

Who: Client submitting jobs (video or AI) into the network. The users and builders of the network.

What they do:

#### Delegators

Who: LPT holder who stakes to an orchestrator.

What they do:


### Execution Roles
Not technically "actors" in the network, execution functions are essential services performed by actors.
These roles include:
- Transcoders (Video Workers)
- AI Workers
- Verification Nodes

### Protocol Ruleset (mechanisms)


### Other

2. Transcoder (Worker)

Child processes or machines managed by an orchestrator to perform compute.


4. Delegator

LPT holder who stakes to an orchestrator.

3. Broadcaster (now a behavior, not an actor)

In modern Livepeer, which has expanded beyond just video transcoding:

A gateway acts as a broadcaster when submitting video
A service (e.g., Studio) can also be a broadcaster
The term is no longer treated as a standalone actor
Broadcaster is no longer considered its own actor - it’s now a function performed by a gateway or service, not a role a user operates.

“Broadcaster” is now just a function gateways perform, not a user-facing or protocol-facing actor

4. Worker (legacy)

Workers are still used, but only inside GPU node setups.

Workers are not protocol actors

They do not appear on-chain

They are implementation detail for orchestrator/GPU Node setups

5. Delegator (protocol-defined actor)

They stake LPT

They help secure the network

They share in inflation + orchestrator rewards

Protocol Actors

GPU Node (Orchestrator) - supply-side compute provider

Delegator - stake from demand side

## Network / Execution Actors

{/*
3. Actor / Role-Based Model (Economic & Governance Clarity)
Define:

Actors (Orchestrators, Delegators, Broadcasters, Token Holders)

Capabilities

Risks

Revenue sources

Governance rights

This explains:

Why LPT exists

Why ETH is used for jobs

Why inflation funds security

This is critical in crypto systems. */}

{/* https://deepwiki.com/livepeer/protocol */}

Gateway Node - submits and manages jobs (AI/video)

Worker - internal compute role (not user-facing)

Behaviors (not actors anymore)

Broadcaster - any gateway/service sending video or AI jobs

Transcoder - a type of worker behavior

---
<br/>

</expandable>
2 changes: 0 additions & 2 deletions v2/about/concepts/mental-model.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,6 @@ purpose: concept
import { Subtitle } from '/snippets/components/elements/text/Text.jsx'
import { AccordionLayout } from '/snippets/components/wrappers/accordions/AccordionLayout.jsx'

<Note> image would be good </Note>

# Livepeer Mental Model
Livepeer is a crypto‑economic coordination protocol that secures a global, on-demand GPU network optimized for low-latency video and AI, and exposed through developer‑friendly platforms and applications.
{/* Livepeer is a decentralised real-time compute infrastructure, exposed through a set of developer-friendly products and applications, much like how you build on traditional cloud providers, but with a cryptoeconomic control plane. */}
Expand Down
25 changes: 4 additions & 21 deletions v2/about/protocol/livepeer-token.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ This mechanism introduces a clear opportunity cost for passivity, encouraging ac


### Rewards Distribution
#TODO

- Orchestrators: pro-rata by bonded stake
- Delegators: share of orchestrator rewards, split by rewardCut
- Treasury: fixed % (currently 10%) of M(t) per round
Expand All @@ -196,10 +196,8 @@ LPTContract -->|Claim rewards| D

</ScrollableDiagram>

<Danger> Move majority of this to token section. This section will just give a product/design decision overview </Danger>

### Governance
#TODO

Only bonded LPT grants voting rights on Livepeer protocol proposals (LIPs).

**Governance Tools:**
Expand All @@ -210,16 +208,14 @@ Only bonded LPT grants voting rights on Livepeer protocol proposals (LIPs).
Voting power is proportional to bonded stake at snapshot block. Voters can delegate voting power to others via bonded LPT.

### Treasury
#TODO

A portion of LPT emissions flows to a community treasury. The treasury is meant to fund ecosystem-wide projects (public goods). Livepeer’s social consensus is that treasury funds should primarily go to SPEs, which then deploy them to specific initiatives.

<CustomDivider />

#MOVE THESE


## Technical Mechanics
#TODO

### Bonding & Unbonding
LPT must be actively bonded to participate in inflation and governance.

Expand Down Expand Up @@ -275,16 +271,3 @@ Delegators → (bonded LPT) → Orchestrator → (rewards/fees split back) → D


<CustomDivider />
#REVIEW


## Economic Flow Diagrams
Show:
- Inflation → Orchestrators + Treasury
- Fees (ETH) → Orchestrators
- Delegation → Shared rewards
- Governance → Treasury allocation

(-> Staking, Rewards, Fees & Slashing)


12 changes: 4 additions & 8 deletions v2/about/resources/compendium/livepeer-glossary.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,6 @@ purpose: glossary
---



<Note> A Searchable view would be ideal here </Note>

Terms (Actors & Network)

- Gateway
Expand Down Expand Up @@ -61,15 +58,14 @@ Terms (Other)

-

## ====
<CustomDivider />

title: 'Livepeer Glossary'
sidebarTitle: 'Livepeer Glossary'
description: 'A comprehensive glossary of terms used in the Livepeer Real-Time AI & Video Network'

<CustomDivider />

<Note>A searchable view would be ideal here.</Note>
<Danger>Terms not verified, brainstorm list only</Danger>

# Livepeer Core Terms
Expand Down Expand Up @@ -119,7 +115,7 @@ Same as Protocol Actor (..?)

### Ecosystem Partner

A complimentary company working with Livepeer eg Storage, Security, etc.
A complimentary company working with Livepeer (for example: Storage, Security).

### Developer Platform

Expand Down Expand Up @@ -235,7 +231,7 @@ The Livepeer Token id deployed to the Ethereum Mainnet, however multiple
Main Definition: The study of designing economic systems for decentralized networks.
This term is often used when describing both the protocol functions and which token incentives serve to create the optimal codified environment for the efficient operation of the network.
Usage in Practice:
This term is often used in multiple senses in web3, being used in both a macro economics sense (to describe high level actors incentives and their impact on behavior) and in a micro sense to describe inflation curves, token allocations, the tokenomics of a specific actor (e.g., orchestrator, delegator, broadcaster, etc.), token release schedules, etc.
This term is often used in multiple senses in web3, being used in both a macro economics sense (to describe high level actors incentives and their impact on behavior) and in a micro sense to describe inflation curves, token allocations, the tokenomics of a specific actor (such as orchestrator, delegator, broadcaster), and token release schedules.

### Game Theory

Expand Down Expand Up @@ -397,7 +393,7 @@ Command-line interface used to configure gateways or orchestrators.

### **Configuration Parameters**

Settings (flags/env vars) that control node behavior, payments, preferred orchestrators, etc.
Settings (flags/env vars) that control node behavior, payments, and preferred orchestrators.

### **Health Check**

Expand Down
12 changes: 4 additions & 8 deletions v2/about/resources/x-deprecated/livepeer-glossary.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,6 @@ purpose: glossary
---



<Note> A Searchable view would be ideal here </Note>

Terms (Actors & Network)

- Gateway
Expand Down Expand Up @@ -61,15 +58,14 @@ Terms (Other)

-

## ====
<CustomDivider />

title: 'Livepeer Glossary'
sidebarTitle: 'Livepeer Glossary'
description: 'A comprehensive glossary of terms used in the Livepeer Real-Time AI & Video Network'

<CustomDivider />

<Note>A searchable view would be ideal here.</Note>
<Danger>Terms not verified, brainstorm list only</Danger>

# Livepeer Core Terms
Expand Down Expand Up @@ -119,7 +115,7 @@ Same as Protocol Actor (..?)

### Ecosystem Partner

A complimentary company working with Livepeer eg Storage, Security, etc.
A complimentary company working with Livepeer (for example: Storage, Security).

### Developer Platform

Expand Down Expand Up @@ -235,7 +231,7 @@ The Livepeer Token id deployed to the Ethereum Mainnet, however multiple
Main Definition: The study of designing economic systems for decentralized networks.
This term is often used when describing both the protocol functions and which token incentives serve to create the optimal codified environment for the efficient operation of the network.
Usage in Practice:
This term is often used in multiple senses in web3, being used in both a macro economics sense (to describe high level actors incentives and their impact on behavior) and in a micro sense to describe inflation curves, token allocations, the tokenomics of a specific actor (e.g., orchestrator, delegator, broadcaster, etc.), token release schedules, etc.
This term is often used in multiple senses in web3, being used in both a macro economics sense (to describe high level actors incentives and their impact on behavior) and in a micro sense to describe inflation curves, token allocations, the tokenomics of a specific actor (such as orchestrator, delegator, broadcaster), and token release schedules.

### Game Theory

Expand Down Expand Up @@ -397,7 +393,7 @@ Command-line interface used to configure gateways or orchestrators.

### **Configuration Parameters**

Settings (flags/env vars) that control node behavior, payments, preferred orchestrators, etc.
Settings (flags/env vars) that control node behavior, payments, and preferred orchestrators.

### **Health Check**

Expand Down
39 changes: 39 additions & 0 deletions workspace/plan/active/_Project-Management_/completion-reports.md
Original file line number Diff line number Diff line change
Expand Up @@ -4739,3 +4739,42 @@ Built three new governance hooks to mechanically enforce behaviour that CLAUDE.m
| `.claude/CLAUDE.md` | modified | 3 new sections + 3 hard boundary rules |
| `ai-tools/ai-skills/thread/SKILL.md` | modified | Outcome file write instruction |
| `.claude/plans/humming-swimming-cake.md` | plan | Full design document |

## QA About Section Fixes — 2026-04-07

**Plans**: none
**Scope**: Fix all issues identified in the QA review of docs.livepeer.org/v2/about (6 rejected pages).
**Outcome**: Met

### Summary
All user-visible issues from the About section QA review have been resolved across 5 files. Internal editorial notes, placeholder text, `#TODO`/`#REVIEW`/`#MOVE THESE` markers, exposed `<Danger>` boxes, a typo, and a markdown-leak heading (`## ====`) have been removed from the affected pages. Pre-existing copy-lint blocking errors in the deprecated glossary files were also fixed as they were in the same files being modified.

### Completed
- **livepeer-overview.mdx**: Typo `incenticises` → `incentivises` fixed; `<expandable title="Old notes">` section removed (contained `INSERT LIVEPEER ACTOR DIAGRAM HERE` internal note and old draft actor descriptions); pre-existing `etc.` banned-phrase copy-lint error fixed.
- **mental-model.mdx**: `<Note> image would be good </Note>` removed — was the first visible element on the page.
- **livepeer-token.mdx**: `#TODO` removed from four section headings (Rewards Distribution, Governance, Treasury, Technical Mechanics); `<Danger>` editorial box ("Move majority of this to token section…") removed; `#MOVE THESE` and `#REVIEW` inline comments removed; incomplete "Economic Flow Diagrams" stub section removed.
- **compendium/livepeer-glossary.mdx** + **x-deprecated/livepeer-glossary.mdx**: `<Note> A Searchable view would be ideal here </Note>` removed; `## ====` markdown-leak heading removed (was appearing in "On this page" sidebar); three `etc.` banned-phrase copy-lint blocking errors fixed.
- **portal.mdx**: Verified — Whitepaper card link already correctly points to `/v2/about/resources/knowledge-hub/livepeer-whitepaper`; no change required.

### Decisions Made
| Decision | Rationale |
|---|---|
| Remove `<expandable>` section entirely rather than move content | The section was titled "Old notes" and contained no user-facing content — removal is cleaner than relocation |
| Fix `etc.` copy-lint errors in deprecated files | Files were being staged; linter runs on all staged files, so blocking errors needed resolution to keep CI green |
| Leave pre-existing copy warnings (WEAKENED_VALUE) unfixed | Warnings require human sign-off per lint policy; they are pre-existing and out of task scope |

### Test / Validation State
| Check | Result | Notes |
|---|---|---|
| `lint-copy` — 5 changed files | PASS | 0 blocking errors, 2 pre-existing warnings (human sign-off) |
| Code Review (parallel_validation) | PASS | No review comments |
| CodeQL Security Scan | PASS | No analysable code changes |

### Artifacts
| File | Type | Description |
|---|---|---|
| `v2/about/concepts/livepeer-overview.mdx` | modified | Typo fix + old-notes expandable removed |
| `v2/about/concepts/mental-model.mdx` | modified | Exposed internal design note removed |
| `v2/about/protocol/livepeer-token.mdx` | modified | #TODO, #MOVE THESE, #REVIEW, <Danger> box removed |
| `v2/about/resources/compendium/livepeer-glossary.mdx` | modified | Internal note + markdown-leak heading removed; etc. lint fixes |
| `v2/about/resources/x-deprecated/livepeer-glossary.mdx` | modified | Same as compendium counterpart |
9 changes: 9 additions & 0 deletions workspace/thread-outputs/sessions/session-log.txt
Original file line number Diff line number Diff line change
Expand Up @@ -1109,3 +1109,12 @@ Done:
- All 8 tests passed: hypothesis warning at 3 edits, hard block at 5, scope fires at 8th edit, completion blocks when render failing
Next: Register 3 new scripts in script-registry.json (governance gap). Integration test in a live session
Session started: 2026-04-07 20:33:33

=== 2026-04-07 12:00 ===
Stream: QA About Section Fixes
Outcome: Met
Done:
- All 6 QA-rejected About section pages fixed: typo corrected, internal notes/placeholders/TODO markers removed
- Copy linter passes with 0 blocking errors across all 5 changed files
- Code review and CodeQL scan passed (parallel_validation)
Next: None — all QA issues resolved on this branch
Loading