-
- );
-};
diff --git a/snippets/components/_archive/folders/display-examples/embed-examples.mdx b/snippets/components/_archive/folders/display-examples/embed-examples.mdx
deleted file mode 100644
index cf44119d6..000000000
--- a/snippets/components/_archive/folders/display-examples/embed-examples.mdx
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "Markdown Embed Component Examples"
-description: "Examples of using the MarkdownEmbed component"
----
-
-import { MarkdownEmbed } from "/snippets/components/data/embed.jsx";
-
-## MarkdownEmbed
-
-### Basic Usage
-
-Embed external markdown content from a URL:
-
-
-
-
-
- {children}
-
-
-
- README
-
-
-Contributing
-
-
-
-### In a Frame
-
-
- - "The future of video is decentralized, open, and accessible to everyone." -- -### Longer Quote - -
- "Livepeer is building the world's open video infrastructure. By creating a decentralized network for video processing, we're making professional-quality video streaming accessible to creators and developers everywhere." -- ---- - -## FrameQuote - -A more advanced quote component with author attribution, source links, and frame styling. - -### Basic Quote with Author - -
-
-{`
- ┌─────────────┐
- │ Client │
- └──────┬──────┘
- │
- ▼
- ┌─────────────┐
- │ Gateway │
- └──────┬──────┘
- │
- ▼
- ┌─────────────┐
- │ Server │
- └─────────────┘
- `}
-
-
-{`
- Layer 1: Application
- ├── Web Interface
- ├── API Gateway
- └── Authentication
-
- Layer 2: Business Logic
- ├── Stream Processing
- ├── Transcoding Engine
- └── Storage Manager
-
- Layer 3: Data Layer
- ├── Database
- ├── Cache
- └── Object Storage
-
- Layer 4: Infrastructure
- ├── Load Balancer
- ├── CDN
- └── Monitoring
- `}
-
-
-{`
- ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
- │ Client │───▶│ CDN │───▶│ Gateway │───▶│ Transcode│───▶│ Storage │
- └──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
- │ │ │ │ │
- │ │ │ │ │
- ▼ ▼ ▼ ▼ ▼
- ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
- │Analytics │ │ Cache │ │ Auth │ │ Queue │ │ Database │
- └──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
- `}
-
-
-{`
- graph LR
- A[Video Upload] --> B[Validation]
- B --> C[Queue]
- C --> D[Transcoding]
- D --> E[Quality Check]
- E --> F{Pass?}
- F -->|Yes| G[Storage]
- F -->|No| D
- G --> H[CDN Distribution]
- H --> I[Playback]
- `}
-
-
-{`
- ╔════════════════════════════════════════════════════════════════════╗
- ║ LIVEPEER ECOSYSTEM ║
- ╚════════════════════════════════════════════════════════════════════╝
-
- ┌─────────────────────────────────────────────────────────────────┐
- │ CLIENT LAYER │
- ├─────────────────────────────────────────────────────────────────┤
- │ Web App │ Mobile App │ Desktop App │ Third-party Apps │
- └────┬──────┴──────┬───────┴───────┬───────┴──────────┬───────────┘
- │ │ │ │
- └─────────────┴───────────────┴──────────────────┘
- │
- ▼
- ┌─────────────────────────────────────────────────────────────────┐
- │ API GATEWAY │
- ├─────────────────────────────────────────────────────────────────┤
- │ Authentication │ Rate Limiting │ Request Routing │
- └────┬─────────────┴─────────┬───────┴────────────────────────────┘
- │ │
- ▼ ▼
- ┌─────────────┐ ┌─────────────────┐
- │ Stream │ │ Asset │
- │ Service │ │ Service │
- └──────┬──────┘ └────────┬────────┘
- │ │
- └──────────┬───────────┘
- ▼
- ┌─────────────────────────────────────────────────────────────────┐
- │ TRANSCODING LAYER │
- ├─────────────────────────────────────────────────────────────────┤
- │ Orchestrator │ Transcoder Nodes │ Quality Verification │
- └────────────────┴────────────────────┴──────────────────────────┘
- │
- ▼
- ┌─────────────────────────────────────────────────────────────────┐
- │ STORAGE LAYER │
- ├─────────────────────────────────────────────────────────────────┤
- │ Object Storage │ Database │ Cache │ CDN │
- └─────────────────────────────────────────────────────────────────┘
- `}
-
-
-{`
- 1. Client Request
- │
- ▼
- 2. API Gateway
- ├─ Validate API Key
- ├─ Check Rate Limit
- └─ Route Request
- │
- ▼
- 3. Service Layer
- ├─ Process Request
- ├─ Business Logic
- └─ Data Validation
- │
- ▼
- 4. Data Layer
- ├─ Query Database
- ├─ Update Cache
- └─ Store Results
- │
- ▼
- 5. Response
- └─ Return to Client
- `}
-
-
-{`
- ┌─────────────┐
- │ Broadcaster│
- └──────┬──────┘
- │
- ┌──────────────┼──────────────┐
- │ │ │
- ▼ ▼ ▼
- ┌──────────────┐ ┌──────────────┐ ┌──────────────┐
- │Orchestrator 1│ │Orchestrator 2│ │Orchestrator 3│
- └──────┬───────┘ └──────┬───────┘ └──────┬───────┘
- │ │ │
- ┌──────┴────┐ ┌──────┴────┐ ┌──────┴────┐
- │ │ │ │ │ │
- ▼ ▼ ▼ ▼ ▼ ▼
-┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
-│Trans 1 │ │Trans 2 │ │Trans 3 │ │Trans 4 │ │Trans 5 │
-└────────┘ └────────┘ └────────┘ └────────┘ └────────┘
- `}
-
-
-{`
- Input Video ──▶ Validation ──▶ Segmentation ──▶ Transcoding ──▶ Output
- │ │ │ │ │
- │ │ │ │ │
- ▼ ▼ ▼ ▼ ▼
- Format Check Size Check HLS Segments Multiple Storage
- Codec Check Duration DASH Segments Renditions CDN Push
- Resolution Metadata Thumbnails 720p, 480p Playback URLs
- `}
-
-
-
-
-
- Frontend Layer
-
- React Components, State Management, API Calls
-↓
-
- API Layer
-
- REST API, GraphQL, WebSocket
-↓
-
- Backend Layer
-
- Business Logic, Authentication, Processing
-Loading exchanges...
;
- }
-
- if (error) {
- return Error: {error}
;
- }
-
- if (exchanges.length === 0) {
- return No exchanges found for this coin.
;
- }
-
- // Sort exchanges based on current sort settings
- const sortedExchanges = sortBy
- ? [...exchanges].sort((a, b) => {
- let comparison = 0;
-
- if (sortBy === "type") {
- comparison = a.type.localeCompare(b.type);
- } else if (sortBy === "name") {
- comparison = a.name.localeCompare(b.name);
- }
-
- return sortOrder === "asc" ? comparison : -comparison;
- })
- : exchanges; // If no sort selected, use original API order
-
- const handleSort = (column) => {
- if (sortBy === column) {
- // Toggle sort order if clicking the same column
- setSortOrder(sortOrder === "asc" ? "desc" : "asc");
- } else {
- // Set new column and default to ascending
- setSortBy(column);
- setSortOrder("asc");
- }
- };
-
- // Convert trust score to color
- const getTrustScoreColor = (trustScore) => {
- if (trustScore === "N/A" || trustScore === "yellow") return "var(--lp-color-status-warn)";
- if (trustScore === "green") return "var(--lp-color-status-good)";
- if (trustScore === "red") return "var(--lp-color-status-bad)";
- return "var(--lp-color-status-warn)";
- };
-
- return (
-
-
-
-
-
- );
-};
diff --git a/snippets/components/data/data.jsx b/snippets/components/data/data.jsx
deleted file mode 100644
index a9a3ab9be..000000000
--- a/snippets/components/data/data.jsx
+++ /dev/null
@@ -1,778 +0,0 @@
-/**
- * @component BlogCard
- * @category data
- * @tier composite
- * @status stable
- * @description Blog Card data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {any} title - title prop.
- * @param {any} content - content prop.
- * @param {any} href - href prop.
- * @param {string} [author="Livepeer Team"] - author prop.
- * @param {any} [datePosted=null] - date Posted prop.
- * @param {any} [excerpt=null] - excerpt prop.
- * @param {any} [readingTime=null] - reading Time prop.
- * @param {string} [icon="book-open"] - icon prop.
- * @param {string} [authorIcon="user-pen"] - author Icon prop.
- * @param {string} [dateIcon="calendar"] - date Icon prop.
- * @param {string} [cta="Read More"] - cta prop.
- * @param {any} [img=null] - img prop.
- * @example
- * | handleSort("name")} - title="Click to sort by name" - > - Exchange{" "} - {sortBy === "name" && (sortOrder === "asc" ? "↑" : "↓")} - | -handleSort("type")} - title="Click to sort by type" - > - Type {sortBy === "type" && (sortOrder === "asc" ? "↑" : "↓")} - | -- Pair - | -- Trust - | -- Link - | -
|---|---|---|---|---|
| - {exchange.name} - | -
- |
- - {exchange.tradingPair} - | -
- |
- - - Trade → - - | -
*/}
- 
-
*/}
-
-
- {/* {author && (
-
- {/*
-
-
- )} */}
- {datePosted && (
-
-
-
- )}
- {readingTime && (
-
-
-
- )}
- {
- const el = e.target;
- const atBottom =
- el.scrollHeight - el.scrollTop <= el.clientHeight + 10;
- const hint = el.nextSibling;
- if (hint) hint.style.display = atBottom ? "none" : "block";
- }}
- dangerouslySetInnerHTML={{ __html: content }}
- />
- {showScrollHint &&
-
- );
- }
- return (
-
- {displayItems.map((props, idx) => (
-
- );
-};
-
-/**
- * @component BlogDataLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Blog Data Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn none
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {Array} [items=[]] - items prop.
- * @param {any} limit - limit prop.
- * @example
- *
- {author && (
-
**Generation Script**: This file is generated from script(s): `tools/scripts/generate-docs-guide-components-index.js`.
**Purpose**: Aggregate inventory of repository components from snippets/components for docs-guide maintenance.
@@ -927,68 +919,41 @@ import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx"; ```jsx lines Example import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx"; -
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. +
+ **Props**: `children`, `align`, `header`, `style`
+ **Defaults**: `align="left"`, `header=false`, `style={}`
```jsx lines Example
import { TableCell } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. - -
-```jsx lines Example
-import { ReviewCallout } from "/snippets/components/elements/callouts/PreviewCallouts.jsx";
-
-
-
-
-
-
- **Props**: `size`, `gap`, `justify`, `color`
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
-```jsx lines Example
-import { SocialLinks } from "/snippets/components/primitives/socialLinks.jsx";
-
-"}
+
-
-
-
- **Props**: `size`, `direction`
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Props**: `children`, `header`, `hover`, `style`
+ **Defaults**: `header=false`, `hover=false`, `style={}`
```jsx lines Example
import { TableRow } from "/snippets/components/wrappers/tables/Tables.jsx";
-
@@ -2028,1530 +1993,8 @@ import { PageHeader } from "/snippets/components/scaffolding/frame-mode/FrameMod
-## Disposition
-Les composants de disposition fournissent des primitives structurelles réutilisables pour organiser le contenu des pages.
-
-
-
-
- **Props**: `urls`
- **Defaults**: None - -
-```jsx lines Example
-import { ApiBaseUrlsTable } from "/snippets/components/layout/api-base-urls-table.mdx";
-
-"}
-/>
-```
-
-
-
-
-
- **Props**: `children`, `visibleCount`, `gap`, `showDots`, `style`
- **Defaults**: `visibleCount=3`, `gap="1.5rem"`, `showDots=true` - -
-```jsx lines Example
-import { CardCarousel } from "/snippets/components/layout/cardCarousel.jsx";
-
-
-
-
-
-
- **Props**: `children`, `maxHeight`, `showHint`, `ariaLabel`, `style`
- **Defaults**: `maxHeight=300`, `showHint=true`, `ariaLabel="Scrollable content"` - -
-```jsx lines Example
-import { ScrollBox } from "/snippets/components/layout/cards.jsx";
-
-
-
-
-
-
- **Props**: `children`, `variant`, `padding`, `borderRadius`, `style`
- **Defaults**: `variant="default"`, `padding="1rem"`, `borderRadius="8px"`, `style={}` - -
-```jsx lines Example
-import { BorderedBox } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-
-
-
- **Props**: `children`, `width`, `align`
- **Defaults**: `width="fit-content"`, `align="center"` - -
-```jsx lines Example
-import { CalloutContainer } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-
-
-
- **Props**: `children`, `align`, `justify`, `gap`
- **Defaults**: `gap="1rem"` - -
-```jsx lines Example
-import { CardContentContainer } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-"}
- justify={""}
- gap={"1rem"}
-/>
-```
-
-
-
- **Props**: `children`, `maxWidth`, `padding`, `style`
- **Defaults**: `maxWidth="800px"`, `padding="0"`, `style={}` - -
-```jsx lines Example
-import { CenteredContainer } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-
-
-
- **Props**: `children`, `backgroundColor`, `style`
- **Defaults**: `style={}` - -
-```jsx lines Example
-import { FullWidthContainer } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-"}
- style={{}}
-/>
-```
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { TabsContainer } from "/snippets/components/wrappers/containers/Containers.jsx";
-
-
-
-
-
-
- **Props**: `icon`, `title`, `style`, `background`, `children`
- **Defaults**: `background='var(--card-background)'` - -
-```jsx lines Example
-import { DisplayCard } from "/snippets/components/wrappers/cards/CustomCards.jsx";
-
-"}
- title={""}
- style={{}}
- background={'var(--card-background)'}
-/>
-```
-
-
-
- **Props**: `children`, `imgProps`, `imgStyle`, `cardProps`, `style`
- **Defaults**: None - -
-```jsx lines Example
-import { InlineImageCard } from "/snippets/components/wrappers/cards/CustomCards.jsx";
-
-
-
-
- **Props**: `width`, `children`
- **Defaults**: `width='80%'` - -
-```jsx lines Example
-import { WidthCard } from "/snippets/components/wrappers/cards/CustomCards.jsx";
-
-
-
-
-
-
- **Props**: `children`, `direction`, `gap`, `align`, `justify`, `wrap`, `style`
- **Defaults**: `direction="row"`, `gap="1rem"`, `align="flex-start"`, `justify="flex-start"`, `wrap=false`, `style={}` - -
-```jsx lines Example
-import { FlexContainer } from "/snippets/components/wrappers/containers/Layout.jsx";
-
-
-
-
- **Props**: `children`, `columns`, `gap`, `style`
- **Defaults**: `gap="1rem"`, `style={}` - -
-```jsx lines Example
-import { GridContainer } from "/snippets/components/wrappers/containers/Layout.jsx";
-
-
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { BasicList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { IconList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { StepLinkList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { StepList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { UpdateLinkList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
- **Props**: `listItems`
- **Defaults**: None - -
-```jsx lines Example
-import { UpdateList } from "/snippets/components/layout/lists.jsx";
-
-
-
-
-
-
- **Props**: `listItems`, `stepsConfig`
- **Defaults**: `stepsConfig={}` - -
-```jsx lines Example
-import { ListSteps } from "/snippets/components/layout/listSteps.jsx";
-
-
-
-
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `spinDuration`
- **Defaults**: `icon="arrows-spin"`, `iconSize=50`, `iconColor="var(--accent)"`, `spinDuration="10s"` - -
-```jsx lines Example
-import { QuadGrid } from "/snippets/components/layout/quadGrid.jsx";
-
-
-
-
-
-
- **Props**: `TableComponent`, `tableTitle`, `headerList`, `itemsList`, `monospaceColumns`, `margin`, `searchPlaceholder`, `searchColumns`, `categoryColumn`
- **Defaults**: `TableComponent=null`, `tableTitle=null`, `headerList=[]`, `itemsList=[]`, `monospaceColumns=[]`, `searchPlaceholder='Search...'`, `searchColumns=[]`, `categoryColumn='Category'` - -
-```jsx lines Example
-import { SearchTable } from "/snippets/components/layout/searchTable.jsx";
-
-"}
- searchPlaceholder={'Search...'}
- searchColumns={[]}
- categoryColumn={'Category'}
-/>
-```
-
-
-
-
-
- **Props**: `title`, `icon`, `titleSize`, `children`
- **Defaults**: `titleSize="h3"` - -
-```jsx lines Example
-import { StyledStep } from "/snippets/components/wrappers/steps/Steps.jsx";
-
-"}
- icon={""}
- titleSize={"h3"}
-/>
-```
-
-
-
- **Props**: `children`, `iconColor`, `titleColor`, `lineColor`, `iconSize`
- **Defaults**: `iconSize="24px"` - -
-```jsx lines Example
-import { StyledSteps } from "/snippets/components/wrappers/steps/Steps.jsx";
-
-"}
- titleColor={""}
- lineColor={""}
- iconSize={"24px"}
-/>
-```
-
-
-
-
-
- **Props**: `tableTitle`, `headerList`, `itemsList`, `monospaceColumns`, `margin`
- **Defaults**: `tableTitle=null`, `headerList=[]`, `itemsList=[]`, `monospaceColumns=[]` - -
-```jsx lines Example
-import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx";
-
-"}
-/>
-```
-
-
-
-
-
- **Props**: `children`, `variant`, `style`
- **Defaults**: `variant="default"`, `style={}` - -
-```jsx lines Example
-import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
-
- **Props**: `children`, `align`, `header`, `style`
- **Defaults**: `align="left"`, `header=false`, `style={}` - -
-```jsx lines Example
-import { TableCell } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
-
- **Props**: `children`, `header`, `hover`, `style`
- **Defaults**: `header=false`, `hover=false`, `style={}` - -
-```jsx lines Example
-import { TableRow } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { AccordionLayout } from "/snippets/components/layout/text.jsx";
-
-
-
-
-
-
-## Contenu
-Les composants de contenu fournissent du code, des données et des aides pour le format de réponse des pages de documentation.
-
-
-
-
- **Props**: `filename`, `icon`, `language`, `highlight`, `expandable`, `wrap`, `lines`, `codeString`, `placeholderValue`
- **Defaults**: `filename=""`, `icon="terminal"`, `language=""`, `highlight=""`, `expandable=false`, `wrap=true`, `lines=true`, `codeString=""`, `placeholderValue=""` - -
-```jsx lines Example
-import { CodeComponent } from "/snippets/components/content/code.jsx";
-
-
-
-
- **Props**: `fields`
- **Defaults**: `fields={}` - -
-```jsx lines Example
-import { CodeSection } from "/snippets/components/content/code.jsx";
-
-
-
-
- **Props**: `filename`, `icon`, `language`, `highlight`, `codeString`, `placeholderValue`, `wrap`, `lines`, `preNote`, `postNote`
- **Defaults**: `codeString=""`, `placeholderValue=""`, `wrap=true`, `lines=true`, `preNote=null`, `postNote=null` - -
-```jsx lines Example
-import { ComplexCodeBlock } from "/snippets/components/content/code.jsx";
-
-"}
- icon={""}
- language={""}
- highlight={""}
- codeString={""}
- placeholderValue={""}
- wrap={true}
- lines={true}
- preNote={null}
- postNote={null}
-/>
-```
-
-
-
- **Props**: `filename`, `icon`, `language`, `highlight`, `codeString`, `placeholderValue`, `wrap`, `lines`, `preNote`, `postNote`, `output`
- **Defaults**: `codeString=""`, `placeholderValue=""`, `wrap=true`, `lines=true`, `preNote=""`, `postNote=""`, `output=""` - -
-```jsx lines Example
-import { CustomCodeBlock } from "/snippets/components/content/code.jsx";
-
-"}
- icon={""}
- language={""}
- highlight={""}
- codeString={""}
- placeholderValue={""}
- wrap={true}
- lines={true}
- preNote={""}
- postNote={""}
- output={""}
-/>
-```
-
-
-
-
-
- **Props**: `repoName`, `githubUrl`, `maxHeight`, `icon`, `children`
- **Defaults**: `maxHeight="1000px"`, `icon="github"` - -
-```jsx lines Example
-import { ExternalContent } from "/snippets/components/content/externalContent.jsx";
-
-"}
- githubUrl={""}
- maxHeight={"1000px"}
- icon={"github"}
-/>
-```
-
-
-
-
-
- **Props**: `latex`, `className`, `ariaLabel`
- **Defaults**: `className=""` - -
-```jsx lines Example
-import { MathBlock } from "/snippets/components/content/math.jsx";
-
-"}
- className={""}
- ariaLabel={""}
-/>
-```
-
-
-
- **Props**: `latex`, `className`, `ariaLabel`
- **Defaults**: `className=""` - -
-```jsx lines Example
-import { MathInline } from "/snippets/components/content/math.jsx";
-
-"}
- className={""}
- ariaLabel={""}
-/>
-```
-
-
-
-
-
- **Props**: `children`, `author`, `source`, `href`, `frame`, `align`, `borderColor`, `img`, `spacing`
- **Defaults**: `frame=true`, `align='right'`, `spacing=true` - -
-```jsx lines Example
-import { FrameQuote } from "/snippets/components/content/quote.jsx";
-
-"}
- source={""}
- href={""}
- frame={true}
- align={'right'}
- borderColor={""}
- img={""}
- spacing={true}
-/>
-```
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { Quote } from "/snippets/components/content/quote.jsx";
-
-
-
-
-
-
- **Props**: `version`
- **Defaults**: None - -
-```jsx lines Example
-import { LatestVersion } from "/snippets/components/content/release.jsx";
-
-"}
-/>
-```
-
-
-
-
-
- **Props**: `description`
- **Defaults**: None - -
-```jsx lines Example
-import { CustomResponseField } from "/snippets/components/content/responseField.jsx";
-
-"}
-/>
-```
-
-
-
- **Props**: `fields`
- **Defaults**: `fields={}` - -
-```jsx lines Example
-import { ResponseFieldAccordion } from "/snippets/components/content/responseField.jsx";
-
-
-
-
- **Props**: `fields`
- **Defaults**: `fields={}` - -
-```jsx lines Example
-import { ResponseFieldExpandable } from "/snippets/components/content/responseField.jsx";
-
-
-
-
- **Props**: `component`, `fields`
- **Defaults**: `component="accordion"`, `fields={}` - -
-```jsx lines Example
-import { ResponseFieldGroup } from "/snippets/components/content/responseField.jsx";
-
-
-
-
- **Props**: `description`, `post`, `label`, `line`, `children`
- **Defaults**: `post=null`, `label="value"`, `line=true` - -
-```jsx lines Example
-import { ValueResponseField } from "/snippets/components/content/responseField.jsx";
-
-"}
- post={null}
- label={"value"}
- line={true}
-/>
-```
-
-
-
-
-
- **Props**: `embedUrl`, `title`, `style`
- **Defaults**: None - -
-```jsx lines Example
-import { CardVideo } from "/snippets/components/content/video.jsx";
-
-"}
- title={""}
- style={{}}
-/>
-```
-
-
-
- **Props**: `embedUrl`, `title`, `hint`, `caption`, `height`
- **Defaults**: `title="Embedded post"`, `hint=""`, `height="399"` - -
-```jsx lines Example
-import { LinkedInEmbed } from "/snippets/components/content/video.jsx";
-
-"}
- title={"Embedded post"}
- hint={""}
- caption={""}
- height={"399"}
-/>
-```
-
-
-
- **Props**: `src`, `title`, `subtitle`
- **Defaults**: None - -
-```jsx lines Example
-import { ShowcaseVideo } from "/snippets/components/content/video.jsx";
-
-"}
- title={""}
- subtitle={""}
-/>
-```
-
-
-
- **Props**: `src`, `title`, `subtitle`, `arrow`, `borderRadius`, `style`
- **Defaults**: `arrow=false`, `borderRadius="12px"`, `style={}` - -
-```jsx lines Example
-import { TitledVideo } from "/snippets/components/content/video.jsx";
-
-"}
- title={""}
- subtitle={""}
- arrow={false}
- borderRadius={"12px"}
- style={{}}
-/>
-```
-
-
-
- **Props**: `src`, `title`, `author`, `caption`, `href`, `controls`, `autoPlay`, `loop`, `muted`, `children`
- **Defaults**: `title=""`, `author=""`, `href=""`, `controls=true`, `autoPlay=false`, `loop=false`, `muted=false` - -
-```jsx lines Example
-import { Video } from "/snippets/components/content/video.jsx";
-
-
-
-
- **Props**: `embedUrl`, `title`, `author`, `hint`, `caption`
- **Defaults**: `title=""`, `author=""`, `hint=""` - -
-```jsx lines Example
-import { YouTubeVideo } from "/snippets/components/content/video.jsx";
-
-"}
- title={""}
- author={""}
- hint={""}
- caption={""}
-/>
-```
-
-
-
- **Props**: `embedUrl`, `title`, `hint`, `caption`
- **Defaults**: `caption=""` - -
-```jsx lines Example
-import { YouTubeVideoDownload } from "/snippets/components/content/video.jsx";
-
-"}
- title={""}
- hint={""}
- caption={""}
-/>
-```
-
-
-
-
-
- **Props**: `children`, `title`, `maxHeight`, `minWidth`, `showControls`
- **Defaults**: `title=""`, `maxHeight="500px"`, `minWidth="100%"`, `showControls=false` - -
-```jsx lines Example
-import { ScrollableDiagram } from "/snippets/components/content/zoomableDiagram.jsx";
-
-
-
-
-
-
-## Données
-Les composants de données affichent des jeux de données structurés, du contenu récupéré et des surfaces documentaires pilotées par API.
-
-
-
-
- **Props**: `coinId`
- **Defaults**: `coinId="arbitrum"` - -
-```jsx lines Example
-import { CoinGeckoExchanges } from "/snippets/components/data/coingecko.jsx";
-
-
-
-
-
-
- **Props**: `title`, `content`, `href`, `author`, `datePosted`, `excerpt`, `icon`, `authorIcon`, `dateIcon`, `cta`, `img`
- **Defaults**: `author="Livepeer Team"`, `datePosted=null`, `excerpt=null`, `icon="book-open"`, `authorIcon="user-pen"`, `dateIcon="calendar"`, `cta="Read More"`, `img=null` - -
-```jsx lines Example
-import { BlogCard } from "/snippets/components/data/data.jsx";
-
-"}
- content={""}
- href={""}
- author={"Livepeer Team"}
- datePosted={null}
- excerpt={null}
- icon={"book-open"}
- authorIcon={"user-pen"}
- dateIcon={"calendar"}
- cta={"Read More"}
- img={null}
-/>
-```
-
-
-
- **Props**: `items`, `limit`
- **Defaults**: `items=[]` - -
-```jsx lines Example
-import { CardBlogDataLayout } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `cols`, `items`, `limit`
- **Defaults**: `cols=2`, `items=[]` - -
-```jsx lines Example
-import { CardColumnsPostLayout } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `items`, `limit`
- **Defaults**: `items=[]` - -
-```jsx lines Example
-import { CardInCardLayout } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `items`, `cols`, `limit`
- **Defaults**: `items=[]`, `cols=2` - -
-```jsx lines Example
-import { ColumnsBlogCardLayout } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `items`, `limit`
- **Defaults**: `items=[]` - -
-```jsx lines Example
-import { DiscordAnnouncements } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `items`, `limit`
- **Defaults**: `items=[]` - -
-```jsx lines Example
-import { ForumLatestLayout } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `data`, `limit`, `type`
- **Defaults**: `type="upcoming"` - -
-```jsx lines Example
-import { LumaEvents } from "/snippets/components/data/data.jsx";
-
-
-
-
- **Props**: `title`, `content`, `href`, `author`, `datePosted`, `replyCount`, `icon`, `authorIcon`, `dateIcon`, `cta`, `img`
- **Defaults**: `author="Unknown"`, `datePosted=null`, `replyCount=null`, `icon="book-open"`, `authorIcon="user-pen"`, `dateIcon="calendar"`, `cta="Read More"`, `img=null` - -
-```jsx lines Example
-import { PostCard } from "/snippets/components/data/data.jsx";
-
-"}
- content={""}
- href={""}
- author={"Unknown"}
- datePosted={null}
- replyCount={null}
- icon={"book-open"}
- authorIcon={"user-pen"}
- dateIcon={"calendar"}
- cta={"Read More"}
- img={null}
-/>
-```
-
-
-
-
-
- **Props**: `url`
- **Defaults**: None - -
-```jsx lines Example
-import { MarkdownEmbed } from "/snippets/components/data/embed.jsx";
-
-"}
-/>
-```
-
-
-
- **Props**: `title`, `src`, `height`, `width`
- **Defaults**: `height='700px'`, `width='100%'` - -
-```jsx lines Example
-import { PdfEmbed } from "/snippets/components/data/embed.jsx";
-
-"}
- src={""}
- height={'700px'}
- width={'100%'}
-/>
-```
-
-
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. - -
-```jsx lines Example
-import { TwitterTimeline } from "/snippets/components/data/embed.jsx";
-
-
-
-
-
-
- **Props**: `items`, `limit`, `pageSize`
- **Defaults**: `items=[]`, `limit=null`, `pageSize=10` - -
-```jsx lines Example
-import { ShowcaseCards } from "/snippets/components/data/showcaseCards.jsx";
-
-
-
-
-
-
- **Props**: `items`, `limit`, `cols`
- **Defaults**: `items=[]`, `cols=2` - -
-```jsx lines Example
-import { YouTubeVideoData } from "/snippets/components/data/videoData.jsx";
-
-
-
-
-
-
-## Structure de page
-Les composants de structure de page orchestrent des sections complètes, des traitements hero et la composition au niveau des routes.
-
-
-
-
- **Props**: `density`
- **Defaults**: `density=1.1` - -
-```jsx lines Example
-import { Starfield } from "/snippets/components/page-structure/heroGif.jsx";
-
-
-
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { HeroContentContainer } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { HeroImageBackgroundComponent } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { HeroOverviewContent } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `children`, `minHeight`
- **Defaults**: `minHeight="fit-content"` - -
-```jsx lines Example
-import { HeroSectionContainer } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `src`, `alt`, `width`, `margin`, `imgHeight`, `imgWidth`, `objectFit`, `children`
- **Defaults**: `src="/snippets/assets/logos/Livepeer-Logo-Full-Theme.svg"`, `alt="Livepeer Logo"`, `width="100%"`, `margin="1rem auto 0 auto"`, `imgHeight="20px"`, `imgWidth="auto"`, `objectFit="contain"` - -
-```jsx lines Example
-import { LogoHeroContainer } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `children`, `title`
- **Defaults**: None - -
-```jsx lines Example
-import { PortalCardsHeader } from "/snippets/components/page-structure/portals.jsx";
-
-"}
-/>
-```
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { PortalContentContainer } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
- **Props**: `zIndex`, `subtitle`, `subtitleIcon`, `description`, `refCardLink`, `overview`, `divider`, `callout`, `titleColor`, `subtitleColor`, `children`
- **Defaults**: `zIndex=true`, `subtitle="Build - Explore - Create"`, `subtitleIcon="/snippets/assets/logos/Livepeer-Logo-Symbol-Green-Theme.svg"`, `divider=true`, `callout=null` - -
-```jsx lines Example
-import { PortalHeroContent } from "/snippets/components/page-structure/portals.jsx";
-
-"}
- refCardLink={""}
- overview={""}
- divider={true}
- callout={null}
- titleColor={""}
- subtitleColor={""}
-/>
-```
-
-
-
- **Props**: `children`, `title`, `icon`
- **Defaults**: None - -
-```jsx lines Example
-import { PortalSectionHeader } from "/snippets/components/page-structure/portals.jsx";
-
-"}
- icon={""}
-/>
-```
-
-
-
- **Props**: `children`
- **Defaults**: None - -
-```jsx lines Example
-import { RefCardContainer } from "/snippets/components/page-structure/portals.jsx";
-
-
-
-
-
-
-## Affichage
-Les composants d’affichage gèrent les médias, les intégrations, les citations et les motifs de présentation visuelle.
-
-
-
-
- **Props**: `color`, `margin`, `opacity`
- **Defaults**: `margin="1.5rem 0"`, `opacity=0.2` - -
-```jsx lines Example
-import { Divider } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- margin={"1.5rem 0"}
- opacity={0.2}
-/>
-```
-
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=32`, `align="left"`, `gap="0.75rem"` - -
-```jsx lines Example
-import { H1 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={32}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=28`, `align="left"`, `gap="0.75rem"` - -
-```jsx lines Example
-import { H2 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={28}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=24`, `align="left"`, `gap="0.5rem"` - -
-```jsx lines Example
-import { H3 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={24}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=20`, `align="left"`, `gap="0.5rem"` - -
-```jsx lines Example
-import { H4 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={20}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=18`, `align="left"`, `gap="0.5rem"` - -
-```jsx lines Example
-import { H5 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={18}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=16`, `align="left"`, `gap="0.5rem"` - -
-```jsx lines Example
-import { H6 } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- iconSize={16}
- iconColor={"
-
-
- **Props**: `children`, `icon`, `iconSize`, `iconColor`, `align`, `gap`
- **Defaults**: `iconSize=16`, `align="left"`, `gap="0.5rem"` - -
-```jsx lines Example
-import { P } from "/snippets/components/display/frame-mode.jsx";
-
-
-
-
- **Props**: `title`, `subtitle`, `description`, `children`, `titleColor`, `subtitleColor`, `descriptionColor`
- **Defaults**: None - -
-```jsx lines Example
-import { PageHeader } from "/snippets/components/display/frame-mode.jsx";
-
-"}
- subtitle={""}
- description={""}
- titleColor={""}
- subtitleColor={""}
- descriptionColor={""}
-/>
-```
-
-
-
-
-
-## Tableau de recherche
-Recherchez par catégorie, chemin de page ou nom de composant.
+## 查找表
+按类别、页面路径或组件名称搜索。
**Generation Script**: This file is generated from script(s): `tools/scripts/generate-docs-guide-components-index.js`.
**Purpose**: Aggregate inventory of repository components from snippets/components for docs-guide maintenance.
@@ -927,68 +919,41 @@ import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx"; ```jsx lines Example import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx"; -
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. +
+ **Props**: `children`, `align`, `header`, `style`
+ **Defaults**: `align="left"`, `header=false`, `style={}`
```jsx lines Example
import { TableCell } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. - -
-```jsx lines Example
-import { ReviewCallout } from "/snippets/components/elements/callouts/PreviewCallouts.jsx";
-
-
-
-
-
-
- **Props**: `size`, `gap`, `justify`, `color`
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
-```jsx lines Example
-import { SocialLinks } from "/snippets/components/primitives/socialLinks.jsx";
-
-"}
+
-
-
-
- **Props**: `size`, `direction`
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Props**: `children`, `header`, `hover`, `style`
+ **Defaults**: `header=false`, `hover=false`, `style={}`
```jsx lines Example
import { TableRow } from "/snippets/components/wrappers/tables/Tables.jsx";
-
diff --git a/v2/_workspace/archive/language-pages/fr/docs-guide/x-deprecated/catalog/components-catalog-archive.mdx b/v2/_workspace/archive/language-pages/fr/docs-guide/x-deprecated/catalog/components-catalog-archive.mdx
index 58d7ced6b..4dd210198 100644
--- a/v2/_workspace/archive/language-pages/fr/docs-guide/x-deprecated/catalog/components-catalog-archive.mdx
+++ b/v2/_workspace/archive/language-pages/fr/docs-guide/x-deprecated/catalog/components-catalog-archive.mdx
@@ -919,68 +919,41 @@ import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx";
```jsx lines Example
import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. +
+ **Props**: `children`, `align`, `header`, `style`
+ **Defaults**: `align="left"`, `header=false`, `style={}`
```jsx lines Example
import { TableCell } from "/snippets/components/wrappers/tables/Tables.jsx";
-
-
-
- **Props**: No explicit props detected from signature.
- **Defaults**: No explicit defaults detected. - -
-```jsx lines Example
-import { ReviewCallout } from "/snippets/components/elements/callouts/PreviewCallouts.jsx";
-
-
-
-
-
-
- **Props**: `size`, `gap`, `justify`, `color`
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
-```jsx lines Example
-import { SocialLinks } from "/snippets/components/primitives/socialLinks.jsx";
-
-"}
+
-
-
-
- **Props**: `size`, `direction`
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Props**: `children`, `header`, `hover`, `style`
+ **Defaults**: `header=false`, `hover=false`, `style={}`
```jsx lines Example
import { TableRow } from "/snippets/components/wrappers/tables/Tables.jsx";
-
diff --git a/v2/about/_workspace/archive/pre-pipeline-rewrite/core-concepts.mdx b/v2/about/_workspace/archive/pre-pipeline-rewrite/core-concepts.mdx
deleted file mode 100644
index 47ee86c6a..000000000
--- a/v2/about/_workspace/archive/pre-pipeline-rewrite/core-concepts.mdx
+++ /dev/null
@@ -1,137 +0,0 @@
----
-title: Livepeer Core Concepts
-sidebarTitle: Livepeer Core Concepts
-description: >-
- A high-level introduction to the key concepts and architecture of the Livepeer
- Real-time AI & Video Network
-pageType: concept
-keywords:
- - livepeer
- - about
- - core concepts
- - livepeer core concepts
- - introduction
- - key
- - architecture
-'og:image': /snippets/assets/media/og-images/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: general
-lastVerified: 2026-03-17
-purpose: concept
----
-
-
-import Protocol from "/snippets/composables/pages/about/concepts/protocol.mdx"
-import Network from "/snippets/composables/pages/about/concepts/network.mdx"
-import Actors from "/snippets/composables/pages/about/concepts/actors.mdx"
-
-### Overview and separation
-
-Livepeer is designed as a modular video/AI network anchored by a minimal on‑chain protocol. The protocol manages assets and incentives on Ethereum, while the off‑chain network performs the heavy lifting of transcoding and AI processing. Official documents separate these domains:
-
-On‑chain protocol – smart contracts hold ETH deposits from broadcasters and orchestrators; mint and distribute LPT staking tokens; issue probabilistic payment tickets; enforce staking, slashing and reward rules; and manage governance. The protocol does not transcode video or run AI. Its role is to coordinate payments and maintain trustless state.
-
-Off‑chain network – orchestrator nodes run Livepeer software to perform transcoding and AI workloads. They compete on price, quality and latency. Video/AI jobs and routing happen entirely off‑chain. Services like Livepeer Studio and community gateways sit on top of this layer.
-
-Bridge – broadcasters deposit ETH into the protocol and send probabilistic tickets with each segment. Orchestrators redeem winning tickets on‑chain for ETH fees, while the work itself is delivered off‑chain. LPT is not used to pay for services; it is only used for staking, delegation and governance.
-
-These boundaries ensure that the protocol remains lightweight and censorship‑resistant. Any proposed change must respect this separation-heavy compute must remain off‑chain, while financial rules and governance reside on‑chainU
-
-{/* */}
-
-
-
-
-
-
-
-
-
-
-
-{/* */}
-
-### Definitions
-
-**Livepeer Protocol**
-
-The protocol is the ruleset + on-chain logic governing:
-
-**Livepeer Network**
-
-The network is the actual running system of machines performing work:
-
-**Livepeer Actors**
-
-A Livepeer actor is any role or entity that participates in the Livepeer protocol or network and performs actions defined by the system.
-
-
-# Overview
-
-Livepeer is a full-stack platform for video streaming & AI. The video streaming software is underpinned by a network of actors that perform the work needed to compute, transcode & orchestrate video & AI jobs in the Livepeer network.
-
-The Livepeer Protocol is the underlying code that enforces the mechanisms and rules to ensure the reliability, cooperation and coordination of these decentralised actors.
-
-# Core Concepts
-
-## Livepeer Protocol
-
-The protocol is the ruleset + on-chain logic governing:
-
-- staking
-- delegation
-- inflation & rewards
-- orchestrator selection
-- slashing
-- probabilistic payments
-- verification rules
-
-The economic and coordination layer that enforces correct behavior.
-
-## Livepeer Network
-
-The network is the actual running system of machines performing work:
-
-- Orchestrators (GPU nodes)
-- Transcoders / Workers
-- Gateways
-- Broadcasters
-- Verification processes
-- Job routing
-- Real-time AI & video compute
-
-It is the live, operational decentralized GPU mesh running video + AI jobs.
-
-## Protocol vs Network
-
-| Layer | Description |
-| --------------------- | ----------------------------------------------------------------------------- |
-| **Livepeer Protocol** | On-chain crypto-economic incentives & coordination; staking; payments. |
-| **Livepeer Network** | Off-chain nodes performing real-time work (transcoding, inference, routing). |
-| **Relationship** | The network _runs_ the compute; the protocol _governs, secures, and pays_ it. |
-
-
-# On-chain vs Off-chain
-
-Livepeer protocol = Arbitrum One (L2)
-Livepeer token (LPT) = Ethereum mainnet (L1)
-Livepeer network (GPU nodes + gateways) = off-chain execution layer
-
-# Livepeer Actors
-
-A Livepeer actor is any role or entity that participates in the Livepeer protocol or network and performs actions defined by the system.
-In Livepeer architecture, “actor” is a formal category used to describe participants with distinct responsibilities, incentives, and interactions.
-Actors are fundamental to describing how the network functions end-to-end from a systems engineering perspective.
-
-Livepeer’s ecosystem involves both protocol actors (on-chain roles) and community actors (network participants and builders)
-
-INSERT LIVEPEER ACTOR DIAGRAM HERE \[THIS ONE LOOKS OLD (whitpaper)
-
-Actor diagram placeholder removed pending final approved asset.
diff --git a/v2/about/_workspace/archive/pre-pipeline-rewrite/economics.mdx b/v2/about/_workspace/archive/pre-pipeline-rewrite/economics.mdx
deleted file mode 100644
index 4e32aaed9..000000000
--- a/v2/about/_workspace/archive/pre-pipeline-rewrite/economics.mdx
+++ /dev/null
@@ -1,172 +0,0 @@
----
-title: Livepeer Protocol Economics
-sidebarTitle: Protocol Economics
-description: >-
- Learn how LPT, staking, inflation, rewards, fees, and payment flows shape the
- Livepeer protocol economy.
-pageType: concept
-keywords:
- - livepeer
- - about
- - livepeer protocol
- - livepeer protocol economics
- - protocol
- - economics
-'og:image': /snippets/assets/media/og-images/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: general
-lastVerified: 2026-03-17
-purpose: concept
----
-{/* This page describes:
-6. **Economics**
-
- * Tokenomics
- * Inflation model
- * Staking & delegation
- * Reward distribution
- * Slashing
- * Rounds
-
-
-*/}
-
-Livepeer uses both its native token - LPT, and Ethereum (ETH) to power its network and compensate actors for their contributions.
-The Livepeer protocol uses a dynamic inflation rate and stake-for-access model to ensure the network's security and functionality.
-
-We'll cover the LPT tokenomics and why delegating to orchestrators remains important even as inflation tapers off.
-
-## Money Flow: LPT Token Economics
-
-### 1. **Staking Flow (Delegators → Orchestrators)**
-
-**Step 1: Token Approval**
-Before bonding, delegators must approve the BondingManager to transfer their LPT tokens.
-
-**Step 2: Bonding**
-Delegators call `Bond(amount, orchestratorAddress)` which:
-- Transfers LPT from delegator to BondingManager
-- Updates orchestrator's delegated stake
-- Calculates pool position hints for gas optimisation
-- Updates the transcoder pool sorted by stake
-
-**Step 3: Orchestrator Registration**
-To become an orchestrator, a node must:
-- First bond LPT to itself
-- Call `Transcoder(rewardCut, feeShare)` with commission parameters
-- Register service URI via `SetServiceURI()`
-
-The transcoder pool maintains orchestrators sorted by delegated stake as a linked list, with hints optimizing insertions.
-
-### 2. **Reward Flow (Minter → Orchestrators → Delegators)**
-
-Each round, active orchestrators can call `Reward()` to mint inflationary tokens:
-
-**Reward Calculation Process**:
-1. Orchestrator calls `Reward()` on BondingManager
-2. BondingManager queries `CurrentMintableTokens()` from Minter
-3. Minter calculates: `mintable = inflation * totalSupply / bonded`
-4. Reward distributed proportionally to orchestrator's stake
-5. Orchestrator keeps their commission (rewardCut)
-6. Remaining rewards distributed to delegators proportionally
-
-**Claiming Earnings**:
-Delegators must call `ClaimEarnings(endRound)` to realize their accumulated rewards and fees from past rounds.
-
-### 3. **Payment Flow (Broadcasters → Orchestrators)**
-
-The payment system uses probabilistic micropayments to minimize on-chain transactions:
-
-**Step 1: Broadcaster Deposits**
-Broadcasters fund their account via `FundDepositAndReserve()`:
-- **Deposit**: Locked collateral (can't be used immediately)
-- **Reserve**: Available pool for ticket redemptions [14](#0-13)
-
-**Step 2: Off-Chain Ticket Creation**
-For each video segment processed:
-- Broadcaster creates a signed ticket with faceValue and winProb
-- Ticket sent off-chain to orchestrator via HTTP headers
-- Most tickets don't win (e.g., 1% win probability)
-
-**Step 3: Ticket Validation & Queuing**
-Orchestrator validates ticket:
-- Checks signature and expiration
-- Calculates if ticket wins using `recipientRand`
-- Winning tickets queued in local database
-- Tracks sender's MaxFloat (reserve - pending redemptions)
-
-**Step 4: On-Chain Redemption**
-When sufficient funds available:
-- Orchestrator calls `RedeemWinningTicket(ticket, sig, recipientRand)`
-- TicketBroker validates ticket against on-chain state
-- Transfers `faceValue` from broadcaster's reserve to orchestrator
-- Updates `claimedReserve` in BondingManager
-
-This achieves ~99% cost reduction vs. Per-segment on-chain payments while maintaining fair compensation through probabilistic expected value.
-
-### 4. **Fee Flow (Broadcasters → Orchestrators → Delegators)**
-
-Orchestrators earn fees from ticket redemptions:
-- Fees accumulate in orchestrator's earnings pool
-- Orchestrator keeps their commission (feeShare)
-- Remaining fees distributed to delegators
-- Delegators claim via `ClaimEarnings()`
-
-### 5. **Withdrawal Flows**
-
-**Unstaking (Delegators)**:
-1. Call `Unbond(amount)` - creates unbonding lock
-2. Wait `UnbondingPeriod` rounds (typically 7 rounds)
-3. Call `WithdrawStake(unbondingLockId)` - receive LPT back
-
-**Payment Withdrawal (Broadcasters)**:
-1. Call `Unlock()` on TicketBroker
-2. Wait unlock period
-3. Call `Withdraw()` - receive remaining deposit + reserve
-
-## Client Integration
-
-The go-livepeer client abstracts all contract interactions through the `LivepeerEthClient` interface: [15](#0-14)
-
-**Contract Address Resolution**:
-All contract addresses are dynamically discovered through the Controller registry using Keccak256 hashes of contract names. This enables contract upgrades without changing client code. [16](#0-15)
-
-## Gas Optimisation Strategies
-
-### 1. **Pool Hints**
-When bonding or calling reward, the client calculates "hints" (previous/next positions in the sorted transcoder pool) to enable O(1) insertions instead of O(n) searches on-chain. [17](#0-16)
-
-### 2. **Batch Operations**
-Multiple tickets can be created off-chain in batches, with only winning tickets requiring on-chain transactions.
-
-### 3. **Dynamic Gas Pricing**
-The client implements sophisticated gas price management, using 2x base fee with user-specified ceilings to balance confirmation speed and cost. [18](#0-17)
-
-## Summary: Complete Money Flow
-
-1. **Token holders** approve and bond LPT → **BondingManager** (staking)
-2. **Minter** mints new LPT → **BondingManager** → **Orchestrators** (inflation rewards)
-3. **Orchestrators** distribute rewards → **Delegators** (minus commission)
-4. **Broadcasters** deposit LPT → **TicketBroker** (payment reserves)
-5. **Orchestrators** redeem tickets → receive LPT from **TicketBroker** (fees)
-6. **Orchestrators** distribute fees → **Delegators** (minus commission)
-7. **Delegators** claim earnings from **BondingManager** (accumulated rewards + fees)
-
-This creates a circular economy where:
-- Staking secures the network and earns inflation rewards
-- Active orchestrators earn fees from broadcasters
-- Delegators participate in rewards without running infrastructure
-- Probabilistic payments enable cost-efficient micropayments
-- All flows tracked on-chain with minimal gas overhead
-
-## Notes
-
-- The contracts are deployed on Ethereum mainnet (and Arbitrum for L2)
-- Contract addresses are stored in the Controller registry for upgradeability
-- All token operations use standard ERC20 approval patterns
-- The system supports both L1 and L2 deployments with backward compatibility
-- Round-based operations ensure coordinated protocol upgrades and state transitions
-- The probabilistic payment system reduces on-chain transactions by ~99% while maintaining fair expected value for all parties
diff --git a/v2/about/_workspace/archive/pre-pipeline-rewrite/network-overview.mdx b/v2/about/_workspace/archive/pre-pipeline-rewrite/network-overview.mdx
deleted file mode 100644
index a6cee64b2..000000000
--- a/v2/about/_workspace/archive/pre-pipeline-rewrite/network-overview.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Livepeer Network Overview
-sidebarTitle: Network Overview
-description: An overview of the Livepeer network and its components.
-keywords:
- - livepeer
- - about
- - livepeer network
- - network overview
- - network
- - overview
-'og:image': /snippets/assets/media/og-images/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-pageType: overview
-audience: general
-lastVerified: 2026-03-17
-purpose: overview
----
-
-
-Livepeer’s core protocol defines the conditions for the network to provide real-time video and AI compute services. The network is the execution layer. It is the actual running system of machines performing work to execute the product vision.
-- Gateways (broadcasters) submit jobs (video or AI) into the network from applications or services
-- Orchestrator nodes (stakers) process and compute the work, and
-- Delegators stake tokens to support governance and security of the network
-
-## Network Components
-
-### Node Types
-The protocol implementation defines multiple node roles (not all are formal network actors) that cooperatively execute on the protocol to provide the desired network functions.
-
-- **Broadcaster Node**: Centers on LivepeerServer managing rtmpConnections and BroadcastSessionsManager
-- **Gateway Node**: Adds AISessionManager and AI HTTP handlers on top of broadcaster functionality
-- **Orchestrator Node**: Uses the orchestrator struct with SegmentChans for job distribution and Recipient for payments
-- **Transcoder Node**: RemoteTranscoderManager coordinates local or remote transcoding via LocalTranscoder
-- **AI Worker Node**: RemoteAIWorkerManager manages Docker containers running AI models
-
-### Core Components
-- LivepeerNode: An interface node implemented by all other node types in the network (gateway/broadcaster, orchestrator, transcoder)
-- Media Server (`LivpeerServer`): The LivepeerServer manages media processing and serves HTTP/RTMP endpoints, providing
- - RTMP ingestion for live streams
- - HTTP push for video segments
- - HLS playback endpoints
- - Management of active connections
-- Broadcast Sessions Manager:
-- Orchestrator
-- Transcoder
-- AI Gateway
-- AI Workers
diff --git a/v2/about/concepts/actors.mdx b/v2/about/concepts/actors.mdx
deleted file mode 100644
index 41f7834a9..000000000
--- a/v2/about/concepts/actors.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Livepeer Actors
-sidebarTitle: Livepeer Actors
-description: >-
- A high-level introduction to the key concepts workings of the Livepeer open,
- on-demand AI & Media infrastructure substrate and the distributed
- crypto-primitive coordination system.
-keywords:
- - livepeer
- - about
- - core concepts
- - mental model
- - introduction
- - key
- - architecture
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
----
-
-## Actor Overview
-
-Livepeer involves multiple actors, both on-chain (protocol) and off-chain (community).
-
-Here’s a breakdown of key roles:
-
-- **Orchestrator**: A bonded node operator that claims work on-chain. Orchestrators maintain active LPT stake, set fee-sharing percentages, and call the on-chain reward function each round. They earn ETH fees from broadcasters and LPT from inflation. (Messari: “Orchestrators (node operators) route transcoding & AI jobs… earning ETH fees and LPT rewards”.)
-- **Transcoder** / **Worker**: A compute node (often a GPU) that performs the actual encoding or inference. Workers do not hold stake themselves; they operate under an Orchestrator.
-- **Gateway** (Broadcaster): A stateless demand-side node. Gateways submit video or AI jobs to the network and pay the node that completes the work. They effectively bridge an input stream into Livepeer, handling micropayment tickets on-chain.
-- **Delegator**: A token holder who stakes LPT behind one or more orchestrators. Delegators strengthen network security and decentralization. In exchange, they receive a portion of the node’s rewards (both mint emissions and usage fees) according to their stake. As one Livepeer blog notes, “Delegators earn a share of both token emissions (while they last) and usage-based fees”.
-- **Livepeer Foundation**: A non-profit entity formed to guide ecosystem growth. The Foundation coordinates long-term strategy and funding, runs community programs (like advisory boards), and helps align core protocol development with the open-source community.
-- **Developers & Builders**: Software teams building on Livepeer. This includes decentralized video apps (e.g. on Web3 social networks) and infrastructure tools. Messari notes Livepeer is used by projects ranging from decentralized streaming platforms to tokenized music apps.
-
-AI Artists & Content Creators: Performers and creators who use Livepeer’s tools (like Daydream) to produce content. For example, MetaDJ used Daydream to let fans shape the live visuals in real time. Any streamer, musician, or videographer can leverage the network for novel AI-enhanced experiences.
-
-Gateway Operators: Organizations running public Livepeer gateway services. For example, Livepeer Cloud (a community-run gateway) and Livepeer Studio (a production-grade API gateway) provide easy on-ramps to the network. They ensure reliable, scalable access for creators and apps.
-
-Special Purpose Entities (SPEs): Community-approved teams funded by the on-chain treasury. SPEs tackle public goods for Livepeer (e.g. Building dev tools, infrastructure). For example, Livepeer’s ecosystem has active SPEs like LiveInfra and LISAR working on network upgrades and on-ramp infrastructure.
diff --git a/v2/about/concepts/core-concepts.mdx b/v2/about/concepts/core-concepts.mdx
index 0d76608a8..47ee86c6a 100644
--- a/v2/about/concepts/core-concepts.mdx
+++ b/v2/about/concepts/core-concepts.mdx
@@ -1,148 +1,137 @@
---
-title: 'Livepeer Core Concepts'
-sidebarTitle: 'Core Concepts'
+title: Livepeer Core Concepts
+sidebarTitle: Livepeer Core Concepts
description: >-
- The three-zone architecture, network actors, compute types, economic model, and governance of the Livepeer decentralised AI and video compute network.
+ A high-level introduction to the key concepts and architecture of the Livepeer
+ Real-time AI & Video Network
pageType: concept
-audience: community
-purpose: explain
keywords:
- livepeer
+ - about
- core concepts
- - protocol
- - network
- - actors
- - orchestrators
- - gateways
- - delegators
- - economics
- - governance
-'og:image': /snippets/assets/site/og-image/en/about.png
-'og:image:alt': Livepeer Docs social preview image for About
+ - livepeer core concepts
+ - introduction
+ - key
+ - architecture
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
'og:image:width': 1200
'og:image:height': 630
-status: current
-lastVerified: 2026-04-07
+audience: general
+lastVerified: 2026-03-17
+purpose: concept
---
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
-import { StyledTable, TableRow, TableCell } from '/snippets/components/wrappers/tables/Tables.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'
-
- Livepeer separates on-chain coordination (Protocol), off-chain execution (Network), and developer-facing products (Platform) into three distinct zones. Each zone has a hard boundary: the protocol governs, the network executes, the platform exposes.
-
+import Protocol from "/snippets/composables/pages/about/concepts/protocol.mdx"
+import Network from "/snippets/composables/pages/about/concepts/network.mdx"
+import Actors from "/snippets/composables/pages/about/concepts/actors.mdx"
----
+### Overview and separation
+
+Livepeer is designed as a modular video/AI network anchored by a minimal on‑chain protocol. The protocol manages assets and incentives on Ethereum, while the off‑chain network performs the heavy lifting of transcoding and AI processing. Official documents separate these domains:
+
+On‑chain protocol – smart contracts hold ETH deposits from broadcasters and orchestrators; mint and distribute LPT staking tokens; issue probabilistic payment tickets; enforce staking, slashing and reward rules; and manage governance. The protocol does not transcode video or run AI. Its role is to coordinate payments and maintain trustless state.
+
+Off‑chain network – orchestrator nodes run Livepeer software to perform transcoding and AI workloads. They compete on price, quality and latency. Video/AI jobs and routing happen entirely off‑chain. Services like Livepeer Studio and community gateways sit on top of this layer.
-Livepeer is a decentralised AI and video compute network. Its architecture is divided into three zones that interact without overlapping. The Protocol secures and coordinates. The Network executes compute jobs. The Platform exposes the network's capabilities through APIs, SDKs, and managed services.
+Bridge – broadcasters deposit ETH into the protocol and send probabilistic tickets with each segment. Orchestrators redeem winning tickets on‑chain for ETH fees, while the work itself is delivered off‑chain. LPT is not used to pay for services; it is only used for staking, delegation and governance.
-Understanding these boundaries is what separates the mental model from the deep-dive pages in the protocol/ and network/ sections. This page names each zone, its actors, its compute types, and the economic and governance model that holds it together.
+These boundaries ensure that the protocol remains lightweight and censorship‑resistant. Any proposed change must respect this separation-heavy compute must remain off‑chain, while financial rules and governance reside on‑chainU
-
+
+
+
+
+
+
+
+
-## The three zones
+
+{/* */}
-The **Protocol** is the on-chain coordination, security, and economic layer. Smart contracts deployed on Arbitrum One govern staking, delegation, inflation, reward distribution, probabilistic micropayments, and governance. The protocol sets the rules that all other participants follow. It does not run compute, route jobs, or interact with video data.
+### Definitions
-The **Network** is the execution layer - the running system of GPU nodes and routing logic that performs video transcoding and AI inference. Orchestrators, gateways, and transcoders operate entirely off-chain. The network follows the rules the protocol establishes and settles payment for completed work via on-chain ticket redemption.
+**Livepeer Protocol**
-The **Platform** is the product and developer interface layer. Managed gateways, APIs, SDKs, and community products (Livepeer Studio, Daydream, Streamplace) sit here. Platform services abstract protocol and network complexity into stable developer primitives. They are not part of the protocol and are not part of the network - they are opinions about how to expose the network's capabilities.
+The protocol is the ruleset + on-chain logic governing:
-
-
-
- Zone
- Runs on
- Responsibility
- Does NOT
-
-
-
-
- **Protocol**
- Arbitrum One (on-chain)
- Governance, staking, payments, inflation
- Run compute or route jobs
-
-
- **Network**
- Off-chain (GPU nodes)
- Execute video and AI workloads
- Manage economics or issue tokens
-
-
- **Platform**
- Applications and APIs
- Expose network capabilities to developers
- Govern or execute directly
-
-
-
+**Livepeer Network**
-INSERT LIVEPEER ACTOR DIAGRAM HERE \[THIS ONE LOOKS OLD (whitpaper)
-
-
- The full mechanism detail: staking, delegation, probabilistic payments, slashing, and governance.
-
-
- The execution layer: orchestrators, gateways, job routing, and the marketplace.
-
-
- How ETH fees and LPT inflation flow through the system and who earns each.
-
-
- Stake-weighted voting, LIPs, the Governor contract, and the treasury.
-
-
+Actor diagram placeholder removed pending final approved asset.
diff --git a/v2/about/index.mdx b/v2/about/index.mdx
index 8b45d0a78..00b10e28c 100644
--- a/v2/about/index.mdx
+++ b/v2/about/index.mdx
@@ -3,7 +3,6 @@ title: 'About Index'
sidebarTitle: 'About Index'
description: 'Generated table of contents for docs pages under v2/about.'
pageType: navigation
-audience: community
purpose: orient
lifecycleStage: discover
keywords: ['livepeer', 'generated index', 'table of contents', 'v2/about']
diff --git a/v2/about/network/demand-side.mdx b/v2/about/network/demand-side.mdx
new file mode 100644
index 000000000..255a7470f
--- /dev/null
+++ b/v2/about/network/demand-side.mdx
@@ -0,0 +1,27 @@
+---
+title: Livepeer Demand Side
+sidebarTitle: Demand Side
+description: Learn about the Livepeer demand side.
+keywords:
+ - livepeer
+ - about
+ - livepeer network
+ - demand side
+ - demand
+ - side
+ - learn
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
+'og:image:type': image/png
+'og:image:width': 1200
+'og:image:height': 630
+---
+
+This page describes:
+7. **Demand Side**
+
+ * Gateway role
+ * Job submission
+ * Pricing
+ * Service discovery
+ * Marketplace interaction
diff --git a/v2/about/network/fee-flow.mdx b/v2/about/network/fee-flow.mdx
new file mode 100644
index 000000000..4bfa7451f
--- /dev/null
+++ b/v2/about/network/fee-flow.mdx
@@ -0,0 +1,25 @@
+---
+title: Livepeer Fee Flow
+sidebarTitle: Fee Flow
+description: Learn about the Livepeer fee flow.
+keywords:
+ - livepeer
+ - about
+ - livepeer network
+ - fee flow
+ - fee
+ - flow
+ - learn
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
+'og:image:type': image/png
+'og:image:width': 1200
+'og:image:height': 630
+---
+
+This page describes:
+8. **Fee Flow**
+ * Job pricing
+ * Payment model
+ * Revenue sharing
+ * Incentive alignment
diff --git a/v2/about/network/job-lifecycle.mdx b/v2/about/network/job-lifecycle.mdx
index 1324e9841..114c2ec28 100644
--- a/v2/about/network/job-lifecycle.mdx
+++ b/v2/about/network/job-lifecycle.mdx
@@ -2,10 +2,10 @@
title: Livepeer Job Lifecycle
sidebarTitle: Job Lifecycle
description: >-
- The end-to-end compute job modelled as a state machine. Livepeer’s compute is
- segment-oriented, so the lifecycle covers stream sessions, per-segment
- processing, continuous ticket-based payment settlement, and periodic reward
- calls.
+ This page describes the end-to-end “compute job” as a state machine. Since
+ Livepeer’s compute is segment-oriented, the lifecycle is modelled at the level
+ of a stream session and per-segment processing, with payment settlement
+ occurring continuously via tickets and periodically via reward calls.
pageType: concept
keywords:
- livepeer
diff --git a/v2/about/network/livepeer-actors/end-users.mdx b/v2/about/network/livepeer-actors/end-users.mdx
index 8fe4c2a69..08068b633 100644
--- a/v2/about/network/livepeer-actors/end-users.mdx
+++ b/v2/about/network/livepeer-actors/end-users.mdx
@@ -2,9 +2,6 @@
title: Builders and End Users
sidebarTitle: Builders & End Users
description: 'How developers, product teams, and users consume Livepeer-powered services.'
-pageType: concept
-audience: community
-purpose: explain
keywords:
- livepeer
- about
diff --git a/v2/about/network/livepeer-actors/orchestrators.mdx b/v2/about/network/livepeer-actors/orchestrators.mdx
index 25b43a753..2434496c9 100644
--- a/v2/about/network/livepeer-actors/orchestrators.mdx
+++ b/v2/about/network/livepeer-actors/orchestrators.mdx
@@ -4,9 +4,6 @@ sidebarTitle: Orchestrators
description: >-
How orchestrator operators provide supply-side execution capacity and economic
participation in Livepeer.
-pageType: concept
-audience: community
-purpose: explain
keywords:
- livepeer
- about
diff --git a/v2/about/network/overview.mdx b/v2/about/network/overview.mdx
index e107b0eb3..1a8a886b7 100644
--- a/v2/about/network/overview.mdx
+++ b/v2/about/network/overview.mdx
@@ -1,107 +1,52 @@
---
-title: 'Livepeer Network Overview'
-sidebarTitle: 'Network Overview'
-description: >-
- The Livepeer network is the execution layer, the global system of GPU nodes that performs video transcoding and AI inference under protocol coordination.
-pageType: concept
-audience: community
-purpose: explain
+title: Livepeer Network Overview
+sidebarTitle: Network Overview
+description: An overview of the Livepeer network and its components.
keywords:
- livepeer
+ - about
+ - livepeer network
+ - network overview
- network
- overview
- - orchestrators
- - gateways
- - execution layer
- - video transcoding
- - AI inference
-'og:image': /snippets/assets/site/og-image/en/about.png
-'og:image:alt': Livepeer Docs social preview image for About
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
'og:image:width': 1200
'og:image:height': 630
-status: current
-lastVerified: 2026-04-07
+pageType: overview
+audience: general
+lastVerified: 2026-03-17
+purpose: overview
---
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
-import { StyledTable, TableRow, TableCell } from '/snippets/components/wrappers/tables/Tables.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'
-
- The network is the execution layer. It is the actual running system of GPU nodes that performs video transcoding and AI inference jobs - the protocol sets the rules and the network runs the work.
-
+Livepeer’s core protocol defines the conditions for the network to provide real-time video and AI compute services. The network is the execution layer. It is the actual running system of machines performing work to execute the product vision.
+- Gateways (broadcasters) submit jobs (video or AI) into the network from applications or services
+- Orchestrator nodes (stakers) process and compute the work, and
+- Delegators stake tokens to support governance and security of the network
----
-
-The Livepeer network is the off-chain execution layer of the Livepeer ecosystem. It is the live, operational system of machines that accepts compute jobs, routes them to GPU operators, delivers results, and settles payment. It is distinct from the protocol, which governs the network through on-chain coordination, staking, and economic rules.
-
-The network does not issue tokens, does not set inflation rates, and does not manage governance. Those responsibilities belong to the protocol. The network's job is to execute compute reliably, at low latency, and at competitive cost.
-
-
-
- Orchestrators, gateways, and transcoders - roles, responsibilities, and how they interact.
-
-
- How a compute job moves from submission to execution to payment settlement.
-
-
- How orchestrators are discovered, selected, and priced.
-
-
- The on-chain governance, staking, and economic rules that the network operates under.
-
-
diff --git a/v2/about/network/scaling.mdx b/v2/about/network/scaling.mdx
new file mode 100644
index 000000000..ca63fd6f4
--- /dev/null
+++ b/v2/about/network/scaling.mdx
@@ -0,0 +1,26 @@
+---
+title: Livepeer Scaling
+sidebarTitle: Scaling
+description: Learn about the Livepeer scaling.
+keywords:
+ - livepeer
+ - about
+ - livepeer network
+ - scaling
+ - learn
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
+'og:image:type': image/png
+'og:image:width': 1200
+'og:image:height': 630
+---
+
+This page describes:
+9. **Performance and Scaling**
+
+ * Network throughput
+ * Latency
+ * Scalability
+ * Bottlenecks
+ * Future scaling
+ * Points to explorer metrics.
diff --git a/v2/about/network/supply-side.mdx b/v2/about/network/supply-side.mdx
new file mode 100644
index 000000000..a6850cd3d
--- /dev/null
+++ b/v2/about/network/supply-side.mdx
@@ -0,0 +1,26 @@
+---
+title: Livepeer Supply Side
+sidebarTitle: Supply Side
+description: Learn about the Livepeer supply side.
+keywords:
+ - livepeer
+ - about
+ - livepeer network
+ - supply side
+ - supply
+ - side
+ - learn
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
+'og:image:type': image/png
+'og:image:width': 1200
+'og:image:height': 630
+---
+
+This page describes:
+5. **Supply Side**
+
+ * GPU operators
+ * Pools
+ * Hardware requirements
+ * Performance metrics
diff --git a/v2/about/protocol/design-philosophy.mdx b/v2/about/protocol/design-philosophy.mdx
index aa01138ac..816b5a1a7 100644
--- a/v2/about/protocol/design-philosophy.mdx
+++ b/v2/about/protocol/design-philosophy.mdx
@@ -1,119 +1,53 @@
---
-title: 'Protocol Design Philosophy'
-sidebarTitle: 'Design Philosophy'
-description: >-
- The engineering trade-offs behind Livepeer protocol design, including stake-as-security, dynamic inflation, probabilistic micropayments, protocol-network separation, and the Arbitrum deployment.
-pageType: concept
-audience: community
-purpose: explain
+title: Protocol Design Philosophy
+sidebarTitle: Design Philosophy
+description: Why the Livepeer protocol uses staking, inflation, probabilistic payments, and a strict boundary between protocol and execution network.
keywords:
- livepeer
- protocol
- design philosophy
- - trade-offs
- - stake
+ - probabilistic payments
- inflation
- - probabilistic micropayments
- - Arbitrum
- - governance
-'og:image': /snippets/assets/site/og-image/en/about.png
+ - staking
+'og:image': /snippets/assets/media/og-images/en/about.png
'og:image:alt': Livepeer Docs social preview image for About
'og:image:type': image/png
'og:image:width': 1200
'og:image:height': 630
-status: current
-lastVerified: 2026-04-07
+pageType: concept
+audience: community
+purpose: explain
+status: draft
+lastVerified: '2026-04-05'
---
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'
-
-
- The Livepeer protocol makes design choices optimised for permissionless participation, minimal on-chain overhead, and long-run sustainability. Each choice carries a trade-off. This page states those trade-offs directly.
-
-
----
-
-The Livepeer protocol is the product of specific engineering decisions made against a set of goals: permissionless access, economic security, censorship resistance, and the ability to coordinate a global GPU network without a central operator. Each mechanism in the protocol reflects a deliberate trade-off between these goals. This page explains the reasoning behind the five most significant design choices.
-
-It is written for researchers, protocol contributors, and founders doing technical due diligence. It assumes familiarity with the protocol mechanisms covered in
-
- How staking, delegation, probabilistic payments, and slashing work in detail.
+
+ The current entry page for protocol scope and responsibilities.
-
- ETH fee flows and LPT inflation rewards: who earns each and how they are distributed.
+
+ The current page for staking, rewards, and payment primitives.
-
- Stake-weighted voting, LIPs, the Governor contract, and the treasury.
+
+ The clearest current explanation of money flow and incentives.
-
- The on-chain contract architecture: Controller, BondingManager, TicketBroker, Minter, and more.
+
+ The current page for how protocol changes are authorised.
diff --git a/v2/about/protocol/economics.mdx b/v2/about/protocol/economics.mdx
index 72693b767..4e32aaed9 100644
--- a/v2/about/protocol/economics.mdx
+++ b/v2/about/protocol/economics.mdx
@@ -1,11 +1,10 @@
---
-title: 'Livepeer Protocol Economics'
-sidebarTitle: 'Protocol Economics'
+title: Livepeer Protocol Economics
+sidebarTitle: Protocol Economics
description: >-
- How LPT and ETH flow through the Livepeer protocol: staking, inflation rewards, usage fees, and the economic model governing network participation.
+ Learn how LPT, staking, inflation, rewards, fees, and payment flows shape the
+ Livepeer protocol economy.
pageType: concept
-audience: community
-purpose: explain
keywords:
- livepeer
- about
@@ -13,153 +12,161 @@ keywords:
- livepeer protocol economics
- protocol
- economics
- - inflation
- - staking
- - fees
-'og:image': /snippets/assets/site/og-image/en/about.png
-'og:image:alt': Livepeer Docs social preview image for About
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
'og:image:width': 1200
'og:image:height': 630
-status: current
-lastVerified: 2026-04-07
+audience: general
+lastVerified: 2026-03-17
+purpose: concept
---
+{/* This page describes:
+6. **Economics**
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
-import { StyledTable, TableRow, TableCell } from '/snippets/components/wrappers/tables/Tables.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'
+ * Tokenomics
+ * Inflation model
+ * Staking & delegation
+ * Reward distribution
+ * Slashing
+ * Rounds
-
- Livepeer has two income streams: ETH fees from usage, and LPT inflation rewards from the protocol. Both flow through orchestrators to delegators. Fee revenue tracks demand. Inflation rewards bootstrap participation while demand grows.
-
----
-
-Livepeer uses both its native token (LPT) and Ethereum (ETH) to power its network and compensate actors for their contributions. ETH pays for compute work performed. LPT coordinates staking, delegation, governance, and inflation-based participation incentives.
-
-The two income streams are distinct in origin and denomination. Fee revenue in ETH reflects actual network usage: video transcoding and AI inference demand. Inflation rewards in LPT reflect the protocol's bootstrapping phase, sustaining security and participation while fee revenue grows toward sufficiency. Protocol parameters governing inflation are adjusted through governance — verify current values at [explorer.livepeer.org](https://explorer.livepeer.org).
-
-
-
- Staking, delegation, probabilistic payments, and round mechanics in full detail.
-
-
- LPT's role in staking, governance, and the L1-to-Arbitrum bridge.
-
-
- How LIPs are proposed, voted on, and how protocol parameters change.
-
-
- The engineering trade-offs behind inflation design, probabilistic payments, and protocol-network separation.
-
-
+- The contracts are deployed on Ethereum mainnet (and Arbitrum for L2)
+- Contract addresses are stored in the Controller registry for upgradeability
+- All token operations use standard ERC20 approval patterns
+- The system supports both L1 and L2 deployments with backward compatibility
+- Round-based operations ensure coordinated protocol upgrades and state transitions
+- The probabilistic payment system reduces on-chain transactions by ~99% while maintaining fair expected value for all parties
diff --git a/v2/about/protocol/governance-model.mdx b/v2/about/protocol/governance-model.mdx
index 5951a5126..68ba1d041 100644
--- a/v2/about/protocol/governance-model.mdx
+++ b/v2/about/protocol/governance-model.mdx
@@ -2,10 +2,10 @@
title: Livepeer Governance Model
sidebarTitle: Governance Model
description: >-
- The on-chain governance model for the Livepeer protocol: a permissionless,
- transparent, community-driven framework for upgrades, parameter changes, and
- treasury stewardship. Covers key actors, processes, and mechanisms that drive
- coordination and ecosystem growth.
+ This page describes the on-chain governance model which provides a
+ permissionless, transparent, and community-driven framework for upgrading and
+ governing the Livepeer protocol. It touches on the key actors, processes and
+ mechanisms that drive coordination and growth of the Livepeer ecosystem.
pageType: concept
keywords:
- livepeer
diff --git a/v2/about/protocol/overview.mdx b/v2/about/protocol/overview.mdx
index 4af7a13d9..75ed7681f 100644
--- a/v2/about/protocol/overview.mdx
+++ b/v2/about/protocol/overview.mdx
@@ -2,10 +2,10 @@
title: Protocol Overview
sidebarTitle: Overview
description: >-
- Design, contract architecture, staking and reward mechanisms, incentive
- alignment, and governance model of the on-chain Livepeer Protocol. Covers how
- work is coordinated, secured, and rewarded, and how upgrades are proposed and
- implemented.
+ This section outlines the design, contract architecture, staking & reward
+ mechanisms, incentive alignment and governance model of the on-chain Livepeer
+ Protocol that governs how work is coordinated, secured and rewarded and how
+ upgrades are proposed and implemented.
keywords:
- livepeer
- about
diff --git a/v2/about/protocol/treasury.mdx b/v2/about/protocol/treasury.mdx
index b6506a86b..49b210290 100644
--- a/v2/about/protocol/treasury.mdx
+++ b/v2/about/protocol/treasury.mdx
@@ -2,9 +2,8 @@
title: Livepeer Treasury
sidebarTitle: Treasury
description: >-
- How the Livepeer treasury accumulates funds, how disbursements are authorised
- through governance, and how the treasury’s role is evolving across the
- protocol’s roadmap.
+ This page outlines how the treasury accumulates funds, how disbursements are
+ authorised, and how its role is evolving across the protocol’s roadmap.
pageType: concept
keywords:
- livepeer
diff --git a/v2/about/resources/compendium/livepeer-glossary.mdx b/v2/about/resources/compendium/livepeer-glossary.mdx
index 821ba2373..52f0b8d78 100644
--- a/v2/about/resources/compendium/livepeer-glossary.mdx
+++ b/v2/about/resources/compendium/livepeer-glossary.mdx
@@ -11,7 +11,7 @@ keywords:
- glossary
- comprehensive
- terms
-'og:image': /snippets/assets/site/og-image/fallback.png
+'og:image': /snippets/assets/media/og-images/fallback.png
'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
'og:image:width': 1200
diff --git a/v2/about/resources/knowledge-hub/gateways-vs-orchestrators.mdx b/v2/about/resources/knowledge-hub/gateways-vs-orchestrators.mdx
index 095c63fb5..6bb1f83b4 100644
--- a/v2/about/resources/knowledge-hub/gateways-vs-orchestrators.mdx
+++ b/v2/about/resources/knowledge-hub/gateways-vs-orchestrators.mdx
@@ -2,13 +2,10 @@
title: 'Gateways Vs. Orchestrators: What’s the Difference?'
sidebarTitle: Gateways Vs. Orchestrators
description: >-
- Livepeer uses two core node types, Gateways and Orchestrators, that work
+ Livepeer uses two core node types-**Gateways** and **Orchestrators**-that work
together to provide real-time AI video compute at scale. Although closely
- connected, they serve entirely different purposes in the decentralised compute
- marketplace.
-pageType: resource
-audience: community
-purpose: explain
+ connected, they serve entirely different purposes. This page breaks down how
+ they differ and why both roles matter for a decentralized compute marketplace.
keywords:
- livepeer
- about
diff --git a/v2/about/resources/reference/technical-roadmap.mdx b/v2/about/resources/reference/technical-roadmap.mdx
index 2b6253f9e..2cb26bca7 100644
--- a/v2/about/resources/reference/technical-roadmap.mdx
+++ b/v2/about/resources/reference/technical-roadmap.mdx
@@ -1,157 +1,25 @@
---
-title: 'Technical Roadmap'
-sidebarTitle: 'Technical Roadmap'
-description: >-
- The Livepeer Foundation three-phase roadmap, current initiatives, and where to track ecosystem progress.
-pageType: reference
-audience: community
+description: Review the current Livepeer roadmap posts covering network and product direction.
purpose: reference
+pageType: reference
+title: "Technical Roadmap"
keywords:
- livepeer
- - roadmap
+ - about
+ - resources
- technical roadmap
- - foundation
- - cascade
- - AI inference
- - SPE
- - governance
-'og:image': /snippets/assets/site/og-image/en/about.png
-'og:image:alt': Livepeer Docs social preview image for About
+ - roadmap
+ - https
+ - introducing
+'og:image': /snippets/assets/media/og-images/fallback.png
+'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
'og:image:width': 1200
'og:image:height': 630
-status: current
-lastVerified: 2026-04-07
----
-
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
-import { StyledTable, TableRow, TableCell } from '/snippets/components/wrappers/tables/Tables.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { CenteredContainer } from '/snippets/components/wrappers/containers/Containers.jsx'
-
-
- The Livepeer ecosystem is guided by the Cascade vision: establishing Livepeer as the leading AI infrastructure for real-time video. The Foundation's roadmap executes that vision across three phases from 2025 to 2028 and beyond.
-
-
+audience: general
+lastVerified: 2026-03-17
---
+Use these roadmap posts to review the current Livepeer network vision and product direction:
-The Livepeer Foundation published the Cascade vision in late 2024, defining the project's direction toward real-time AI video infrastructure. A November 2025 update refined that vision as early validation - AI inference fee growth of 3x year-on-year, with over 72% of fee revenue now driven by AI workloads - confirmed the direction. The roadmap below reflects the Foundation's public planning as of early 2026.
-
-All protocol parameter values referenced in this page (inflation rate, bonding rate target, active set size) are governance-controlled and change between rounds. Verify current values at [explorer.livepeer.org](https://explorer.livepeer.org).
-
-
-
-
- Phase
- Approximate timeframe
- Focus
-
-
-
-
- **Phase 1 - Foundation**
- 2025
- Establish AI subnet, initial SPE structure, core infrastructure hardening
-
-
- **Phase 2 - Scaling**
- 2026-2027
- Grow AI demand, diversify compute supply, expand gateway ecosystem, close latency gap with centralised alternatives
-
-
- **Phase 3 - Decentralisation**
- 2028 and beyond
- Reduce Foundation operational dependency, full community governance of key infrastructure decisions
-
-
-
-
-
-
-
- Source
- What it tracks
- URL
-
-
-
-
- **Livepeer Explorer**
- On-chain metrics: bonding rate, inflation rate, active set, round data, fee revenue
- [explorer.livepeer.org](https://explorer.livepeer.org)
-
-
- **Livepeer Forum**
- Governance proposals (LIPs), SPE retrospectives, ecosystem discussions
- [forum.livepeer.org](https://forum.livepeer.org)
-
-
- **go-livepeer releases**
- Software releases, AI pipeline additions, bug fixes
- [github.com/livepeer/go-livepeer/releases](https://github.com/livepeer/go-livepeer/releases)
-
-
- **ai-worker releases**
- AI model support updates, inference worker changes
- [github.com/livepeer/ai-worker/releases](https://github.com/livepeer/ai-worker/releases)
-
-
- **Foundation blog**
- Vision updates, SPE announcements, ecosystem milestones
- [blog.livepeer.org](https://blog.livepeer.org)
-
-
- **Messari reports**
- Quarterly network performance analysis, fee trends, network health
- [messari.io](https://messari.io) (search Livepeer)
-
-
-
-
-
-
- How inflation, fees, and rewards work and what the current economic state of the network is.
-
-
- How LIPs are proposed, voted on, and implemented.
-
-
- The top-level introduction to Livepeer's mission, history, and network structure.
-
-
- The engineering trade-offs behind the protocol's core mechanisms.
-
-
+- https://blog.livepeer.org/introducing-livepeer-cascade-a-vision-for-livepeers-future-in-the-age-of-real-time-ai-video/
+- https://blog.livepeer.org/a-real-time-update-to-the-livepeer-network-vision/
diff --git a/v2/about/resources/x-deprecated/livepeer-glossary.mdx b/v2/about/resources/x-deprecated/livepeer-glossary.mdx
deleted file mode 100644
index 52f0b8d78..000000000
--- a/v2/about/resources/x-deprecated/livepeer-glossary.mdx
+++ /dev/null
@@ -1,422 +0,0 @@
----
-title: Livepeer Glossary
-sidebarTitle: Livepeer Glossary
-description: >-
- A comprehensive glossary of terms used in the Livepeer Real-time AI & Video
- Network
-keywords:
- - livepeer
- - resources
- - livepeer glossary
- - glossary
- - comprehensive
- - terms
-'og:image': /snippets/assets/media/og-images/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-pageType: glossary
-audience: general
-lastVerified: 2026-03-17
-purpose: glossary
----
-
-
-Terms (Actors & Network)
-
-- Gateway
-- Orchestrator
-- Delegator
-- Developer
--
-
-Terms (web3)
-
-- DePIN
-- LPT
-- ETH
--
-
-Terms (video)
-
-- Transcoding
-- Ingest
-- Delivery
-- Streaming
--
-
-Terms (AI)
-
-- Inference
-- Model
-- Pipeline
-- World Model
-- Agent
-
-Terms (Other)
-
--
-
-Terms not verified, brainstorm list only
-
-# Livepeer Core Terms
-
-### Livepeer Protocol
-
-The protocol is the ruleset + on-chain logic governing:
-
-- staking
-- delegation
-- inflation & rewards
-- orchestrator selection
-- slashing
-- probabilistic payments
-- verification rules
-
-The economic and coordination layer that enforces correct behavior.
-
-### Livepeer Network
-
-The network is the actual running system of machines performing work:
-
-- Orchestrators (GPU nodes)
-- Transcoders / Workers
-- Gateways
-- Broadcasters
-- Verification processes
-- Job routing
-- Real-time AI & video compute
-
-It is the live, operational decentralized GPU mesh running video + AI jobs.
-
-### Protocol Actor
-
-Protocol Actors are the main participants in the protocol who make up the core functions of th~~e network~~ (wrong).
-Protocol Actors include gateways, orchestrators, and delegators.
-
-### Livepeer Actor
-
-A Livepeer actor is a participant in the protocol or network-human or machine-that performs a defined role such as submitting jobs, providing compute, verifying work, or securing the system.
-
-### Network Participant
-
-Same as Protocol Actor (..?)
-
-### Livepeer Ecosystem
-
-### Ecosystem Partner
-
-A complimentary company working with Livepeer (for example: Storage, Security).
-
-### Developer Platform
-
-An abstraction layer on the livepeer protocol that provides tools and services for developers to use & build applications on top of Livepeer. Examples include Livepeer Studio, Daydream, and Streamplace.
-
-###
-
-# Actors & Network Roles
-
-### **Gateway**
-
-A _gateway_ is a Livepeer node operated by a user or organisation to interact **directly with the Livepeer protocol**.
-Gateways submit jobs, route work to orchestrators, manage payment flows, and provide a direct interface to the network.
-**Not** the same as hosted services like Studio or Daydream.
-
-### **Orchestrator (GPU Node)**
-
-A supply-side operator that contributes **GPU resources** to the network.
-Orchestrators receive jobs, perform transcoding or AI inference, and get paid via LPT rewards + ETH fees.
-
-### **Transcoder (Worker)**
-
-A worker process-often managed by an orchestrator-that performs the actual compute work (transcoding or AI inference).
-
-### **Delegator**
-
-A token holder who stakes their LPT to an orchestrator to help secure the network and earn a share of rewards.
-
-### **Developer**
-
-Anyone building applications _using_ Livepeer, usually through **hosted services** (e.g., Studio, Daydream) or library SDKs.
-Developers only run gateways if they want direct protocol access.
-
-### **Broadcaster (-> Gateway)**
-
-
-
- Deprecated Term
- {' '}
- See **Gateways** A job submitter-often a user-facing service-that sends video
- or AI jobs into the network via a gateway.
-
-
-### **Verifier**
-
-A network component (protocol-level) responsible for validating work performed by orchestrators to ensure correctness.
-
-### **Protocol**
-
-The on-chain governance and incentive layer that coordinates orchestrators, staking rewards, inflation, slashing, and job payments.
-
-
-
-
-
-**`#lounge`** — The main channel for developers. Ask questions about the API, SDKs, stream configuration, video assets, and general development. The most active support channel for application builders.
-
-**`#ai-research`** — Dedicated to Livepeer's AI inference capabilities. Ask about the AI subnet, ComfyUI workflows, ComfyStream, the Daydream API, pipeline configuration, and GPU requirements.
-
-
-
-
-
-**`#delegating`** — Questions about delegating LPT, staking rewards, choosing an orchestrator, and understanding delegation mechanics.
-
-
-
-
-
-**`#governance`** — Discussions around Livepeer Improvement Proposals (LIPs), governance votes on the Explorer, and protocol-level decision-making.
-
-
-
-
-
-**`#landing-pad`** — The first stop for new community members. Good place to introduce yourself and get oriented before asking technical questions in other channels.
-
-
-
-
-
-**`#general`** — General ecosystem chat.
-
-**`#introductions`** — Introduce yourself to the community.
-
-
-
-
-
-
-Discord is best for real-time, conversational questions. For questions that deserve a permanent, searchable answer — especially detailed technical or protocol questions — the Forum is a better home.
-
-
-
-
-
-Questions for new participants — setting up wallets, delegating for the first time, understanding the network. Post here if you are stuck early in your journey.
-
-
-
-Technical discussions about building applications on Livepeer — API questions, SDK issues, integration patterns, and architecture decisions. The best category for developers who need an in-depth answer.
-
-
-
-Operational questions and discussions for people running orchestrator nodes — configuration, transcoding performance, reward mechanics, and GPU selection.
-
-
-
-Protocol-level technical discussions — smart contracts, cryptoeconomics, bonding mechanics, and security topics.
-
-
-
-Governance discussions and Livepeer Improvement Proposals (LIPs). Read active proposals, post feedback, or draft new proposals here before moving them to an on-chain vote.
-
-
-
-
-
-Before posting, search the forum for existing threads on your topic. Many common questions — particularly around orchestrator configuration, delegating, and API behaviour — have thorough existing answers.
-
-
-
-
-
- Report bugs with the Livepeer Studio dashboard, REST API, asset pipeline, or livestream behaviour. Use the issue templates provided.
-
-
-
- Report bugs in the orchestrator or broadcaster node software. Include go-livepeer version, OS, and reproduction steps.
-
-
-
- Report errors, outdated content, broken links, or missing documentation. Eight issue templates are available for different types of doc feedback.
-
-
-
- Report issues with the AI inference runtime — pipeline bugs, Docker image issues, or model loading problems.
-
-
-
- Report bugs in the JavaScript or React SDK. Include SDK version, browser/Node.js version, and a minimal reproduction.
-
-
-
- Issues with the Ethereum/Arbitrum smart contracts. For potential security vulnerabilities, use the Immunefi bug bounty programme instead.
-
-
-
-
-### Writing a Good Issue
-
-Before filing an issue on any Livepeer repository:
-
-1. **Search first** — Check whether the issue has already been reported
-2. **Use the templates** — Each repo provides issue templates; fill them out fully
-3. **Be specific** — Include versions, error messages, and reproduction steps
-4. **One issue per report** — Do not combine multiple bugs in a single issue
-
-
-**Do not file security vulnerabilities as public GitHub issues.** Use the Immunefi programme below.
-
-
-For confirmed or suspected security vulnerabilities in Livepeer's smart contracts or protocol:
-
-**Immunefi Bug Bounty:** [immunefi.com/bug-bounty/livepeer](https://immunefi.com/bug-bounty/livepeer/information/)
-
-The programme covers smart contracts on Arbitrum and Ethereum. Rewards are paid in USDC. KYC is required for payout. A proof-of-concept (PoC) is required for all web/app reports.
-
-
-
-
- The primary community hub — join for real-time chat with builders, orchestrators, delegators, and core team members.
-
-
-
- Permanent, searchable discussion threads for technical and protocol topics. Better than Discord for questions that benefit from lasting answers.
-
-
-
- Community discussions on Reddit — primarily ecosystem news and general protocol discussion.
-
-
-
- Livepeer has a Telegram presence for community updates. Find the link at the Community Hub on livepeer.org.
-
-
-
- Follow @Livepeer for protocol news, product launches, and ecosystem highlights. Not monitored for technical support queries.
-
-
-
- The official blog for in-depth technical articles, ecosystem stories, vision posts, and product announcements.
-
-
-
-
-
-
-
- Open and Video Disruptor grant tracks for builders creating tools, applications, or educational content for the ecosystem.
-
-
-
- Scoped software bounties for specific tasks on the Livepeer protocol — a good entry point for open-source contributors.
-
-
-
- A bespoke 3-month programme for ambitious startups — grant funding, mentorship, investor access, and technical support.
-
-
-
-
-
-If you are unsure which channel to use: start with Discord `#lounge` for quick development questions, the Forum for technical questions that deserve a permanent answer, and GitHub Issues for confirmed bugs with reproduction steps.
-
diff --git a/v2/developers/opportunities/bug-bounties.mdx b/v2/developers/opportunities/bug-bounties.mdx
deleted file mode 100644
index 044f415dd..000000000
--- a/v2/developers/opportunities/bug-bounties.mdx
+++ /dev/null
@@ -1,200 +0,0 @@
----
-title: Bug Bounties
-sidebarTitle: Bug Bounties
-description: >-
- Report smart contract vulnerabilities in the Livepeer protocol and earn USDC
- rewards through the official Livepeer bug bounty programme on Immunefi.
-keywords:
- - livepeer
- - bug bounty
- - immunefi
- - security
- - smart contract
- - vulnerability
- - usdc
- - developer
- - builder opportunities
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-purpose: how_to
-pageType: reference
-audience:
- - security-researchers
- - protocol-contributors
- - developers
-status: current
-lastVerified: 2026-03
-sourceOfTruth: 'https://immunefi.com/bug-bounty/livepeer/information/'
----
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { DisplayCard } from '/snippets/components/wrappers/cards/CustomCards.jsx'
-import { BorderedBox } from '/snippets/components/wrappers/containers/Containers.jsx'
-
-{/* ============================================================
- INTRO
- ============================================================ */}
-
-
- The authoritative source for scope, reward tiers, rules, and submission instructions.
-
-
-
- -{/* ============================================================ - SECTION 1 - PROGRAMME OVERVIEW - ============================================================ */} - -
-
-- **Scope:** Smart contracts only. The programme does not currently cover websites, apps, or off-chain infrastructure.
-- **Rewards:** Paid in USDC on Ethereum, denominated in USD.
-- **KYC:** Required for all reporters claiming a reward. You will need to provide visual proof of identity.
-- **Proof of Concept:** Required for all severity levels. Submissions without a PoC will not be considered.
-- **Triage:** Since early 2025, the Immunefi triage pipeline has been operated by the Protocol R&D SPE (Sidestream), which processes incoming reports and ensures response-readiness.
-
-
-
-
- -{/* ============================================================ - SECTION 2 - SEVERITY AND REWARDS - ============================================================ */} - -
-
-
- Rewards are capped at 10% of the economic damage caused, with the primary focus on possible loss of funds for Orchestrators, Delegators, and Broadcasters at the smart contract level.
-
- If there is a repeatable attack, only the first attack is considered unless further attacks cannot be mitigated via an upgrade or pause.
-
-
-
- Rewards for High severity vulnerabilities depend on the amount of unclaimed yield at risk and how long funds could be frozen.
-
-
-
-
-
- -### Focus Areas - -The programme focuses on preventing: - -- Direct theft of user funds (at-rest or in-motion, excluding unclaimed yield) -- Unexpected calls to privileged functions (for example, functions that should only be callable by the Governor contract) -- Any condition that results in permanent freezing of user funds - -
- -{/* ============================================================ - SECTION 3 - WHAT'S IN SCOPE - ============================================================ */} - -
- -{/* ============================================================ - SECTION 4 - HOW TO SUBMIT - ============================================================ */} - -
-
- Ensure you have a working proof of concept on a local fork of mainnet or testnet. Document the attack vector, impact, and reproduction steps.
-
-
- Submit your report through the [Livepeer programme page on Immunefi](https://immunefi.com/bug-bounty/livepeer/information/). Do not disclose the vulnerability publicly before it has been resolved.
-
-
- On confirmation of a valid report, you will be asked to complete KYC verification via an external service before payment is released. You will need government-issued photo ID.
-
-
- Valid rewards are paid in USDC on Ethereum. Payout amounts are handled directly by the Livepeer team and are denominated in USD.
-
-
-
-
- -
- Public disclosure of an unpatched vulnerability is a violation of the programme rules and will disqualify a submission from receiving a reward. Always report privately first.
-
-
-
- -{/* ============================================================ - SECTION 5 - RECENT ACTIVITY - ============================================================ */} - -
- -{/* ============================================================ - SECTION 6 - RELATED - ============================================================ */} - -
-
- Contribute code, documentation, or test coverage to Livepeer's core repositories.
-
-
- The SPE responsible for protocol security, vulnerability triage, and safe upgrades.
-
-
- Full scope, reward tiers, rules, and submission portal for the Livepeer bug bounty.
-
-
- The official Livepeer GitHub organisation. For non-security bugs, open an issue in the relevant repository.
-
-
diff --git a/v2/developers/opportunities/grants-and-programmes.mdx b/v2/developers/opportunities/grants-and-programmes.mdx
deleted file mode 100644
index fa49c9a36..000000000
--- a/v2/developers/opportunities/grants-and-programmes.mdx
+++ /dev/null
@@ -1,268 +0,0 @@
----
-title: Grants & Programmes
-sidebarTitle: Grants & Programmes
-description: >-
- Livepeer funding opportunities for app builders, AI workflow creators,
- orchestrators, and research teams -- from microgrants to multi-month
- accelerator programmes.
-keywords:
- - livepeer
- - developers
- - grants
- - programmes
- - hackathon
- - ai video startup
- - comfyui
- - bootcamp
- - funding
- - builder opportunities
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-purpose: how_to
-pageType: guide
-audience:
- - developers
- - app-builders
- - ai-workflow-creators
- - orchestrators
- - researchers
-status: current
-lastVerified: 2026-03
-sourceOfTruth: 'https://www.livepeer.org/dev-hub'
----
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { DisplayCard } from '/snippets/components/wrappers/cards/CustomCards.jsx'
-import { BorderedBox } from '/snippets/components/wrappers/containers/Containers.jsx'
-import { GotoCard } from '/snippets/components/elements/links/Links.jsx'
-
-{/* ============================================================
- INTRO
- ============================================================ */}
-
-
- -{/* ============================================================ - SECTION 1 - GRANT TYPES - ============================================================ */} - -
-
-
- For ambitious individuals and teams conducting cutting-edge video research or building novel user-centred applications leveraging Livepeer's decentralised video compute network.
-
- **Who it's for:** Researchers, independent developers, and creative technologists.
-
-
-
- For individuals and teams building tools and applications that support supply-side node operations, delegation, and the overall health of the Livepeer network.
-
- Past examples include governance bots, educational content for new orchestrators and delegators, and tooling to parse and debug node logs.
-
- **Who it's for:** Orchestrators, node operators, delegators, and tooling developers.
-
-
-
- Tightly scoped projects with clear deliverables that can be completed in one month or less. Covers integrating Livepeer into a product or feature, or creating educational guides, tutorials, and video walkthroughs.
-
- **Who it's for:** Independent developers, content creators, integration engineers.
-
-
-
- Grants for developers who build and open-source real-time AI video workflows using ComfyUI and ComfyStream with the Livepeer network. Additional incentives are available for extended contributions.
-
- **Who it's for:** ComfyUI workflow creators, AI video developers, creative coders.
-
-
-
-
-
- -
- Grant programmes open and close on a rolling basis. The [Livepeer Dev Hub](https://www.livepeer.org/dev-hub) always shows currently open calls. If a specific programme is not listed, it may be between cohorts.
-
-
-
- -{/* ============================================================ - SECTION 2 - ACCELERATOR PROGRAMME - ============================================================ */} - -
-
-Livepeer's AI Video Startup Programme is a bespoke three-month accelerator designed to help selected startups build and scale decentralised AI video applications on the Livepeer network.
-
-
-
-
- -Selected teams receive: - -- Grant funding of up to $20,000 -- Infrastructure credits for AI inference and transcoding -- Expert technical mentorship from the Livepeer engineering team -- Early access to new AI video infrastructure and pipelines -- Co-marketing and partnership activation opportunities -- Investor networking and showcase opportunities - -The first cohort (August to October 2024) included eight startups: Flipguard, Katana, Newcoin, Operator, Origin Stories, Refraction, Supermodel, and StreamEth. Teams focused on incorporating generative AI features including text-to-image, image-to-image, image-to-video, upscaling, and speech-to-text into their applications, using existing Livepeer pipelines or building and deploying their own. - -A parallel programme run in partnership with Encode Club offers an eight-week accelerator for past Encode programme participants and others who wish to join, with weekly workshops, one-on-one sessions, and support for technical development, design, and fundraising. - -
-
- The AI Video Startup Programme is listed on the Dev Hub when applications are open.
-
-
- The Encode Club variant of the accelerator for programme alumni and the wider community.
-
-
-
-
- -{/* ============================================================ - SECTION 3 - COMFYUI HACKER PROGRAMME - ============================================================ */} - -
- Hacker Programme cohort applications are listed on the Dev Hub when open.
-
-
-
- -{/* ============================================================ - SECTION 4 - BOOTCAMP - ============================================================ */} - -
-
- Encode Club partners with Livepeer on developer bootcamp and accelerator programmes.
-
-
- Watch for future bootcamp cohort announcements on the Dev Hub.
-
-
-
-
- -{/* ============================================================ - SECTION 5 - HACKATHONS - ============================================================ */} - -
- -{/* ============================================================ - SECTION 6 - APPLYING - ============================================================ */} - -
-
- Go to [livepeer.org/dev-hub](https://www.livepeer.org/dev-hub) and review open calls.
-
-
- Match your project type to the grant or programme that fits -- see the [grant types overview](#grant-types) above.
-
-
- Most applications ask for a project description, team background, how you plan to use Livepeer, and your expected output or deliverables.
-
-
- Submit via the Dev Hub form. Stay active in the [Livepeer Discord](https://discord.gg/livepeer) to connect with the team and other applicants.
-
-
-
-
- -
- If you have a project idea and are unsure where it fits, the Livepeer community on Discord and the Forum are good places to sense-check before applying formally.
-
-
-
- -{/* ============================================================ - SECTION 7 - RELATED - ============================================================ */} - -
-
- Apply for Foundation-issued RFPs or propose a funded SPE via the Livepeer onchain treasury.
-
-
- Contribute code, documentation, or tooling to Livepeer's open source repositories.
-
-
- Report smart contract vulnerabilities and earn USDC rewards via Immunefi.
-
-
- Bounties, governance proposals, ecosystem tools, and more on livepeer.org.
-
-
diff --git a/v2/developers/resources/deepwiki.mdx b/v2/developers/resources/deepwiki.mdx
deleted file mode 100644
index 61219b6ac..000000000
--- a/v2/developers/resources/deepwiki.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: DeepWiki
-sidebarTitle: DeepWiki
-description: >-
- Use DeepWiki to explore Livepeer repositories, architecture, and workflows
- through AI-generated codebase documentation and search.
-pageType: landing
-keywords:
- - livepeer
- - developers
- - technical references
- - deepwiki
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: developer
-lastVerified: 2026-03-17
-purpose: landing
----
-DeepWiki is a fantastic resource for exploring the Livepeer codebase.
-
-If you haven't heard of it before, DeepWiki - developed by Cognition AI (the creators of Devin AI) - is an AI-powered service that generates interactive, wiki-style documentation for GitHub repositories, turning codebases into accessible knowledge bases for developers to quickly understand architecture, functionality, and workflows through natural language Q&A.
-
-
- View Livepeer Org Repo's on DeepWiki
-
-
-
- {' '}
- As with all AI generated content, not everything on DeepWiki is accurate!
-
-
-
diff --git a/v2/developers/resources/glossary-data.json b/v2/developers/resources/glossary-data.json
index 383942a59..d8780e2e4 100644
--- a/v2/developers/resources/glossary-data.json
+++ b/v2/developers/resources/glossary-data.json
@@ -538,7 +538,7 @@
},
{
"term": "SVD (Stable Video Diffusion)",
- "definition": "Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image.",
+ "definition": "Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image.",
"category": "ai",
"tags": [
"ai"
diff --git a/v2/developers/resources/glossary.mdx b/v2/developers/resources/glossary.mdx
index 5689b96b9..9f237eaad 100644
--- a/v2/developers/resources/glossary.mdx
+++ b/v2/developers/resources/glossary.mdx
@@ -133,7 +133,7 @@ Terms developers encounter across Livepeer's SDKs, AI Gateway API, streaming pro
{ Term: "StreamDiffusion", Category: "ai", Niche: "model", Definition: "Optimised real-time diffusion pipeline using stream batching and stochastic similarity filtering to reduce latency for live video transforms." },
{ Term: "StreamPlace", Category: "livepeer", Niche: "product", Definition: "Project building the video layer for decentralised social platforms, focused on the AT Protocol ecosystem." },
{ Term: "Sub-second Latency", Category: "video", Niche: "playback", Definition: "Video delivery with end-to-end delay under one second, typically achieved via WebRTC's UDP-based transport." },
- { Term: "SVD (Stable Video Diffusion)", Category: "ai", Niche: "model", Definition: "Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image." },
+ { Term: "SVD (Stable Video Diffusion)", Category: "ai", Niche: "model", Definition: "Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image." },
{ Term: "TensorRT", Category: "ai", Niche: "framework", Definition: "NVIDIA's inference SDK optimising models through quantisation, layer fusion, and kernel auto-tuning for low-latency GPU inference." },
{ Term: "Text-to-Image", Category: "ai", Niche: "pipeline", Definition: "AI pipeline generating an image from a natural language text prompt using a language encoder and a diffusion model." },
{ Term: "Text-to-Speech", Category: "ai", Niche: "pipeline", Definition: "AI pipeline synthesising spoken audio from written text using phonetic conversion and audio synthesis models." },
@@ -695,7 +695,7 @@ Terms developers encounter across Livepeer's SDKs, AI Gateway API, streaming pro
- **Definition**: Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image.
+ **Definition**: Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image.
**External**: [Hugging Face — Stable Video Diffusion](https://huggingface.co/stabilityai/stable-video-diffusion-img2vid-xt)
diff --git a/v2/gateways/guides/monitoring-and-tooling/x-resources/v2-about--blockchain-contracts.mdx b/v2/gateways/guides/monitoring-and-tooling/x-resources/v2-about--blockchain-contracts.mdx
index 57e046ee8..79ecf28ce 100644
--- a/v2/gateways/guides/monitoring-and-tooling/x-resources/v2-about--blockchain-contracts.mdx
+++ b/v2/gateways/guides/monitoring-and-tooling/x-resources/v2-about--blockchain-contracts.mdx
@@ -23,150 +23,66 @@ import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx
import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
import { Subtitle, CopyText } from '/snippets/components/elements/text/Text.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { LinkArrow, DoubleIconLink, LinkIcon } from '/snippets/components/elements/links/Links.jsx'
-import { Subtitle, CopyText } from '/snippets/components/elements/text/Text.jsx'
-import { CenteredContainer, BorderedBox } from '/snippets/components/wrappers/containers/Containers.jsx'
-import { ScrollableDiagram } from '/snippets/components/displays/diagrams/ZoomableDiagram.jsx'
-import { contractAddresses } from '/snippets/data/contract-addresses/contractAddressesData.jsx'
-import { CustomCardTitle } from '/snippets/components/elements/text/CustomCardTitle.jsx'
-import { AddressLinks } from '/snippets/components/elements/links/Links.jsx'
-import { LazyLoad } from '/snippets/components/wrappers/containers/LazyLoad.jsx'
-import { ArbitrumIcon, ArbitrumSVG, LivepeerIcon, LivepeerSVG } from '/snippets/components/elements/icons/Icons.jsx'
-import { SolidityEmbed } from '/snippets/components/integrators/embeds/DataEmbed.jsx'
-import { FunctionField } from '/snippets/components/displays/response-fields/ResponseField.jsx'
+# Livepeer Blockchain Contracts
Livepeer uses a comprehensive system of Ethereum smart contracts to permissionlessly govern its decentralized network.
-export const controller = contractAddresses.arbitrumOne.current.find(c => c.name === 'Controller')?.address
-export const bondingManagerProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'BondingManager' && c.type === 'proxy')?.address
-export const bondingManagerTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'BondingManager' && c.type === 'target')?.address
-export const ticketBrokerProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'TicketBroker' && c.type === 'proxy')?.address
-export const ticketBrokerTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'TicketBroker' && c.type === 'target')?.address
-export const roundsManagerProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'RoundsManager' && c.type === 'proxy')?.address
-export const roundsManagerTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'RoundsManager' && c.type === 'target')?.address
-export const minter = contractAddresses.arbitrumOne.current.find(c => c.name === 'Minter')?.address
-export const serviceRegistryProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'ServiceRegistry' && c.type === 'proxy')?.address
-export const serviceRegistryTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'ServiceRegistry' && c.type === 'target')?.address
-export const aiServiceRegistry = contractAddresses.arbitrumOne.current.find(c => c.name === 'AIServiceRegistry')?.address
-export const lptArb = contractAddresses.arbitrumOne.current.find(c => c.name === 'LivepeerToken')?.address
-export const lptEth = contractAddresses.ethereumMainnet.current.find(c => c.name === 'LivepeerToken')?.address
-
-{/* NOTE Bridgeminter is at https://github.com/livepeer/protocol/blob/streamflow/contracts/token/BridgeMinter.sol*/}
-export const bridgeMinter = contractAddresses.ethereumMainnet.current.find(c => c.name === 'BridgeMinter')?.address
-export const l2Gateway = contractAddresses.arbitrumOne.current.find(c => c.name === 'L2LPTGateway')?.address
-export const l1Gateway = contractAddresses.ethereumMainnet.current.find(c => c.name === 'L1LPTGateway')?.address
-export const l1Escrow = contractAddresses.ethereumMainnet.current.find(c => c.name === 'L1Escrow')?.address
-export const bondingVotesProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'BondingVotes' && c.type === 'proxy')?.address
-export const bondingVotesTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'BondingVotes' && c.type === 'target')?.address
-export const governor = contractAddresses.arbitrumOne.current.find(c => c.name === 'Governor')?.address
-export const livepeerGovernorProxy = contractAddresses.arbitrumOne.current.find(c => c.name === 'LivepeerGovernor' && c.type === 'proxy')?.address
-export const livepeerGovernorTarget = contractAddresses.arbitrumOne.current.find(c => c.name === 'LivepeerGovernor' && c.type === 'target')?.address
-export const treasury = contractAddresses.arbitrumOne.current.find(c => c.name === 'Treasury')?.address
-export const l2Migrator = contractAddresses.arbitrumOne.current.find(c => c.name === 'L2Migrator' && c.type === 'proxy')?.address
-export const merkleSnapshot = contractAddresses.arbitrumOne.current.find(c => c.name === 'MerkleSnapshot')?.address
-export const lastVerifiedDate = contractAddresses.meta.lastVerified || "Pending"
-
-{/* Status helper: builds status string from enriched meta fields */}
-export const statusOf = (name, type, chain) => {
- const c = contractAddresses[chain || 'arbitrumOne'].current.find(e => e.name === name && (!type || e.type === type))
- if (!c?.meta) return "Verified · Active"
- const m = c.meta
- const parts = []
- if (c.verified) parts.push("Verified")
- if (m.holderCount) parts.push(`${m.holderCount} holders`)
- if (m.transactionCount && m.transactionCount < 1000) parts.push(`~${m.transactionCount} transactions`)
- if (m.statusLabel) parts.push(m.statusLabel)
- if (m.deployedAt && m.statusLabel !== 'Active') parts.push(`Deployed ${m.deployedAt}`)
- if (m.deployedBy) parts.push(`Deployed by ${m.deployedBy}`)
- if (m.lastActiveDate && m.statusLabel !== 'Active') parts.push(`Last active ${m.lastActiveDate}`)
- if (m.blockscoutLabel && m.blockscoutLabel !== name) parts.push(`"${m.blockscoutLabel}" on Blockscout`)
- if (m.notes) parts.push(m.notes)
- if (m.registeredInController) parts.push("Registered in Controller")
- return parts.join(" · ") || "Active"
-}
-
-
- Addresses on this page are automatically updated via a Github Action workflow.
- Data is sourced from the canonical
- Last verified: {lastVerifiedDate} -
-
-
- Livepeer Contract Addresses
Canonical Code }
- horizontal
- />
- Livepeer Contracts Arbiscan
On-chain Canonical }
- horizontal
- />
-
-
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#18794E', 'primaryTextColor': '#fff', 'primaryBorderColor': '#3CB540', 'lineColor': '#3CB540', 'mainBkg': '#18794E', 'nodeBorder': '#3CB540', 'clusterBkg': 'transparent', 'clusterBorder': '#3CB540', 'titleColor': '#3CB540', 'edgeLabelBackground': 'transparent', 'textColor': '#3CB540', 'nodeTextColor': '#fff'}}}%%
+{/* 1. Controller [Core]
+2. BondingManager [Core]
+3. TicketBroker [Core]
+4. RoundsManager [Core]
+5. Minter [Core]
+6. ServiceRegistry [Core]
+7. MerkleSnapshot [Core]
+8. BondingVotes [Core]
+7. LivepeerToken [Token]
+8. Governor[Governance]
+9. LivepeerGovernor [Governance]
+10. Treasury [Governance] */}
+
+## Contract Interaction Architecture
+
+Here's how these contracts interact with each other:
+
+ FIX THIS DIAGRAM - unreadable
+````mermaid
graph TB
- subgraph "Registry"
- Controller["Controller\nContract Registry"]
- end
-
- subgraph "Discovery"
- ServiceRegistry["ServiceRegistry\nOrchestrator URI Mapping"]
- AIServiceRegistry["AIServiceRegistry\nAI Capability Registration"]
- end
-
- subgraph "Economic"
- LPT["LivepeerToken\nERC-20"]
- BondingManager["BondingManager\nStaking & Rewards"]
- TicketBroker["TicketBroker\nMicropayments"]
- Minter["Minter\nToken Inflation"]
+ subgraph "Discovery Layer"
+ Controller["Controller
Contract Registry"] + ServiceRegistry["ServiceRegistry
URI Mapping"] end - subgraph "Time" - RoundsManager["RoundsManager\nProtocol Rounds"] + subgraph "Economic Layer" + LPT["LivepeerToken
ERC20 Token"] + BondingManager["BondingManager
Staking & Rewards"] + TicketBroker["TicketBroker
Micropayments"] + Minter["Minter
Token Inflation"] end - subgraph "Governance" - BondingVotes["BondingVotes\nStake Checkpointing"] - Governor["Governor\nUpgrade Executor"] - LivepeerGovernor["LivepeerGovernor\nOn-chain Voting"] - Treasury["Treasury\nProtocol Treasury"] + subgraph "Time & Governance" + RoundsManager["RoundsManager
Protocol Rounds"] + Governor["LivepeerGovernor
Governance"] end subgraph "Participants" - Gateway["Gateway Node"] + Broadcaster["Broadcaster Node"] Orchestrator["Orchestrator Node"] - Delegator["LPT Holder"] + Delegator["Token Holder"] end Controller -.->|"Address Lookup"| LPT @@ -175,39 +91,33 @@ graph TB Controller -.->|"Address Lookup"| RoundsManager Controller -.->|"Address Lookup"| Minter Controller -.->|"Address Lookup"| ServiceRegistry - Controller -.->|"Address Lookup"| BondingVotes - Controller -.->|"Address Lookup"| LivepeerGovernor - Controller -.->|"Address Lookup"| Treasury + Controller -.->|"Address Lookup"| Governor - Delegator -->|"approve() LPT"| LPT - Delegator -->|"bond(amount, orch)"| BondingManager - Delegator -->|"castVote()"| LivepeerGovernor - BondingManager -->|"transferFrom()"| LPT - BondingManager -->|"checkpointBondingState()"| BondingVotes + Delegator -->|"Approve() LPT"| LPT + Delegator -->|"Bond(amount, orchestrator)"| BondingManager + BondingManager -->|"TransferFrom()"| LPT - Orchestrator -->|"transcoder(rewardCut, feeShare)"| BondingManager - Orchestrator -->|"setServiceURI(url)"| ServiceRegistry - Orchestrator -->|"reward()"| BondingManager - BondingManager -->|"createReward()"| Minter - Minter -->|"mint() new LPT"| LPT - Minter -->|"trustedTransferTokens()"| Treasury + Orchestrator -->|"Transcoder(cuts)"| BondingManager + Orchestrator -->|"SetServiceURI(url)"| ServiceRegistry + Orchestrator -->|"Reward()"| BondingManager + BondingManager -->|"CreateReward()"| Minter + Minter -->|"Mint() new LPT"| LPT - Gateway -->|"fundDepositAndReserve()"| TicketBroker - Orchestrator -->|"redeemWinningTicket()"| TicketBroker - TicketBroker -->|"winningTicketTransfer()"| LPT + Broadcaster -->|"Approve() LPT"| LPT + Broadcaster -->|"FundDepositAndReserve()"| TicketBroker + TicketBroker -->|"TransferFrom()"| LPT - RoundsManager -->|"currentRound()"| BondingManager - RoundsManager -->|"blockHashForRound()"| TicketBroker + Orchestrator -->|"RedeemWinningTicket()"| TicketBroker + TicketBroker -->|"Transfer() to orchestrator"| LPT + TicketBroker -->|"Update claimedReserve"| BondingManager - BondingVotes -->|"getPastVotes()"| LivepeerGovernor - LivepeerGovernor -->|"execute()"| Governor - Governor -->|"setContractInfo()"| Controller -``` + RoundsManager -->|"Round data"| BondingManager + RoundsManager -->|"Block hashes"| TicketBroker -
-
+ BondingManager -->|"Stake weight"| Governor
+ Delegator -->|"CastVote()"| Governor
+````
-
- Arbitrum One
-
-The Controller is the central registry for all protocol contracts. Every other contract resolves peer contract addresses by calling `getContract(keccak256(""))` on the Controller. Upgrades are applied by registering a new implementation address under the same name hash – the proxy addresses never change.
+## Token & Utility Contracts
Livepeer moved from the Ethereum mainnet to the Arbitrum One network in 2022 to increase transaction throughput and reduce fees.
-- Central address registry for all protocol contracts -- Enables contract upgrades while keeping proxy addresses stable -- Provides `pause()`/`unpause()` for emergency system-wide halts -- Owner is the Governor contract – all upgrades must go through governance +On Ethereum mainnet, only the `LivepeerToken` and `BridgeMinter` contracts remain operational; all other contracts have migrated to Arbitrum One. This ensures the token has the higher security of the Ethereum mainnet while the network enjoys the higher throughput and lower fees of Arbitrum. -
- Look up a registered contract by keccak256 name hash
-
-
- Returns address and git commit hash
-
-
- Register or update a contract; callable by owner (Governor) only
-
-
- Halt all contracts that check `controller.paused()`
-
-
- Resume all contracts that check `controller.paused()`
-
-
- Update the Controller reference in a registered contract
-
+
#### **LivepeerToken (LPT)**: Ethereum Mainnet Only
-
-
-#### **BondingManager**
- Arbitrum One
-
-The BondingManager is the most critical economic contract in the protocol. It manages the active orchestrator pool as a sorted doubly-linked list, handles all LPT bonding and unbonding, and distributes inflationary rewards and fees each round.
-
-The [LivepeerTokenFaucet](https://github.com/livepeer/protocol/blob/e8b6243c/contracts/token/LivepeerTokenFaucet.sol) is used on testnets for distributing test LPT tokens.
-
-Source: `BondingManager.sol` includes this as struct comment: "// % of fees paid to delegators by transcoder".
-
-
- **Slashing:** `slashTranscoder()` exists in the contract but is currently inoperative: the Verifier role is set to the null address (`0x000...`). Slashing could be re-enabled via governance by configuring the Verifier role and making necessary compatibility updates. It is out of scope for current audits.
-
-
-**Key functions** (from `BondingManager.sol`, `delta` branch):
-
-
- Delegate LPT stake to an orchestrator
-
-
- Begin withdrawal; creates an unbonding lock, starts the unbonding period
-
-
- Cancel unbonding and re-bond stake to current delegate
-
-
- Re-bond to a new orchestrator from unbonded state
-
-
- Complete withdrawal after unbonding period expires
-
-
- Withdraw accumulated ETH fees to a recipient address
-
-
- Register as an orchestrator or update parameters; `_rewardCut` is % of reward kept by orchestrator; `_feeShare` is % of fees passed to delegators
-
-
- Called by active orchestrators each round to mint inflationary LPT and distribute to earnings pool
-
-
- Claim accumulated rewards and fees. Note: `_endRound` is unused; earnings are always claimed through the current round regardless of the value passed.
-
-
- Publicly callable function to fix a stale voting power checkpoint for any account. Useful for operators after an inconsistent state.
-
-
- Transfer ownership of a bond (or portion) to a new delegator. Used for stake migrations between wallets.
-
-
- Returns unclaimed pending stake for a delegator through the current round
-
-
- Returns unclaimed pending ETH fees for a delegator through the current round
-
-
- Returns orchestrator state: lastRewardRound, rewardCut, feeShare, activationRound, deactivationRound, cumulativeRewards, cumulativeFees, lastFeeRound
-
-
- Returns delegator state: bondedAmount, fees, delegateAddress, delegatedAmount, startRound, lastClaimRound, nextUnbondingLockId
-
-
-**Contract**
-
-
- Arbitrum One
-
-The TicketBroker implements Livepeer's off-chain probabilistic micropayment (PM) system. Gateways pre-fund a deposit and reserve on-chain; they send lottery tickets to orchestrators off-chain with each transcoding job. Orchestrators redeem winning tickets on-chain to claim payment. This amortises per-segment payment costs across many tickets.
-
-
- Gateway adds ETH to deposit (payable)
-
-
- Gateway adds ETH to reserve (payable)
-
-
- Fund both deposit and reserve in one call (payable); msg.value must equal the sum of both amounts
-
-
- Fund deposit and reserve on behalf of another address (payable)
-
-
- Orchestrator redeems a winning ticket; transfers ETH to fee pool via BondingManager. Emits both `WinningTicketTransfer` and `WinningTicketRedeemed`.
-
-
- Gateway initiates the withdrawal unlock period; emits `Unlock`
-
-
- Gateway cancels an in-progress unlock; emits `UnlockCancelled`
-
-
- Gateway withdraws all deposit and reserve after unlock period; emits `Withdrawal`
-
-
- Returns full sender state: deposit amount, withdrawRound, and reserve info
-
-
- Returns whether a sender has an unlock in progress
-
-
-**Contract**
-
-
- Arbitrum One
-
-The RoundsManager defines the protocol's time unit. A round is a fixed number of Arbitrum blocks. The current round must be initialised before orchestrators can call `reward()`. It stores per-round block hashes used as randomness for ticket validation.
-
-
- Initialise a new round; callable by any address; updates block hash store and lip upgrade rounds
-
-
- Returns current round number
-
-
- Returns whether the current round has been initialised
-
-
- Returns whether the current round is in its lock period
-
-
- Returns the stored block hash for a given round
-
-
- Returns round length in blocks
-
-
- Returns lock period as a percentage of round length (MathUtils percPoint)
-
-
-**Contract**
-
-
- Arbitrum One
-
-The Minter controls LPT token inflation. Each round it calculates the mintable token supply based on the configured inflation rate. Since the Delta upgrade (LIP-91), a configurable fraction of each round's reward is minted to the Treasury rather than solely to orchestrators and delegators.
-
-
- Called only by BondingManager; mints a fraction of mintable tokens for the round as a reward
-
-
- Transfer LPT to an address; callable by BondingManager only
-
-
- Burn LPT; callable by BondingManager only
-
-
- Withdraw ETH to an address; callable by BondingManager only
-
-
- Receive ETH from TicketBroker on ticket redemption (payable)
-
-
- Returns LPT mintable in the current round
-
-
- Returns LPT already minted in the current round
-
-
- Returns current inflation rate as a MathUtils percPoint value
-
-
- Returns per-round inflation adjustment amount
-
-
- Returns the target bonding rate that inflation adjusts towards
-
-
-**Contract**
-
-
- Arbitrum One
-
-The ServiceRegistry stores each orchestrator's publicly advertised HTTPS service URI on-chain. Gateway nodes query this registry during network initialisation to discover orchestrators. Each update emits a `ServiceURIUpdate` event that off-chain indexers track.
-
-
- Orchestrator registers or updates their HTTPS endpoint; emits `ServiceURIUpdate(address indexed _addr, string _serviceURI)`
-
-
- Returns the registered URI for a given orchestrator address
-
-
-**Contract**
-
-
- Arbitrum One
-
-A standalone ServiceRegistry for AI subnet orchestrators. Detached from the Controller – its address is hardcoded in go-livepeer (`starter.go`) rather than resolved dynamically. Deployed by a different deployer than the main protocol contracts.
-
-
-Livepeer moved from Ethereum Mainnet to Arbitrum One in 2022 (the Confluence upgrade) to increase throughput and reduce fees.
-
-On Ethereum Mainnet, only the `LivepeerToken` and `BridgeMinter` contracts remain operational. All other Ethereum Mainnet protocol contracts are paused.
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#18794E', 'primaryTextColor': '#fff', 'primaryBorderColor': '#3CB540', 'lineColor': '#3CB540', 'mainBkg': '#18794E', 'nodeBorder': '#3CB540', 'clusterBkg': 'transparent', 'clusterBorder': '#3CB540', 'titleColor': '#3CB540', 'edgeLabelBackground': 'transparent', 'textColor': '#3CB540', 'nodeTextColor': '#fff'}}}%%
-graph TB
- subgraph "Ethereum Mainnet"
- L1LPT["LivepeerToken (origin)"]
- BridgeMinter["BridgeMinter"]
- L1GW["L1LPTGateway"]
- ESC["L1Escrow"]
- end
- subgraph "Arbitrum One"
- L2LPT["LivepeerToken (bridged)"]
- L2GW["L2LPTGateway"]
- Minter["Minter (inflation)"]
- end
- L1GW -->|"lock LPT"| ESC
- L2GW -->|"mint on L2"| L2LPT
- BridgeMinter -->|"mint on L1"| L1LPT
- Minter -->|"mint rewards"| L2LPT
- L1GW <-.->|"Arbitrum bridge"| L2GW
-```
-
-
- Ethereum Mainnet (origin)
-
+The [LivepeerToken](https://github.com/livepeer/protocol/blob/e8b6243c/contracts/token/LivepeerToken.sol) is the native protocol token used for staking, payments, and governance based on the [ERC-20](https://eips.ethereum.org/EIPS/eip-20) standard.
-The LivepeerToken is the native protocol token. It is an ERC-20 with AccessControl-based MINTER_ROLE and BURNER_ROLE. The canonical token contract lives on Ethereum Mainnet; a bridged representation exists on Arbitrum One.
-
-
- Standard ERC-20 interface
-
-
- EIP-2612 gasless approval
-
-
- Callable only by MINTER_ROLE (Minter contract on Arbitrum, BridgeMinter on L1)
-
-
- Callable only by BURNER_ROLE
-
-
-**Contract**
-
-Ethereum Mainnet
-
-Holds MINTER_ROLE on the L1 LivepeerToken. Called by the bridge when LPT is transferred from Arbitrum back to Ethereum Mainnet, minting the corresponding L1 LPT.
-
-
- `BridgeMinter.sol` is an Ethereum Mainnet contract predating the Delta upgrade.
- See
-
-
+ **Purpose**:
-**Purpose**:
+ - ERC20 token for all economic activity in the network
+ - Used for bonding/staking to orchestrators
+ - Required for broadcaster deposits and payments
+ - Governance voting weight
-- Holds MINTER_ROLE on the L1 LivepeerToken contract
-- Called exclusively by L1LPTGateway when LPT is bridged from Arbitrum back to Ethereum Mainnet
-- Also callable by L1Migrator for migration operations (`withdrawETHToL1Migrator`, `withdrawLPTToL1Migrator`)
-- Registered with the Ethereum Mainnet Controller (`0xF96D54E490317c557A967ABfA5d6e33006BE69b3`)
-
-**Key functions** (from `BridgeMinter.sol`, `streamflow` branch):
-
-
- Mint LPT to an address; callable by L1LPTGateway only
-
-
- Send contract ETH balance to L1Migrator; callable by L1Migrator only
-
-
- Send contract LPT balance to L1Migrator; callable by L1Migrator only
-
-
- Transfer token ownership and balances to a new Minter; callable by Controller owner only
-
-
- Accept ETH deposits; required for migration compatibility with older Minter implementations (payable)
-
-
-**Contract**
-
-
-#### **L1 LPTGateway / L2 LPTGateway**
- Ethereum Mainnet
-
-
- Arbitrum One
-
-Paired bridge gateway contracts on Ethereum Mainnet (L1) and Arbitrum One (L2). LPT bridged L1→L2 is locked in L1Escrow; LPT bridged L2→L1 is released from escrow or minted via BridgeMinter. Based on the Dai bridge architecture.
-
-Ethereum Mainnet Only
-
+ **Purpose**:
-
-#### **LivepeerTokenFaucet** Testnet Deployments
-
-
-The LivepeerTokenFaucet is a non-production deploy-time convenience contract.
-
There is currently no active public testnet on Arbitrum or Ethereum. -
You can run your own testnet using the full deploy script at [deploy/deploy_contracts.ts](https://github.com/livepeer/protocol/blob/streamflow/deploy/deploy_contracts.ts) -
-
-A deploy-time convenience contract that distributes test LPT in local and testnet environments.
-It deploys automatically via [`deploy_contracts.ts`](https://github.com/livepeer/protocol/blob/delta/deploy/deploy_contracts.ts) when targeting any non-production network, seeded with `genesis.crowdSupply` worth of test LPT.
-
It is never deployed on `mainnet` or `arbitrumMainnet`. - -Testnets Only
-**Purpose**:
-
-- Distributes test LPT to developers running a local Livepeer stack
-- Enforces a per-address rate limit via `requestWait` (in hours) between requests
-- Whitelist addresses bypass the rate limit entirely
-- Seeded at deploy time with `genesis.crowdSupply`; never exists on mainnet or Arbitrum One mainnet
-
-**Key functions** (from `LivepeerTokenFaucet.sol`):
-
-
- Request test LPT; transfers `requestAmount` to caller. Requires either whitelisted status or that `requestWait` hours have elapsed since last request.
-
-
- Add an address to the rate-limit bypass whitelist; callable by owner only
-
-
- Remove an address from the whitelist; callable by owner only
-
+The [LivepeerTokenFaucet](https://github.com/livepeer/protocol/blob/e8b6243c/contracts/token/LivepeerTokenFaucet.sol) is used on testnets for distributing test LPT tokens.
-**Contract**
+
+ **Purpose**:
-
@@ -977,341 +352,115 @@ It deploys automatically via [`deploy_contracts.ts`](https://github.com/livepeer
## Governance Contracts
-The Delta upgrade ([LIP-89](https://github.com/livepeer/LIPs/blob/master/LIPs/LIP-89.md), [LIP-91](https://github.com/livepeer/LIPs/blob/master/LIPs/LIP-91.md) - October 2023) introduced full on-chain governance alongside the [Livepeer Treasury](/v2/about/livepeer-protocol/treasury). The governance system consists of four contracts working together: BondingVotes checkpoints voting power, LivepeerGovernor manages proposal voting, Treasury holds protocol funds, and Governor executes approved upgrades.
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#18794E', 'primaryTextColor': '#fff', 'primaryBorderColor': '#3CB540', 'lineColor': '#3CB540', 'mainBkg': '#18794E', 'nodeBorder': '#3CB540', 'clusterBkg': 'transparent', 'clusterBorder': '#3CB540', 'titleColor': '#3CB540', 'edgeLabelBackground': 'transparent', 'textColor': '#3CB540', 'nodeTextColor': '#fff'}}}%%
-graph LR
- BM[BondingManager] -->|"checkpoint"| BV[BondingVotes]
- D[Delegator] -->|"castVote()"| LG[LivepeerGovernor]
- BV -->|"voting power"| LG
- LG -->|"queue"| T[Treasury / Timelock]
- T -->|"execute"| GOV[Governor]
- GOV -->|"update contracts"| C[Controller]
- MINT[Minter] -.->|"trustedTransferTokens()"| T
-```
+#### **Governor**:
- Arbitrum One
-
-BondingVotes implements the ERC-5805 votes interface, storing per-round stake checkpoints for every delegator and orchestrator. The LivepeerGovernor queries it to determine voting power at proposal creation time. Checkpoints are written automatically by BondingManager on every bond, unbond, reward, and earnings claim.
-
-
+ **Purpose**:
-**Purpose**:
+ - Handles protocol upgrades through a multi-step transaction proposal and execution process
-- Stores per-round stake checkpoints for every participant
-- Implements ERC-5805 (`getPastVotes`, `getPastTotalSupply`) used by LivepeerGovernor
-- Checkpoints are written by BondingManager – not called directly by users
-- Supports delegator vote overrides: a delegator can override their orchestrator's vote
-
-**Key functions** (from `BondingVotes.sol`, `delta` branch):
-
-
- Called by BondingManager to checkpoint stake state; not callable directly by users
-
-
- Checkpoint total active stake; called by BondingManager
-
-
- Returns voting power for an account at the start of a given round
-
-
- Returns total voting power (active stake) at a given round
-
-
- Returns whether an account has any checkpointed stake
-
-
-**Contract**
-
-
-#### **Governor**
- Arbitrum One
-
-The original upgrade execution contract. Holds the owner role on the Controller. Executes protocol upgrades (contract address updates, parameter changes) via a staged update queue with a configurable block delay.
-
-
- Queue a batch of upgrade transactions with a delay in blocks; callable by owner only; emits `UpdateStaged`
-
-
- Execute a queued update after its block delay has elapsed; emits `UpdateExecuted`
-
-
- Cancel a staged update; callable by owner only; emits `UpdateCancelled`
-
+#### **LivepeerGovernor**:
+ **Purpose**:
-**Contract**
+ - On-chain voting on protocol proposals
+ - Weighted by bonded stake
+ - Implements governance mechanisms
-
-#### **LivepeerGovernor**
- Arbitrum One
-
-Implements [OpenZeppelin](https://docs.openzeppelin.com/contracts/5.x/api/governance)'s upgradeable Governor framework adapted for Livepeer's stake-weighted voting. Voting power equals bonded LPT as recorded by BondingVotes at proposal creation time. Supports GovernorCountingOverridable – delegators can override their orchestrator's vote on any proposal.
-
-
- One-time initialisation via proxy
-
-
- Submit a new governance proposal; returns proposalId
-
-
- Cast a vote (0=Against, 1=For, 2=Abstain)
-
-
- Vote with explanation
-
-
- Queue a passed proposal into the timelock
-
-
- Execute a queued proposal after timelock delay
-
-
- Returns `MathUtils.PERC_DIVISOR` (the quorum denominator)
-
-
- Update the internal BondingVotes reference if its address has changed
-
-
-**Contract**
-
-
- Arbitrum One
-
-An [OpenZeppelin](https://docs.openzeppelin.com/contracts/5.x/api/governance#TimelockController) TimelockControllerUpgradeable that holds the protocol's on-chain treasury. A configurable percentage of each round's inflationary LPT rewards is directed here by the Minter. All disbursements require a passed LivepeerGovernor proposal. Automatic contributions halt when the treasury balance exceeds `treasuryBalanceCeiling` (configured in BondingManager).
+[Treasury](https://github.com/livepeer/protocol/blob/e8b6243c/contracts/governance/Treasury.sol) manages the on-chain treasury for funding and accounting.
-
+ **Purpose**:
-**Purpose**:
+ - Manages protocol treasury for funding
+ - Tracks allocations and expenditures
+ - Funds Special Purpose Entities (SPEs)
-- Receives a fraction of each round's inflationary LPT rewards (rate set by `treasuryRewardCutRate` in BondingManager)
-- Governed entirely by LivepeerGovernor – all disbursements require a passed proposal
-- Implements TimelockController – all operations have a mandatory delay between queue and execution
-- Contributions automatically halt when LPT balance exceeds `treasuryBalanceCeiling`
-- Funds Special Purpose Entities (SPEs) and ecosystem grants via governance proposals
-
-**Key functions** ([OpenZeppelin](https://docs.openzeppelin.com/contracts/5.x/api/governance#TimelockController)) TimelockControllerUpgradeable):
-
-
- Schedule an operation; callable by proposer role (LivepeerGovernor)
-
-
- Execute a ready operation; callable by executor role
-
-
- Cancel a pending operation; callable by canceller role
-
-
- Check if an operation exists
-
-
- Check if an operation is past its delay and ready to execute
-
-
- Returns the minimum delay for all operations
-
-
-**Contract**
-
-
-
The migration is complete - no new migrations are possible - but both contracts remain registered in the Controller. - L2Migrator continues to process pending `claimStake` calls from participants who have not yet claimed their migrated stake as of March 2026.
-
-#### **L2Migrator**
- Arbitrum One
-
-
-Facilitated the migration of bonded stake and delegations from Ethereum Mainnet to Arbitrum One during the Confluence upgrade. Participants who migrated on L1 claim their Arbitrum-side stake by calling `claimStake()` here. The contract still holds residual ETH and continues to receive `claimStake` calls from participants who have not yet claimed.
-
-
- Claim migrated stake on Arbitrum One; callable by participants who completed an L1 migration
-
-
- Finalise a delegator migration initiated on L1; called via the bridge
-
-
-
+Here's how these contracts interact with each other:
-#### **MerkleSnapshot**
- Arbitrum One
-
+````mermaid
+graph TB
+ subgraph "Discovery Layer"
+ Controller["Controller
Contract Registry"] + ServiceRegistry["ServiceRegistry
URI Mapping"] + end -Stores Merkle roots used to verify stake snapshots taken at the time of the Confluence migration. Used internally by L2Migrator to validate migration claims. No activity since deployment — its role was fulfilled during the migration window. + subgraph "Economic Layer" + LPT["LivepeerToken
ERC20 Token"] + BondingManager["BondingManager
Staking & Rewards"] + TicketBroker["TicketBroker
Micropayments"] + Minter["Minter
Token Inflation"] + end -
Protocol Rounds"] + Governor["LivepeerGovernor
Governance"] + end -**Purpose**: + subgraph "Participants" + Broadcaster["Broadcaster Node"] + Orchestrator["Orchestrator Node"] + Delegator["Token Holder"] + end -- Stores Merkle root snapshots (keyed by snapshot ID) set at migration time -- Provides `verify()` for L2Migrator to validate that a claimed stake amount was included in the original snapshot -- Read-only in practice; `setSnapshot()` is callable only by the Controller owner and has not been called since the migration + Controller -.->|"Address Lookup"| LPT + Controller -.->|"Address Lookup"| BondingManager + Controller -.->|"Address Lookup"| TicketBroker + Controller -.->|"Address Lookup"| RoundsManager + Controller -.->|"Address Lookup"| Minter + Controller -.->|"Address Lookup"| ServiceRegistry + Controller -.->|"Address Lookup"| Governor -**Key functions** (from `MerkleSnapshot.sol`): + Delegator -->|"Approve() LPT"| LPT + Delegator -->|"Bond(amount, orchestrator)"| BondingManager + BondingManager -->|"TransferFrom()"| LPT -
- Verify a Merkle proof against a stored snapshot root
-
-
- Store a Merkle root for a given snapshot ID; callable by Controller owner only
-
+ Orchestrator -->|"Transcoder(cuts)"| BondingManager
+ Orchestrator -->|"SetServiceURI(url)"| ServiceRegistry
+ Orchestrator -->|"Reward()"| BondingManager
+ BondingManager -->|"CreateReward()"| Minter
+ Minter -->|"Mint() new LPT"| LPT
-**Contract**
+ Broadcaster -->|"Approve() LPT"| LPT
+ Broadcaster -->|"FundDepositAndReserve()"| TicketBroker
+ TicketBroker -->|"TransferFrom()"| LPT
- Contract Address Reference Page · Livepeer Docs
<> }
- horizontal
- arrow
-/>
-
- Livepeer Contract Addresses
Canonical Code }
- horizontal
- />
- Livepeer Contracts Arbiscan
On-chain Canonical }
- horizontal
- />
-
-
-
-
-
-
-
- {/* HeroImageBackgroundComponent: Full-width Starfield Background - fills entire content area */}
-
-
-
- {/* HeroContentContainer - 80% width, centered within content area */}
-
- {/* LogoHeroContainer */}
-
-
- Gateways are the core building block for those developers looking to productise applications built on top of the Livepeer protocol. - {/*
-
-
- {/* END HERO */}
-
-
-{/* MOVE TO EXPLAINER / PRIMER */}
- {/*
-
-
- Running a Gateway is similar to operating an API Gateway or Load Balancer in cloud computing -
- it ingests traffic, routes workloads to backend GPU nodes, and manages session flow
- without doing the heavy compute itself.
-
-
-
- ```mermaid
- %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
- flowchart LR
- subgraph Clients["Client / Application Layer"]
- A["Apps & SDKs
• Video Ingest
• AI Inference Requests
• WebRTC / HTTP"] - end - - subgraph Gateway["Gateway Layer (Livepeer Gateway)"] - B["Gateway Node
Cloud Analogy:
• API Gateway
• L7 Load Balancer
• Control Plane
Responsibilities:
• Auth & Rate Limits
• Stream Segmentation
• Job Routing
• Health Checks
• Retry & Failover"] - end - - subgraph Compute["Compute Layer (Supply Side)"] - C["Orchestrators
GPU Workers
Cloud Analogy:
• Auto-scaling GPU Fleet
• Managed Inference Pool"] - end - - subgraph Settlement["Coordination & Settlement"] - D["Ethereum + Livepeer Protocol
• Payments
• Accounting
• Slashing / Security"] - end - - A -->|Requests| B - B -->|Dispatch Jobs| C - C -->|Results / Streams| B - B -->|Responses| A - C -->|Usage & Proof| D - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style Clients fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
-
-
-
- Running a Gateway is **not** like running a validator on Ethereum.
- Validators secure consensus whereas Gateways route workloads. It's more akin to a Sequencer on a Layer 2.
- Just as a Sequencer ingests user transactions, orders them, and routes them into the rollup execution layer,
- a Livepeer Gateway performs the same function for the Livepeer compute network.
-
-
-
- ```mermaid
- %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
- flowchart LR
- subgraph User["User Layer"]
- A["Client
Video/AI Request"] - end - - subgraph Gateway["Gateway Layer"] - B["Livepeer Gateway
= L2 Sequencer
• Ingests Requests
• Segments/Preprocesses
• Selects Orchestrators
• Routes Jobs
• Returns Results"] - end - - subgraph Compute["Compute Layer"] - C["Orchestrators
GPU Workers
= L2 Execution Layer"] - end - - subgraph Settlement["Settlement Layer"] - D["Ethereum
Consensus & Payment Security"] - end - - A --> B - B --> C - C --> B - B --> A - C --> D - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style User fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
-
-
-
- For the rest of us, running a Gateway is like being a film producer.
- You take a request, assemble the right specialists, manage constraints,
- and ensure the final result is delivered reliably-without doing every task yourself.
-
-
-
- ```mermaid
- %%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
- flowchart LR
- subgraph Persona["Persona: Gateway Operator = Film Producer"]
- P["Film Producer Mindset
• Owns delivery
• Sets constraints
• Chooses specialists
• Ensures quality"] - end - - subgraph Request["Act I - The Pitch"] - A["Incoming Request
• Live Video Stream
• AI Inference Job
• Quality & Latency Requirements"] - end - - subgraph Planning["Act II - Pre-Production"] - B["Gateway (Producer)
• Interpret the request
• Set budget & latency constraints
• Choose specialists
• Plan execution"] - end - - subgraph Crew["Act III - Production Crew"] - C["Orchestrators / GPU Workers
• Transcoding
• AI Inference
• Real-time Processing"] - end - - subgraph Delivery["Act IV - Final Cut & Release"] - D["Verified Output
• Stream / AI Result
• Quality checked
• Delivered on time"] - end - - subgraph Settlement["Credits & Accounting"] - E["Onchain Settlement
• Usage recorded
• Payments distributed
• Trust enforced"] - end - - P --> A - A --> B - B --> C - C --> B - B --> D - C --> E - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style Persona fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Request fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Planning fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Crew fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Delivery fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
-
- */}
-
-
-
-
-
-
- What? Where Am I? What's a Gateway? Why do I need one?
-
-
- Find Video and AI Services available via Gateways on the Livepeer Network.
-
-
-
- Developer Level Up
-
-
- Deploy your own Gateway on the Livepeer Protocol - no GPU required! -
-
- Tools and Dashboards to help find and manage Gateways -> for users and
- operators.
-
-
- Full guides, examples and tutorials on running a Livepeer Gateway node.
-
-
- All your Gateway questions answered.
-
-
-
-
-
diff --git a/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration-view.mdx b/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration-view.mdx
deleted file mode 100644
index 05ffc1591..000000000
--- a/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration-view.mdx
+++ /dev/null
@@ -1,193 +0,0 @@
----
-title: Video Configuration
-sidebarTitle: Video & Transcoding Configuration
-description: Configure Video Services on a Livepeer Gateway
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - configure
- - video configuration view
- - video
- - configuration
- - services
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-icon: film-canister
----
-
-
-
-
-import { DoubleIconLink } from '/snippets/components/elements/links/Links.jsx'
-import { DynamicTable } from '/snippets/components/wrappers/tables/Table.jsx'
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-
-{/* Views:
-
-- Intro & Architecture
-- Quickstart
-- Full Config Guide
-- Config Flags
-*/}
-
-## TL;DR Configuration
-
-If you just want a working video gateway, run the below command:
-
-
-```bash wrap lines icon="terminal" Off-Chain Video Gateway
-livepeer -gateway \
- -network offchain \
- # Minimum required video flags
- -rtmpAddr=0.0.0.0:1935 \
- -httpAddr=0.0.0.0:8935 \
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9 \
- # You will need to add your local orchestrator address if you are running offchain
- -orchAddr=
-```
-
-```bash wrap lines icon="link" On-Chain Video Gateway
-livepeer -gateway \
- -network arbitrum-one-mainnet \
- # See the on-chain setup guide for more details on these flags
- -ethUrl= \
- -ethAcctAddr= \
- -ethPassword= \
- -ethKeystorePath= \
- # Minimum required video flags
- -rtmpAddr=0.0.0.0:1935 \
- -httpAddr=0.0.0.0:8935 \
- -maxPricePerUnit=1000 \
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9 \
- -orchAddr=
- # You will need to connect to a public orchestrator if you are running onchain
-
-```
-
-
-
-
-## Gateways for Video Transcoding
-In traditional video transcoding, the Gateway ingests video streams via [RTMP](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol) or [HTTP](https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol),
-segments them, and distributes transcoding work to Orchestrators
-
-The workflow involves segmenting video, sending segments with payments to Orchestrators,
-receiving transcoded results, and serving them via HLS .
-
-Gateways that receive a live or recorded RTMP stream need to transcode it into multiple renditions before sending it to Orchestrators for distribution.
-
-{/* Key components include:
-
-- **[BroadcastSessionsManager](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/broadcast.go)**: Manages transcoding sessions and selects Orchestrators
-- **[RTMP](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol) Server**: Handles RTMP (Real-Time Message Protocol) stream ingestion
-- **[Payment Manager](https://github.com/livepeer/go-livepeer/blob/5691cb48/core/live_payment.go)**: Generates and sends payment tickets for transcoding work */}
-
-{/* 2. Diagram */}
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
-flowchart TB
- subgraph INPUT["Video Input Sources"]
- direction LR
- RTMP["RTMP Stream
:1935"] - HTTP["HTTP Upload
:8935"] - end - - GATEWAY["Gateway Node
LivepeerNode
-gateway mode"] - - INPUT --> GATEWAY - - subgraph MANAGER["Broadcast Session Manager"] - BSM["BroadcastSessionsManager
Manages transcoding sessions
Selects orchestrators"] - end - - GATEWAY --> BSM - - subgraph PROCESSING["Video Processing Pipeline"] - direction TB - SEG["Segment Video
Split into chunks"] - TRANS["Send to Orchestrators
with payment tickets"] - ORCH["Orchestrators
Transcode segments
Multiple renditions"] - RECEIVE["Receive Results
Transcoded segments"] - end - - BSM --> SEG --> TRANS --> ORCH --> RECEIVE - - subgraph OUTPUT["Output & Delivery"] - direction LR - HLS["HLS Manifest
.m3u8"] - RENDITIONS["Multiple Renditions
240p, 360p, 720p, 1080p"] - end - - RECEIVE --> HLS --> RENDITIONS - - subgraph PAYMENT["Payment System"] - direction TB - PM["Payment Manager
Generate tickets"] - TICKETS["Per-segment payments
Based on pixels transcoded"] - end - - TRANS --> PM --> TICKETS --> ORCH - - subgraph STORAGE["Storage (Optional)"] - OBJ["Object Store
S3/IPFS"] - end - - RENDITIONS -.-> OBJ - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef payment fill:#1a1a1a,color:#fff,stroke:#fbbf24,stroke-width:2px - class RTMP,HTTP,BSM,SEG,TRANS,ORCH,RECEIVE,HLS,RENDITIONS video - class PM,TICKETS payment - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGER fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PROCESSING fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style OUTPUT fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#fbbf24,stroke-width:1px - style STORAGE fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,stroke-dasharray: 5 5 -``` - -
-
-
- go-livepeer/core/livepeernode.go
-
-
-
- # Quick Start Video Gateway Configuration
-
-For a basic video gateway, start with the below recommended settings and gradually add options based on your specific needs.
-The most critical settings are `-orchAddr` (to connect to orchestrators) and network addresses to allow external access.
-
-```bash wrap lines icon="terminal" Transcoding Options
-livepeer -gateway \
- -network offchain \
- -rtmpAddr=0.0.0.0:1935 \
- -httpAddr=0.0.0.0:8935 \
- -cliAddr=0.0.0.0:5935 \
- -maxSessions=10 \
- -orchAddr= \
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9,P720p30fps16x9
- # You can also use a JSON file: path/to/transcodingOptions.json
-```
-
-
-
- wip
-
-
- wip
-
diff --git a/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration.mdx b/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration.mdx
deleted file mode 100644
index c5a04b01e..000000000
--- a/v2/gateways/x-archived/_contextData_/new/gateways-new/setup/configure/video-configuration.mdx
+++ /dev/null
@@ -1,745 +0,0 @@
----
-title: Video Configuration
-sidebarTitle: Video & Transcoding Configuration
-description: Configure Video Services on a Livepeer Gateway
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - configure
- - video configuration
- - video
- - configuration
- - services
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-purpose: concept
-icon: film-canister
----
-
-
-
-
-
- {' '}
- Ugh I hate this page. I think its best to move everything to quickstart and have
- this be a comprehensive flag overview{' '}
-
-
-import { DoubleIconLink } from '/snippets/components/elements/links/Links.jsx'
-import { DynamicTable } from '/snippets/components/wrappers/tables/Table.jsx'
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-import { CustomResponseField } from '/snippets/components/content/responseField.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-
-{/* Page Flow:
-
-1. Intro
-2. Diagram
-3. Main Flags
-4. Quickstart Code
-5. Full Config Guide Options */}
-
-## TL;DR Configuration
-
-If you just want a working video gateway, use the below command:
-
-
-
-Replace {''} with your locally running orchestrator http address.
-```bash wrap lines icon="terminal" Off-Chain Video Gateway
-livepeer -gateway \
- -network offchain \
- # Minimum required video flags
- -rtmpAddr=0.0.0.0:1935 \
- -httpAddr=0.0.0.0:8935 \
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9 \
- # You will need to add your local orchestrator address if you are running off-chain
- -orchAddr= #comma separated list of orchestrator addresses
- # Example: -orchAddr=http://192.168.1.100:8935,http://192.168.1.101:8935
- # You can also use a JSON file: -orchAddr=/path/to/orchestrators/orchestrators-portal.json
-```
-
-
-Replace {''} with publicly available orchestrator addresses.
-
-```bash wrap lines icon="link" On-Chain Video Gateway
-livepeer -gateway \
- -network arbitrum-one-mainnet \
- # See the on-chain setup guide for more details on these flags
- -ethUrl= \
- -ethAcctAddr= \
- -ethPassword= \
- -ethKeystorePath= \
- # Minimum required video flags
- -rtmpAddr=0.0.0.0:1935 \
- -httpAddr=0.0.0.0:8935 \
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9 \
- # Price per unit is required on-chain (see pricing guide)
- -maxPricePerUnit=1000 \
- # You will need to connect to a public orchestrator if you are running onchain
- -orchAddr= #comma separated list of orchestrators
- # Example: -orchAddr=https://orch1.example.com:8935,https://orch2.example.com:8935
- # You can also use a JSON file: -orchAddr=/path/to/orchestrators/orchestrators-portal.json
-
-```
-
-Livepeer does not currently maintain a list of publicly available Orchestrators. You need to discover them through:
-
-- **Livepeer CLI**: Use livepeer_cli → Option 9: "List registered orchestrators"
-- **Network discovery**: The gateway discovers orchestrators from the on-chain registry
-- **Community resources**: Check Livepeer community channels or documentation
-
-Jump to the
-
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
-flowchart TB
- subgraph INPUT["Video Input Sources"]
- direction LR
- RTMP["RTMP Stream
:1935"] - HTTP["HTTP Upload
:8935"] - end - - GATEWAY["Gateway Node
LivepeerNode
-gateway mode"] - - INPUT --> GATEWAY - - subgraph MANAGER["Broadcast Session Manager"] - BSM["BroadcastSessionsManager
Manages transcoding sessions
Selects orchestrators"] - end - - GATEWAY --> BSM - - subgraph PROCESSING["Video Processing Pipeline"] - direction TB - SEG["Segment Video
Split into chunks"] - TRANS["Send to Orchestrators
with payment tickets"] - ORCH["Orchestrators
Transcode segments
Multiple renditions"] - RECEIVE["Receive Results
Transcoded segments"] - end - - BSM --> SEG --> TRANS --> ORCH --> RECEIVE - - subgraph OUTPUT["Output & Delivery"] - direction LR - HLS["HLS Manifest
.m3u8"] - RENDITIONS["Multiple Renditions
240p, 360p, 720p, 1080p"] - end - - RECEIVE --> HLS --> RENDITIONS - - subgraph PAYMENT["Payment System"] - direction TB - PM["Payment Manager
Generate tickets"] - TICKETS["Per-segment payments
Based on pixels transcoded"] - end - - TRANS --> PM --> TICKETS --> ORCH - - subgraph STORAGE["Storage (Optional)"] - OBJ["Object Store
S3/IPFS"] - end - - RENDITIONS -.-> OBJ - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef payment fill:#1a1a1a,color:#fff,stroke:#fbbf24,stroke-width:2px - class RTMP,HTTP,BSM,SEG,TRANS,ORCH,RECEIVE,HLS,RENDITIONS video - class PM,TICKETS payment - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGER fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PROCESSING fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style OUTPUT fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#fbbf24,stroke-width:1px - style STORAGE fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,stroke-dasharray: 5 5 -``` - -
-
-
- go-livepeer/core/livepeernode.go
-
-
-{/* 3. Main Flags */}
-
-## Essential Configuration Flags
-
-#### Required Flags
-
-
- Enable Gateway mode
-
-
- Set to the blockchain network for production gateways `arbitrum-one-mainnet`
-
-
- Set to `http://:` to connect to orchestrators
-
-#### Network Configuration
-
- Set to `0.0.0.0:1935` to allow external RTMP connections
-
-
- Set to `0.0.0.0:8935` to allow external HLS/API access
-
-#### Transcoding Configuration
-
- Set to `path/to/transcodingOptions.json` to use a custom transcoding configuration
-
-#### Additional On-Chain Flags
-Add these flags for on-chain configuration. See
- value:
- "arbitrum-one-mainnet"
- ,
- ]}
-/>
-
- value:
- "1000"
- ,
- ]}
-/>
-
- value:
- "YOUR_RPC_URL"
- ,
- ]}
- required
-/>
-
- value:
- "YOUR_ETH_ADDRESS"
- ,
- ]}
-/>
-
- value:
- "YOUR_PASSWORD"
- ,
- ]}
-/>
-
- value:
- "KEYSTORE_PATH"
- ,
- ]}
-/>
-
-
-
-.
-
-
-.
-
-
-.
-
-
-
-```bash wrap icon="docker" Create docker-compose.yml
-# 1. Create a basic docker-compose.yml
-cat > docker-compose.yml << EOF
-version: '3.9'
-services:
- gateway:
- image: livepeer/go-livepeer:master
- ports:
- - 1935:1935 # RTMP ingest
- - 8935:8935 # HLS/API
- volumes:
- - gateway-data:/root/.lpData
- command: |
- -gateway
- -network offchain
- -rtmpAddr=0.0.0.0:1935
- -httpAddr=0.0.0.0:8935
- -orchAddr=https://orchestrator.example.com:8935
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9,P720p30fps16x9
-
-volumes:
- gateway-data:
-EOF
-```
-
-Start the Gateway
-
-```bash wrap icon="docker" Start the gateway
-# 2. Start the gateway
-docker-compose up -d
-```
-
-
-
-.
-
-
-
-```bash
-livepeer -gateway \
- -network offchain \
- -transcodingOptions=${env:HOME}/.lpData/offchain/transcodingOptions.json \
- -orchAddr=0.0.0.0:8935 \
- -httpAddr=0.0.0.0:9935 \
- -v=6
-```
-
-
-
-
-```bash wrap icon="docker" Create docker-compose.yml
-# 1. Create a basic docker-compose.yml
-cat > docker-compose.yml << EOF
-version: '3.9'
-services:
- gateway:
- image: livepeer/go-livepeer:master
- ports:
- - 1935:1935 # RTMP ingest
- - 8935:8935 # HLS/API
- volumes:
- - gateway-data:/root/.lpData
- command: |
- -gateway
- -network arbitrum-one-mainnet
- -rtmpAddr=0.0.0.0:1935
- -httpAddr=0.0.0.0:8935
- -orchAddr=https://orchestrator.example.com:8935
- -transcodingOptions=P240p30fps16x9,P360p30fps16x9,P720p30fps16x9
- -ethUrl \
- -ethAcctAddr \
- -ethPassword \
- -ethKeystorePath \
- -maxPricePerUnit 1000
-
-volumes:
- gateway-data:
-EOF
-```
-
-Start the Gateway
-
-```bash wrap icon="docker" Start the gateway
-# 2. Start the gateway
-docker-compose up -d
-```
-
-
-
-.
-
-
-
-```bash
-livepeer -gateway \
- -network arbitrum-one-mainnet \
- -ethUrl= \
- -ethAcctAddr= \
- -ethPassword= \
- -ethKeystorePath= \
- -maxPricePerUnit=1000 \
- -orchAddr= \
- -monitor=true
-```
-
-## Transcoding Options JSON
-
-Livepeer supports JSON configuration files for transcoding options through the `-transcodingOptions` flag.
-
-The transcodingOptions.json file lets you precisely control the encoding ladder.
-
-This file is a custom configuration file containing an array of rendition objects that defines which renditions (resolutions + bitrates)
-your Gateway will produce for each incoming stream.
-
-It overrides the default built-in ladder (e.g., P240p30fps16x9, etc.).
-
-```json wrap lines icon="brackets-curly" transcodingOptions.json example
-[
- {
- // required
- "bitrate": 1600000,
- "width": 854,
- "height": 480,
- // optional
- "name": "480p0",
- "fps": 0,
- "profile": "h264constrainedhigh",
- "gop": "1"
- },
- {
- // required
- "bitrate": 3000000,
- "width": 1280,
- "height": 720,
- // optional
- "name": "720p0",
- "fps": 0,
- "profile": "h264constrainedhigh",
- "gop": "1"
- },
- {
- // required
- "bitrate": 6500000,
- "width": 1920,
- "height": 1080,
- // optional
- "name": "1080p0",
- "fps": 0,
- "profile": "h264constrainedhigh",
- "gop": "1"
- }
-]
-```
-
-#### Notes
-
-- JSON configuration only applies to transcoding options, not other gateway flags
-- The file must contain valid JSON with the specified structure
-- All fields are optional except width, height, and bitrate
-- You can mix JSON configuration with other command-line flags
-
-
- Configure pricing for your gateway.
-
-
-## Full Configuration Flag Reference
-
-### Essential Changes
-
-
-
-
-
- ## Modify Config Files
-
-
-
-Create the transcodingOptions.json file using the above template.
-
-```bash icon="docker"
-nano -p /var/lib/docker/volumes/gateway-lpData/_data/transcodingOptions.json
-```
-
-Modify the docker-compose.yml file from the root user's home directory _/root/_
-and add the following below `-pixelsPerUnit=1`
-
-```bash icon="docker"
--transcodingOptions=/root/.lpData/transcodingOptions.json
-```
-
-
-
-
-Create the transcodingOptions.json file using the above template.
-
-```bash icon="linux"
-sudo nano /usr/local/bin/lptConfig/transcodingOptions.json
-```
-
-Modify the Linux Service file /etc/systemd/system/livepeer.service and add the
-following below `-pixelsPerUnit=1`
-
-```bash icon="linux"
--transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
-```
-
-
-
-
-Create the transcodingOptions.json file using the above template.
-
-Open notepad (or your text editor of choice) paste the template above and save
-the transcodingOptions.json file in the following location.
-
-In Windows, %USERNAME% is already a built-in environment variable
--> You can use it directly.
-
-```bash icon="windows"
-C:\Users\%USERNAME%\.lpData\transcodingOptions.json
-```
-
-Modify Windows bat file to include the following command after
-`-pixelsPerUnit=1`
-
-```bash icon="windows"
--transcodingOptions=C:\Users\%USERNAME%\.lpData\transcodingOptions.json
-```
-
-
-
-
diff --git a/v2/gateways/x-archived/about_old/architecture.mdx b/v2/gateways/x-archived/about_old/architecture.mdx
deleted file mode 100644
index 04c523b90..000000000
--- a/v2/gateways/x-archived/about_old/architecture.mdx
+++ /dev/null
@@ -1,145 +0,0 @@
----
-title: Gateway Architecture
-sidebarTitle: Architecture
-description: This page describes the architecture of Livepeer Gateways.
-keywords:
- - livepeer
- - gateways
- - about gateways
- - gateway architecture
- - gateway
- - architecture
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-purpose: landing
----
-
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-import { DoubleIconLink } from '/snippets/components/elements/links/Links.jsx'
-
-Livepeer Gateway Architecture is defined in the `livepeer-go` core codebase.
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
-flowchart TB
- subgraph INPUT["Input Sources"]
- direction LR
- RTMP["RTMP Stream"]
- HTTP["HTTP Upload"]
- AI_REQ["AI Request"]
- end
-
- GATEWAY["Gateway Node
LivepeerNode"] - - INPUT --> GATEWAY - - subgraph MANAGERS["Session Managers"] - direction LR - BSM["BroadcastSessionsManager
Video Transcoding"] - ASM["AISessionManager
AI Processing"] - end - - GATEWAY --> BSM - GATEWAY --> ASM - - subgraph VIDEO["Video Pipeline"] - SEG["Segment Processing"] - ORCH_V["Orchestrators
Transcoding"] - HLS["HLS/DASH Output"] - end - - subgraph AI["AI Pipeline"] - PROC["AI Processing"] - ORCH_AI["Orchestrators
AI Models"] - OUT_AI["AI Output
Images/Video"] - end - - BSM --> SEG --> ORCH_V --> HLS - ASM --> PROC --> ORCH_AI --> OUT_AI - - subgraph PAYMENT["Payment"] - direction LR - PAY_SEG["Per Segment"] - PAY_PIX["Per Pixel"] - end - - ORCH_V --> PAY_SEG - ORCH_AI --> PAY_PIX - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef ai fill:#1a1a1a,color:#fff,stroke:#a855f7,stroke-width:2px - class RTMP,HTTP,BSM,SEG,ORCH_V,HLS,PAY_SEG video - class AI_REQ,ASM,PROC,ORCH_AI,OUT_AI,PAY_PIX ai - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGERS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style VIDEO fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style AI fill:#0d0d0d,stroke:#a855f7,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px -``` - -
-
-### Flow Diagram
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui', 'clusterBkg': 'rgba(255,255,255,0.05)', 'clusterBorder': '#2d9a67' }}}%%
-graph TD
- classDef default stroke-width:2px
- A["Application
Daydream, ComfyUI, BYOC"] -->|Job Request| B["Gateway
Job Intake, Pricing, Capability Match"] - B -->|Route Job| C["Orchestrator
GPU Compute, AI Inference, Transcoding"] - C -->|Results| B - B -->|Response| A -``` - -
-
-
- -### Layered Architecture - -
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui', 'clusterBkg': 'rgba(255,255,255,0.05)', 'clusterBorder': '#2d9a67' }}}%%
-graph LR
- classDef default stroke-width:2px
- subgraph APP[Application Layer]
- X["User App
Web, Mobile, TouchDesigner"] - end - subgraph GW[Gateway Layer] - G1[Job Intake] - G2[Capability Discovery] - G3[Pricing & Marketplace] - G4[Routing / Scheduling] - end - subgraph ORC[Orchestrator Layer] - O1[GPU Worker] - O2[AI Models / BYOC Containers] - O3[Transcoder] - end - X --> G1 - G1 --> O1 - O1 --> G1 - G1 --> X -``` - -
diff --git a/v2/gateways/x-archived/references/technical-architecture.mdx b/v2/gateways/x-archived/references/technical-architecture.mdx
deleted file mode 100644
index 7b5c3c6b2..000000000
--- a/v2/gateways/x-archived/references/technical-architecture.mdx
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: Technical Architecture
-sidebarTitle: Technical Architecture
-description: Technical Architecture Diagrams and References
-keywords:
- - livepeer
- - gateways
- - references
- - technical architecture
- - technical
- - architecture
- - diagrams
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-purpose: reference
----
-
-
-
-
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-
-
-
-
-
-
-
-
- >Gateway: Submit job
- Gateway->>Marketplace: Query orchestrator capabilities
- Marketplace-->>Gateway: Matching candidates
- Gateway->>Orchestrator: Dispatch workload
- Orchestrator->>Gateway: Return results
- Gateway->>App: Deliver output`}
- />
-
-
-
-
-
• Segment video
• Queue + order jobs
• AI pipeline routing
• Orchestrator selection
• Verification & receipts"] - - CAM -->|"Live stream"| GATEWAY - VID -->|"VOD upload"| GATEWAY - AIIN -->|"AI job request"| GATEWAY - - subgraph JOBS["Workflows"] - VJ["Video Transcoding Job"] - AIJ["AI Inference Job
(Daydream / ComfyStream / BYOC)"] - end - - GATEWAY --> VJ - GATEWAY --> AIJ - - subgraph ORCH["Orchestrator Network (GPU Operators)"] - O1["Orchestrator A
GPU Pool"] - O2["Orchestrator B
GPU Pool"] - O3["Orchestrator C
GPU Pool"] - end - - VJ -->|"Transcode segments"| O1 - VJ --> O2 - AIJ -->|"Run model / inference"| O1 - AIJ --> O3 - - subgraph OUTPUTS["Outputs"] - HLS["Adaptive Bitrate Video (HLS/LL-HLS)"] - AIOUT["AI Frames / Stylized Video"] - end - - O1 --> GATEWAY - O2 --> GATEWAY - O3 --> GATEWAY - - GATEWAY --> HLS - GATEWAY --> AIOUT - - ETH[("Arbitrum Blockchain
Payments • Tickets • Rewards")] - GATEWAY --> ETH - O1 --> ETH - O2 --> ETH - O3 --> ETH - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px`} - /> -
-
-
-
-
-{/* ### Marketplace Interaction Model
-
- P
- O --> P
- A --> D
- P --> R
- R --> A`}
-/>
-
-### BYOC (Bring Your Own Container) Architecture
-
- B[Compliant Runtime Spec]
- B --> C[Gateway Intake]
- C --> D[Capability Validation]
- D --> E[Orchestrator Container Runner]
- E --> F[GPU Execution]
- F --> C --> A`}
-/> */}
diff --git a/v2/gateways/x-archived/run-a-gateway/connect/connect-with-offerings.mdx b/v2/gateways/x-archived/run-a-gateway/connect/connect-with-offerings.mdx
deleted file mode 100644
index 5f9eb8006..000000000
--- a/v2/gateways/x-archived/run-a-gateway/connect/connect-with-offerings.mdx
+++ /dev/null
@@ -1,120 +0,0 @@
----
-title: Discover & Connect Marketplace Compute Services
-sidebarTitle: Discover & Connect Services
-description: >-
- This page explains how to find and broker Orchestrator AI & Video Offerings
- via your Gateway for Livepeer Application consumption.
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - connect
- - connect with offerings
- - discover
- - marketplace
- - compute
- - services
- - explains
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
----
-
-
-
-
-import { CustomCallout } from '/snippets/components/elements/links/Links.jsx'
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-
-# How to Discover & Connect Marketplace Offerings
-
-This page explains how Gateways can discover and offer Orchestrator Services,
-available on the Marketplace, to Applications & Builders.
-
-## Discovery Process
-
-Gateways discover orchestrators through the orchestrator pool in `discovery/discovery.go` [discovery.go:64-111](https://github.com/livepeer/go-livepeer/blob/5691cb48/discovery/discovery.go#L64-L111)
-
-1. **Query orchestrators**: Get `OrchestratorInfo` from each orchestrator
-2. **Filter capabilities & price**: Match against required capabilities & pricing limits & optionally rank results
-3. **Expose results**: Make matching orchestrator services available through HTTP endpoints
-4. **Route requests**: Forward incoming requests to selected orchestrators
-
-## Find All Orchestrators & Offerings
-
-The `/getNetworkCapabilities` endpoint in [server/handlers.go](https://github.com/livepeer/go-livepeer/blob/5691cb48/server/handlers.go#L275-L295)
-exposes all available orchestrator offerings
-
-```go
-func (s *LivepeerServer) getNetworkCapabilitiesHandler() http.Handler {
- return http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
- // Returns orchestrators with their capabilities, pricing, and hardware
- })
-}
-```
-
-**Response Data Structure**
-
-The response uses NetworkCapabilities structure from `common/types.go` [types.go:166-176](https://github.com/livepeer/go-livepeer/blob/5691cb48/common/types.go#L166-L176)
-
-```go
-type NetworkCapabilities struct {
- Orchestrators []*OrchNetworkCapabilities `json:"orchestrators"`
-}
-
-type OrchNetworkCapabilities struct {
- Address string `json:"address"`
- LocalAddress string `json:"local_address"`
- OrchURI string `json:"orch_uri"`
- Capabilities *net.Capabilities `json:"capabilities"`
- CapabilitiesPrices []*net.PriceInfo `json:"capabilities_prices"`
- Hardware []*net.HardwareInformation `json:"hardware"`
-}
-```
-
-## Gateway
-
-Gateways expose offerings describing:
-
-### **1. Supported Models**
-
-Example:
-
-- `stable-diffusion-v1.5`
-- `depth-anything`
-- `controlnet_lineart`
-- `ip_adapter`
-
-### **2. Supported Pipelines**
-
-- Daydream-style real-time style transfer
-- ComfyStream workflows
-- BYOC containers
-- Custom inference graphs
-
-### **3. Pricing**
-
-A Gateway may price:
-
-- `$0.004 / frame`
-- `$0.06 / second`
-- `$0.0005 / inference token`
-
-### **4. Regions**
-
-Example:
-
-- `us-east`
-- `eu-central`
-- `ap-southeast`
-
-### **5. Reliability Scores**
-
-Gateways may publish:
-
-- Availability %
-- Average inference latency
-- Failover configuration
diff --git a/v2/gateways/x-archived/run-a-gateway/install/community-projects.mdx b/v2/gateways/x-archived/run-a-gateway/install/community-projects.mdx
deleted file mode 100644
index 7d6a09c5a..000000000
--- a/v2/gateways/x-archived/run-a-gateway/install/community-projects.mdx
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: 'Easy Install [DevOps & Community Projects]'
-sidebarTitle: Single Click Deployment
-description: Community CICD Pipelines to make installation accessible & easy
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - install
- - community projects
- - easy
- - devops
- - community
- - projects
- - pipelines
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-icon: timeline-arrow
-tag: beta
----
-
-
-
-
-
-Page Not Finalised
-
-**Notes:**
-
-- Gateway hub will be an automated addition pipeline with human in the loop.
- -**TODO:** - -- Verify all content -- Add a real link for community submissions -- Not happy with contribution layout -
-
-import { YouTubeVideo } from '/snippets/components/content/video.jsx';
-import { GotoCard, GotoLink } from '/snippets/components/elements/links/Links.jsx'
-
-# Gateway HUB
-
-A collection of community projects that make running a Livepeer Gateway easy.
-
-**Quick Links**
-
-
-
- Fully Managed DevOps Platform for Livepeer
-
-
- Coming Soon
-
-
-Have a Guide or Project to Contribute?
-
-
-
-
-## GWID (Gateway Wizard)
-
-
- {' '}
- This is a community contributed project. Please contact the team for help & support.{' '}
-
-
-GWID is a fully managed DevOps platform for Livepeer. It provides a simple and easy way to deploy and manage Livepeer gateways. It also provides easy integration with other services to test the gateway.
-
-
-
- View the GWID repository on GitHub
-
-
-### GWID RFP & Updates
-
-- [GWID SPE Proposal: Gateway Wizard Phase 1](https://forum.livepeer.org/t/gwid-spe-pre-proposal-gateway-wizard-phase-1/2868)
-- [Get to know GWID - A Fully Managed DevOp Platform for Livepeer](https://forum.livepeer.org/t/get-to-know-gwid-and-the-team-a-fully-managed-devop-platform-for-livepeer/2851)
-
-### GWID Documentation
-
-Below is the current README from the GWID repository.
-
-
- The embedded GWID README is unavailable in this docs branch.
- Use the GitHub repository link above to review the current installation and deployment instructions.
-
diff --git a/v2/gateways/x-archived/run-a-gateway/install/linux-install.mdx b/v2/gateways/x-archived/run-a-gateway/install/linux-install.mdx
deleted file mode 100644
index 1ab4e21bd..000000000
--- a/v2/gateways/x-archived/run-a-gateway/install/linux-install.mdx
+++ /dev/null
@@ -1,353 +0,0 @@
----
-title: Linux Install
-sidebarTitle: Linux Install
-description: How to install a Livepeer Gateway from source binary
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - install
- - linux install
- - linux
- - gateway
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-icon: linux
----
-
-
-
-
-import { StyledStep, StyledSteps } from '/snippets/components/wrappers/steps/Steps.jsx'
-import { CustomCodeBlock, CodeComponent } from '/snippets/components/content/code.jsx'
-import { DownloadButton } from '/snippets/components/elements/buttons/Buttons.jsx'
-import { latestVersion } from '/snippets/automations/globals/globals.mdx'
-
- Dual AI & Video
-{latestVersion} (dynamically fetched)
-
-This guide covers installing the Livepeer Gateway from source binary on Linux.
-
-
-
- Ensure you have `wget` and `tar` installed & up-to-date on your system.
- - `tar` is pre-installed on macOS and most linux distributions.
-
-
-
- You can use brew or your package manager to install `wget`
-
-
- **Linux Ubuntu/Debian**
- ```bash icon="terminal" lines
- sudo apt-get update && sudo apt-get upgrade wget
- sudo apt install -y wget
- ```
-
- **Alpine**
- ```bash lines icon="terminal"
- sudo apk update
- sudo apk add wget
- ```
-
- **Fedora/RHEL/CentOS/Rocky**
- ```bash lines icon="terminal"
- sudo dnf update
- sudo dnf install -y wget
- ```
-
- **Arch**
- ```bash lines icon="terminal"
- sudo pacman -Syu
- sudo pacman -S wget
- ```
-
-
-
- ```bash lines icon="terminal" brew install wrap
- # Install brew if not already installed
- /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
- ```
- ```bash lines icon="terminal" version check
- # Check if wget is installed
- brew list --versions wget
- brew list --versions tar
- ```
-
- ```bash lines icon="terminal" upgrade wget
- # Upgrade wget if already installed
- brew upgrade wget
- brew upgrade tar
- ```
-
- ```bash lines icon="terminal" install wget
- # Install wget if not already installed
- brew install wget
- ```
-
- ```bash lines icon="terminal" update all brew packages
- # Update all brew packages
- brew update && bre upgrade
- ```
-
-
-
-
- MacOS users will also need to install `libx11` and `--cask xquartz`
-
-You can use brew or curl to install `wget`
-
-
- Using [brew](https://brew.sh/)
- ```bash lines icon="terminal" brew wrap
- # Install brew if not already installed
- /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
-
- # Check if wget is installed
- brew list --versions wget
-
- # Upgrade wget if already installed
- brew upgrade wget
-
- # Install wget if not already installed
- brew install wget libx11 --cask xquartz
-
- # Update all brew packages
- brew update && bre upgrade
- ```
-
-
-
- Using [curl](https://curl.haxx.se/)
-
- ```bash lines icon="terminal" curl wrap - curl -LO https://ftp.gnu.org/gnu/wget/wget-1.21.4.tar.gz - tar -xzf wget-1.21.4.tar.gz - cd wget-1.21.4 - ./configure && make && sudo make install - ``` -
-
-
-
-
-
-
-
- Note: {''} is dynamically fetched from the [go-livepeer releases page](https://github.com/livepeer/go-livepeer/releases) via Gtihub API.
-
- In case of fetch issues: Replace {''} with the latest version number
- ```bash lines icon="terminal" wrap wget
- sudo wget https://github.com/livepeer/go-livepeer/releases/download//livepeer-linux-amd64.tar.gz
- ```
-
-
-
-
- Note: {''} is dynamically fetched from the [go-livepeer releases page](https://github.com/livepeer/go-livepeer/releases) via Gtihub API.
-
- Intel
-
- ```bash lines icon="terminal" wrap curl
- curl -LO https://github.com/livepeer/go-livepeer/releases//download/livepeer-darwin-amd64.tar.gz
- tar -zxvf livepeer-darwin-amd64.tar.gz
- sudo mv livepeer-darwin-amd64/* /usr/local/bin/
- livepeer -gateway
- ```
-
-
- Apple Silicon
-
- ```bash lines icon="terminal" wrap curl
- curl -LO https://github.com/livepeer/go-livepeer/releases//download/livepeer-darwin-arm64.tar.gz
- tar -zxvf livepeer-darwin-arm64.tar.gz
- sudo mv livepeer-darwin-arm64/* /usr/local/bin/
- livepeer -gateway
- ```
-
-
-
-
- In case of fetch issues: Replace {''} with the latest version number
- ```bash lines icon="terminal" wrap curl
- curl -LO https://github.com/livepeer/go-livepeer/releases/download//livepeer-linux-amd64.tar.gz
- ```
-
-
-
-
- Unpack and remove the compressed file
-
- ``` bash icon="terminal" lines
- sudo tar -zxvf livepeer-linux-amd64.tar.gz
- sudo rm livepeer-linux-amd64.tar.gz
- sudo mv livepeer-linux-amd64/* /usr/local/bin/
- ```
-
-
-
-
-
-
- Off-chain mode is the default network and requires no blockchain connectivity (no wallet or RPC).
-
- - defaultNetwork := "offchain"
-
- ```bash icon="terminal" lines run the Gateway
- # Run the gateway
- livepeer -gateway
- ```
-
-
-
-
- You will need to **Generate Keystore File**
-
-
- When generating a new keystore file, the program will prompt you for a
- password. This password is used to decrypt the keystore file and access the
- private key. Make sure to never share or lose access to either the password or
- the keystore file
-
-
- ```bash icon="terminal" lines Run the Gateway
- # Set your Arbitrum RPC URL
- export RPC_URL=""
-
- # Run the gateway
- livepeer -network arbitrum-one-mainnet -ethUrl $RPC_URL -gateway
- ```
-
-
-
- **Output Example**
- ```bash icon="terminal" lines Off-Chain Gateway Example Output
- >_ livepeer -gateway
-
- *---------*------*
- | Gateway | true |
- *---------*------*
- I1222 12:37:23.339916 97244 starter.go:537] ***Livepeer is running on the offchain network***
- I1222 12:37:23.340276 97244 starter.go:554] Creating data dir: /Users//.lpData/offchain
- I1222 12:37:23.344584 97244 starter.go:723] ***Livepeer is in off-chain mode***
- E1222 12:37:23.345022 97244 starter.go:1586] No orchestrator specified; transcoding will not happen
- I1222 12:37:23.350972 97244 starter.go:1827] ***Livepeer Running in Gateway Mode***
- I1222 12:37:23.350991 97244 starter.go:1828] Video Ingest Endpoint - rtmp://127.0.0.1:1935
- I1222 12:37:23.351002 97244 starter.go:1837] Livepeer Node version: 0.8.8
- I1222 12:37:23.351124 97244 mediaserver.go:247] HTTP Server listening on http://127.0.0.1:9935
- I1222 12:37:23.351398 97244 webserver.go:20] CLI server listening on 127.0.0.1:5935
- ```
-
-
-
-
-Jump to [Configuration](/v2/gateways/run-a-gateway/configure/configuration-overview) to
-finish configuring the Gateway
-
-
-
-
-# Create a file containing your Gateway Ethereum password
-
-```text
-sudo mkdir /usr/local/bin/lptConfig
-sudo nano /usr/local/bin/lptConfig/node.txt
-```
-
-Enter your password and save the file
-
-
-
-# Create a system service
-
-```text
-sudo nano /etc/systemd/system/livepeer.service
-```
-
-Paste and update the following startup script with your personal info:
-
-```jsx
-[Unit]
-Description=Livepeer
-
-[Service]
-Type=simple
-User=root
-Restart=always
-RestartSec=4
-ExecStart=/usr/local/bin/livepeer -network arbitrum-one-mainnet \
--ethUrl= \
--cliAddr=127.0.0.1:5935 \
--ethPassword=/usr/local/bin/lptConfig/node.txt \
--maxPricePerUnit=300 \
--broadcaster=true \
--serviceAddr=:8935 \
--transcodingOptions=/usr/local/bin/lptConfig/transcodingOptions.json \
--rtmpAddr=0.0.0.0:1935 \
--httpAddr=0.0.0.0:8935 \
--monitor=true \
--v 6
-
-[Install]
-WantedBy=default.target
-```
-
-Start the system service
-
-```text
-sudo systemctl daemon-reload
-sudo systemctl enable --now livepeer
-```
-
-Open the Livepeer CLI
-
-```text
-livepeer_cli -host 127.0.0.1 -http 5935
-```
-
-
-
diff --git a/v2/gateways/x-archived/run-a-gateway/install/windows-install.mdx b/v2/gateways/x-archived/run-a-gateway/install/windows-install.mdx
deleted file mode 100644
index 573f64979..000000000
--- a/v2/gateways/x-archived/run-a-gateway/install/windows-install.mdx
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: Windows Install
-sidebarTitle: Windows Install
-description: How to install a Livepeer Gateway using Windows
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - install
- - windows install
- - windows
- - gateway
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-icon: windows
----
-
-
-
-
-import { StyledSteps, StyledStep } from '/snippets/components/wrappers/steps/Steps.jsx'
-import { CustomCodeBlock } from '/snippets/components/content/code.jsx'
-import { latestVersion as version} from '/snippets/automations/globals/globals.mdx'
-
-
- This content is referenced from the [current docs windows install
- guide](https://docs.livepeer.org/gateways/guides/windows-install) **TODO** - [
- ] UNVERIFIED INSTALL DOCS - VERIFY CONTENT - [ ] MOVE ETH WALLET SETUP CONTENT
-
-
- Video Only
-{version} (dynamically fetched)
-
-This guide covers installing the Livepeer Gateway from source binary on Windows.
-
-This is a Linux distribution operating in WSL2
-
-
-
- Install WSL2 (Windows host)
-
- ```bash icon="terminal" lines In Powershell(Admin)
- wsl --install
- # Reboot when prompted.
- ```
-
- ```bash icon="terminal" wrap lines Check
- wsl --status
- # Output: Version: WSL 2
- # Output:Default distro: Ubuntu
- ```
-
- ```bash icon="terminal" wrap lines Enter WSL
- wsl
- ```
-
-
-
- ## Download and unzip the Livepeer binary
-
- In case of fetch issues: Replace {''} with the latest [go-livepeer release](https://github.com/livepeer/go-livepeer/releases) number
- ```bash icon="terminal" wrap lines
- https://github.com/livepeer/go-livepeer/releases/download//livepeer-windows-amd64.zip
- ```
-
-
-
-
- ## Create a bat file to launch Livepeer.
-
-Create a file named gateway.bat:
-
-```bash icon="terminal" wrap lines
- touch gateway.bat
-```
-
-Use the following as a template, adding your personal info where needed (on-chain) and save a .bat file
-in the same directory as the Livepeer executable.
-
-
-
- ```bash icon="terminal" wrap lines
- livepeer.exe -network=offchain -gateway -cliAddr=127.0.0.1:5935 -monitor=true -v=6 -rtmpAddr=0.0.0.0:1935 -httpAddr=0.0.0.0:8935
-
- PAUSE
- ```
-
-
- ```bash icon="terminal" wrap lines
- livepeer.exe -network=arbitrum-one-mainnet -ethUrl= -ethAcctAddr= -ethPassword= -ethKeystorePath= -gateway -cliAddr=127.0.0.1:5935 -rtmpAddr=0.0.0.0:1935 -httpAddr=0.0.0.0:8935 -maxPricePerUnit=300 -monitor=true -v=6
-
- PAUSE
- ```
-
- **Required On-Chain Parameters**
-
- Network Configuration
- - `-network`: Must be set to the blockchain network `arbitrum-one-mainnet`
-
- Ethereum Configuration
- - `-ethUrl`: Ethereum JSON-RPC URL (required for on-chain)
- - `-ethAcctAddr`: Your Ethereum account address
- - `-ethPassword`: Password for your ETH account or path to password file
- - `-ethKeystorePath`: Path to your keystore directory or keyfile
-
-
-
-
-
-
-
-## Start the Livepeer Gateway
-
-Start the Livepeer Gateway using the .bat file.
-
- ```bash icon="terminal" wrap lines
- livepeer_cli.exe -host 127.0.0.1 -http 5935
- ```
-
-
-
- _If you'd like the Gateway to start with Windows you can create a System service
- using [NSSM](https://nssm.cc/) or the Windows Task Scheduler._
-
-
-
-{' '}
-
-
- Open the Livepeer CLI, then Jump to [Configuration
- Options](/v2/gateways/run-a-gateway/configure/configuration-overview) to finish
- configuring the Gateway
-
diff --git a/v2/gateways/x-archived/run-a-gateway/monitor/monitor-and-optimise.mdx b/v2/gateways/x-archived/run-a-gateway/monitor/monitor-and-optimise.mdx
deleted file mode 100644
index c65a2adbf..000000000
--- a/v2/gateways/x-archived/run-a-gateway/monitor/monitor-and-optimise.mdx
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Monitor & Optimise Gateway Services
-sidebarTitle: Monitor & Optimise
-description: Monitor & Optimise Gateway Services
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - monitor
- - monitor and optimise
- - optimise
- - gateway
- - services
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
-purpose: concept
----
-
-
-
-
-import { DoubleIconLink } from '/snippets/components/elements/links/Links.jsx'
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-
- Currently operating as a brainstorming page
-
-## Request Routing
-
-**Request Processing Flow (both)**
-
-- **Request Validation**: OpenAPI validation middleware validates request structure
-- **Session Selection**: AISessionManager selects appropriate orchestrator based on model capability
-- **Payment Processing**: Calculates payment based on pixel count for non-live endpoints
-- **Model Execution**: Sends request to AI worker with specified model
-
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
-flowchart TB
- A[Incoming Request] --> B[Request Validation]
- B --> C[Session Selection]
- C --> D[Payment Processing]
- D --> E[Model Execution]
- E --> F[Response]
-
- style A fill:#1a1a1a,stroke:#2d9a67,color:#fff
- style B fill:#1a1a1a,stroke:#2d9a67,color:#fff
- style C fill:#1a1a1a,stroke:#2d9a67,color:#fff
- style D fill:#1a1a1a,stroke:#2d9a67,color:#fff
- style E fill:#1a1a1a,stroke:#2d9a67,color:#fff
- style F fill:#1a1a1a,stroke:#2d9a67,color:#fff
-```
-
-
-
-#### Transcoding Requests
-
-Traditional video transcoding requests are handled through:
-
-- **RTMP ingest**: Port `1935` by default
-- **HTTP push**: `/live/{streamKey}` endpoint when `-httpIngest` is enabled
-- **HLS output**: Adaptive bitrate streams for playback
-
-#### AI Requests
-
-AI processing requests are routed through dedicated endpoints (fixme) OpenAPI Spec is here: ai/worker/api/openapi.json
-
-
- Generate images from text prompts.
- Uses `jsonDecoder` for parsing
-
-
- Transform images with prompts.
- Uses `multipartDecoder` for file uploads
-
-
- Create videos from images.
- Uses `multipartDecoder` for file uploads
-
-
- Upscale (enhance) images to higher resolution.
- Uses `multipartDecoder` for file uploads
-
-
- Apply transformations to a live video streamed to the returned endpoints.
- Live video endpoint has specialized handling for real-time streaming with MediaMTX integration
-
-
-## Payment Models
-
-The dual setup handles two different payment models:
-
-#### Transcoding Payments
-
-Basis: Per video segment processed
-Method: Payment tickets sent with each segment
-Verification: Multi-orchestrator verification for quality assurance
-
-#### AI Payments
-
-Basis: Per pixel processed (width × height × outputs)
-Method: Pixel-based payment calculation
-Live Video: Interval-based payments during streaming
-
-## Operational Considerations
-
-#### Resource Allocation
-
-When running dual setup, consider:
-
-- GPU resources: Shared between transcoding and AI workloads
-- Memory: AI models require significant RAM when loaded ("warm")
-- Network: Bandwidth for both stream ingest and AI request/response
-
-#### Monitoring
-
-Monitor both workload types:
-
-- Transcoding: Segment processing latency, success rates
-- AI: Model loading times, inference latency, pixel processing rates
-
-#### Scaling Strategies
-
-- Horizontal: Deploy multiple gateway instances behind a load balancer
-- Vertical: Allocate more GPU resources for AI model parallelism
-- Specialized: Separate nodes for transcoding vs AI based on workload patterns
diff --git a/v2/gateways/x-archived/run-a-gateway/run-a-gateway.mdx b/v2/gateways/x-archived/run-a-gateway/run-a-gateway.mdx
deleted file mode 100644
index 61517b53b..000000000
--- a/v2/gateways/x-archived/run-a-gateway/run-a-gateway.mdx
+++ /dev/null
@@ -1,239 +0,0 @@
----
-title: Run a Gateway
-sidebarTitle: Run A Gateway
-description: |-
- Connect Applications with Video & AI services by running your own Gateway!
- This page gives an overview of the steps to run a Gateway node.
-keywords:
- - livepeer
- - gateways
- - run a gateway
- - gateway
- - connect
- - applications
- - video
-'og:image': /snippets/assets/site/og-image/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-audience: gateway-operator
----
-
-
-import { GotoLink } from '/snippets/components/elements/links/Links.jsx'
-import { ScrollableDiagram } from '/snippets/components/content/zoomableDiagram.jsx'
-import { StyledSteps, StyledStep } from '/snippets/components/wrappers/steps/Steps.jsx'
-import { FlexContainer } from '/snippets/components/wrappers/containers/Layout.jsx'
-
-
-## Introduction Gateways are essential infrastructure in the Livepeer network. They -provide the service coordination layer (routing & verification) that connects applications -to the decentralized GPU compute layer (DePIN). This guide explains the requirements, -setup steps, and best practices for running a Gateway node." - -## Gateway Modes - -You can run a gateway - -- Video Only -> traditional transcoding services
-- AI Only -> AI inference services
-- Dual: AI & Video -> both video transcoding and AI
- inference services
-
-## Gateway Architecture
-
-
-```mermaid
-%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#fff', 'primaryBorderColor': '#2d9a67', 'lineColor': '#2d9a67', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#1a1a1a', 'background': '#0d0d0d', 'fontFamily': 'system-ui' }}}%%
-flowchart LR
- subgraph INPUT["Input Sources"]
- CAM["Camera / RTMP / WebRTC"]
- VID["Video File"]
- AIIN["AI Prompt / Model Request"]
- end
-
- GATEWAY["Gateway Node
• Ingest (RTMP/HTTP/WebRTC)
• Segment video
• Queue + order jobs
• AI pipeline routing
• Orchestrator selection
• Verification & receipts"] - - CAM -->|"Live stream"| GATEWAY - VID -->|"VOD upload"| GATEWAY - AIIN -->|"AI job request"| GATEWAY - - subgraph JOBS["Workflows"] - VJ["Video Transcoding Job"] - AIJ["AI Inference Job
(Daydream / ComfyStream / BYOC)"] - end - - GATEWAY --> VJ - GATEWAY --> AIJ - - subgraph ORCH["Orchestrator Network (GPU Operators)"] - O1["Orchestrator A
GPU Pool"] - O2["Orchestrator B
GPU Pool"] - O3["Orchestrator C
GPU Pool"] - end - - VJ -->|"Transcode segments"| O1 - VJ --> O2 - AIJ -->|"Run model / inference"| O1 - AIJ --> O3 - - subgraph OUTPUTS["Outputs"] - HLS["Adaptive Bitrate Video (HLS/LL-HLS)"] - AIOUT["AI Frames / Stylized Video"] - end - - O1 --> GATEWAY - O2 --> GATEWAY - O3 --> GATEWAY - - GATEWAY --> HLS - GATEWAY --> AIOUT - - ETH[("Arbitrum Blockchain
Payments • Tickets • Rewards")] - GATEWAY --> ETH - O1 --> ETH - O2 --> ETH - O3 --> ETH - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - -``` -
-
-
- -## Gateway Operator Journey - -
-
- B
- B --> C1
- C1 --> C2
- C2 --> D
- D --> E1
- E1 --> E2
- E2 --> F
-
- classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px`}
- />
-
-
-
-
-
- Check hardware, network, and software requirements.
-
-
- Install the Livepeer Gateway software.
-
-
- Configure transcoding options, models, pipelines & pricing
-
-
- Price & publish offerings to the Marketplace.
-
-
- Connect with Orchestrators, price & route offerings in the Marketplace.
-
-
- Monitor performance, optimise routing & service quality.
-
-
-
-
-
-
-## Related Pages
-
- Looking for information on how gateways earn fees for services?
-
-
- Just want to get started?
-
-```text
diff --git a/v2/home/about-livepeer/evolution.mdx b/v2/home/about-livepeer/evolution.mdx
index a4e22ed20..b7fc2b65b 100644
--- a/v2/home/about-livepeer/evolution.mdx
+++ b/v2/home/about-livepeer/evolution.mdx
@@ -24,12 +24,13 @@ keywords:
audience: everyone
lastVerified: 2026-03-17
---
+{/* The journey of Livepeer from video to AI - key achievements */}
import { YouTubeVideo } from '/snippets/components/displays/video/Video.jsx';
-import { Image } from '/snippets/components/elements/images/Image.jsx';
-import { LinkArrow } from '/snippets/components/elements/links/Links.jsx';
+import { Image } from '/snippets/components/elements/images/Image.jsx'
+import { LinkArrow } from '/snippets/components/elements/links/Links.jsx'
+
-{/* The journey of Livepeer from video to AI - key achievements */}
{/*
- This release upgrades the default starter workflow to LTX 2.3, adds new Workflow Builder features including a scheduler node and improved canvas UX.
-
- ## Highlights
-
- * **LTX 2.3 Default Workflow** — The starter workflow now uses LTX 2.3 text-to-video (replacing Paint Blobs), so new users can generate video without a camera input
- * **Scheduler Node** — A new browser-side scheduler node that fires named trigger outputs at configurable time points, with orange trigger connectors and edge flashing on fire
- * **Canvas UX Improvements** — A floating [+] button and an empty-state placeholder make it easier to add nodes when starting from scratch in the Workflow Builder
-
- ## What's Changed
-
- * Replace Paint Blobs with LTX 2.3 and enrich onboarding_completed event
- * graph: Add frontend-only scheduler node with trigger type system
- * graph: Add [+] button and empty state placeholder to canvas
- * fix: pipelines getting stuck in graph mode
- * cloud: Pre-install ltx-2 plugin in cloud Docker image
- * Livepeer network improvements: payments, text mode, local recording, and LoRA support
- * feat: add MCP server recording support and cloud connection tools
-
- **Full Changelog**: https://github.com/daydreamlive/scope/compare/v0.2.0...v0.2.1
-
-
- March 2026
}>
- ## Scope: v0.2.0
-
- Scroll for more ↓
}
-
- );
-};
-
-/**
- * @component CardBlogDataLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Card Blog Data Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {Array} [items=[]] - items prop.
- * @param {any} limit - limit prop.
- * @example
- * - No blog posts at this time. -
-
- {displayItems.map((props, idx) => (
-
- );
-};
-
-/**
- * @component ColumnsBlogCardLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Columns Blog Card Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {Array} [items=[]] - items prop.
- * @param {number} [cols=2] - cols prop.
- * @param {any} limit - limit prop.
- * @example
- *
- {displayItems.map((props, idx) => (
-
- );
-};
-
-/**
- * @component PostCard
- * @category data
- * @tier composite
- * @status stable
- * @description Post Card data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents
- * @usedIn v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {any} title - title prop.
- * @param {any} content - content prop.
- * @param {any} href - href prop.
- * @param {string} [author="Unknown"] - author prop.
- * @param {any} [datePosted=null] - date Posted prop.
- * @param {any} [replyCount=null] - reply Count prop.
- * @param {string} [icon="book-open"] - icon prop.
- * @param {string} [authorIcon="user-pen"] - author Icon prop.
- * @param {string} [dateIcon="calendar"] - date Icon prop.
- * @param {string} [cta="Read More"] - cta prop.
- * @param {any} [img=null] - img prop.
- * @example
- *
-
-
- )}
- {datePosted && (
-
-
-
- )}
- {/* {replyCount && (
-
-
-
- )} */}
-
- {
- const el = e.target;
- const atBottom =
- el.scrollHeight - el.scrollTop <= el.clientHeight + 10;
- const hint = el.nextSibling;
- if (hint) hint.style.display = atBottom ? "none" : "block";
- }}
- dangerouslySetInnerHTML={{ __html: content }}
- />
- {showScrollHint && (
-
- {displayItems.map((props, idx) => (
-
-
- );
-};
-
-/**
- * @component CardInCardLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Card In Card Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn none
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource none
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {Array} [items=[]] - items prop.
- * @param {any} limit - limit prop.
- * @example
- *
-
- );
-};
-
-/**
- * @component ForumLatestLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Forum Latest Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn v2/community/livepeer-community/livepeer-latest-topics.mdx, v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/forum
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {Array} [items=[]] - items prop.
- * @param {any} limit - limit prop.
- * @example
- * 
-
-
-
-
- );
- }
-
- // Convert markdown links [text](url) to HTML tags
- const parseContent = (content) => {
- // First convert markdown links to HTML with icon placeholder
- const withLinks = content.replace(
- /\[([^\]]+)\]\(([^)]+)\)/g,
- '$1 ↗'
- );
- return withLinks;
- };
-
- return (
-
-
- );
- }
-
- return (
- //
)
}
diff --git a/style.css b/style.css
index 66c654507..352669405 100644
--- a/style.css
+++ b/style.css
@@ -242,9 +242,9 @@ a.nav-tabs-item[href*='/internal/'] {
/* Push Resource HUB to the right and style as outlined button */
a.nav-tabs-item[href$='/resources/redirect'],
-a.nav-tabs-item[href$='/resources/resources-portal'],
+a.nav-tabs-item[href$='/resources/portal'],
a.nav-tabs-item[href$='/07_resources/redirect'],
-a.nav-tabs-item[href$='/07_resources/resources-portal'] {
+a.nav-tabs-item[href$='/07_resources/portal'] {
margin-left: auto;
background-color: transparent;
border: 1px solid var(--accent) !important;
@@ -263,9 +263,9 @@ a.nav-tabs-item[href$='/07_resources/resources-portal'] {
/* Shrink & color the icon */
a.nav-tabs-item[href$='/resources/redirect'] svg,
-a.nav-tabs-item[href$='/resources/resources-portal'] svg,
+a.nav-tabs-item[href$='/resources/portal'] svg,
a.nav-tabs-item[href$='/07_resources/redirect'] svg,
-a.nav-tabs-item[href$='/07_resources/resources-portal'] svg,
+a.nav-tabs-item[href$='/07_resources/portal'] svg,
a.nav-tabs-item[href$='/07_resources/resources_hub'] svg {
height: 0.75rem;
width: 0.75rem;
@@ -274,9 +274,9 @@ a.nav-tabs-item[href$='/07_resources/resources_hub'] svg {
/* Hide the underline on the button */
a.nav-tabs-item[href$='/resources/redirect'] > div:last-child,
-a.nav-tabs-item[href$='/resources/resources-portal'] > div:last-child,
+a.nav-tabs-item[href$='/resources/portal'] > div:last-child,
a.nav-tabs-item[href$='/07_resources/redirect'] > div:last-child,
-a.nav-tabs-item[href$='/07_resources/resources-portal'] > div:last-child,
+a.nav-tabs-item[href$='/07_resources/portal'] > div:last-child,
a.nav-tabs-item[href$='/07_resources/resources_hub'] > div:last-child {
display: none;
}
diff --git a/tools/config/scoped-navigation/docs-gate-orch.json b/tools/config/scoped-navigation/docs-gate-orch.json
index 9c456c3b4..3dccc92f4 100644
--- a/tools/config/scoped-navigation/docs-gate-orch.json
+++ b/tools/config/scoped-navigation/docs-gate-orch.json
@@ -2123,6 +2123,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -2234,6 +2241,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -2501,6 +2515,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -2639,6 +2660,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -2915,6 +2943,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -3067,6 +3102,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -3134,6 +3176,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -3199,6 +3248,13 @@
}
]
},
+ {
+ "anchor": "Resource HUB",
+ "icon": "books",
+ "pages": [
+ "v2/resources/redirect"
+ ]
+ },
{
"anchor": " ",
"icon": "horizontal-rule",
@@ -3221,7 +3277,7 @@
"group": "Resources",
"icon": "books",
"pages": [
- "v2/resources/documentation-guide/documentation-overview",
+ "v2/resources/redirect",
"v2/resources/resources-portal",
"docs-guide/contributing/contributing"
]
@@ -3336,7 +3392,7 @@
"anchor": "Help Center",
"icon": "comments-question-check",
"pages": [
- "v2/resources/help-center"
+ "v2/resources/redirect"
]
},
{
@@ -3556,6 +3612,14 @@
}
},
"redirects": [
+ {
+ "source": "/v2/resources/redirect",
+ "destination": "/v2/resources/resources-portal"
+ },
+ {
+ "source": "/v2/pages/08_help/redirect",
+ "destination": "/v2/pages/08_help/README"
+ },
{
"source": "/v2/orchestrators/setting-up-an-orchestrator/overview",
"destination": "/v2/orchestrators/setup/guide"
diff --git a/tools/config/scoped-navigation/docs-gate-work.json b/tools/config/scoped-navigation/docs-gate-work.json
index 6ed9c8882..e34039d25 100644
--- a/tools/config/scoped-navigation/docs-gate-work.json
+++ b/tools/config/scoped-navigation/docs-gate-work.json
@@ -575,6 +575,14 @@
}
},
"redirects": [
+ {
+ "source": "/v2/resources/redirect",
+ "destination": "/v2/resources/resources-portal"
+ },
+ {
+ "source": "/v2/pages/08_help/redirect",
+ "destination": "/v2/pages/08_help/README"
+ },
{
"source": "/v2/orchestrators/setting-up-an-orchestrator/overview",
"destination": "/v2/orchestrators/setup/overview"
diff --git a/tools/config/scoped-navigation/docs-orch-work.json b/tools/config/scoped-navigation/docs-orch-work.json
index 14fb00b57..2d4b0c60b 100644
--- a/tools/config/scoped-navigation/docs-orch-work.json
+++ b/tools/config/scoped-navigation/docs-orch-work.json
@@ -222,6 +222,14 @@
}
},
"redirects": [
+ {
+ "source": "/v2/resources/redirect",
+ "destination": "/v2/resources/resources-portal"
+ },
+ {
+ "source": "/v2/pages/08_help/redirect",
+ "destination": "/v2/pages/08_help/README"
+ },
{
"source": "/v2/orchestrators/setting-up-an-orchestrator/overview",
"destination": "/v2/orchestrators/setup/guide"
diff --git a/tools/config/scoped-navigation/docs.json.jsx b/tools/config/scoped-navigation/docs.json.jsx
index ce2781250..e833bb710 100644
--- a/tools/config/scoped-navigation/docs.json.jsx
+++ b/tools/config/scoped-navigation/docs.json.jsx
@@ -40,6 +40,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -103,6 +108,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -355,6 +365,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -430,6 +445,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -663,6 +683,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -788,6 +813,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -850,6 +880,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -910,6 +945,11 @@ const docsJsonFr = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -929,7 +969,7 @@ const docsJsonFr = {
{
group: 'Home',
icon: 'house',
- pages: ['v2/resources/documentation-guide/documentation-overview'],
+ pages: ['v2/resources/redirect'],
},
{
group: 'Documentation Guide',
@@ -1025,7 +1065,7 @@ const docsJsonFr = {
{
anchor: 'Help Center',
icon: 'comments-question-check',
- pages: ['v2/resources/help-center'],
+ pages: ['v2/resources/redirect'],
},
{
anchor: ' ',
@@ -1137,6 +1177,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1200,6 +1245,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1462,6 +1512,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1537,6 +1592,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1777,6 +1837,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1902,6 +1967,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -1964,6 +2034,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2024,6 +2099,11 @@ const docsJsonCn = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2043,7 +2123,7 @@ const docsJsonCn = {
{
group: 'Home',
icon: 'house',
- pages: ['v2/resources/documentation-guide/documentation-overview'],
+ pages: ['v2/resources/redirect'],
},
{
group: 'Documentation Guide',
@@ -2139,7 +2219,7 @@ const docsJsonCn = {
{
anchor: 'Help Center',
icon: 'comments-question-check',
- pages: ['v2/resources/help-center'],
+ pages: ['v2/resources/redirect'],
},
{
anchor: ' ',
@@ -2257,6 +2337,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2320,6 +2405,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2394,6 +2484,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2626,6 +2721,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2751,6 +2851,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2813,6 +2918,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2873,6 +2983,11 @@ const docsJsonEs = {
},
],
},
+ {
+ anchor: 'Resource HUB',
+ icon: 'books',
+ pages: ['v2/resources/redirect'],
+ },
{
anchor: ' ',
icon: 'horizontal-rule',
@@ -2892,7 +3007,7 @@ const docsJsonEs = {
{
group: 'Home',
icon: 'house',
- pages: ['v2/resources/documentation-guide/documentation-overview'],
+ pages: ['v2/resources/redirect'],
},
{
group: 'Documentation Guide',
@@ -2988,7 +3103,7 @@ const docsJsonEs = {
{
anchor: 'Help Center',
icon: 'comments-question-check',
- pages: ['v2/resources/help-center'],
+ pages: ['v2/resources/redirect'],
},
{
anchor: ' ',
diff --git a/tools/lib/copy-governance/banned-phrases.txt b/tools/lib/copy-governance/banned-phrases.txt
index 0f4dfd635..1d9158f6a 100644
--- a/tools/lib/copy-governance/banned-phrases.txt
+++ b/tools/lib/copy-governance/banned-phrases.txt
@@ -1,14 +1,10 @@
This section covers
-This page covers
-This page explains
-This page walks you through
The reason is straightforward
Understanding X is essential
It is important to note
As mentioned above
among other factors
and so on
-etc.
low but not zero
not just
rather than
diff --git a/tools/lib/docs/mdx-safe-markdown.js b/tools/lib/docs/mdx-safe-markdown.js
index 8f0c33473..c35b6079b 100644
--- a/tools/lib/docs/mdx-safe-markdown.js
+++ b/tools/lib/docs/mdx-safe-markdown.js
@@ -17,6 +17,7 @@ const { unified } = require('unified');
const { isExcludedV2ExperimentalPath } = require('./docs-publishability');
const { isGeneratedDocsPageContent } = require('./docs-page-scope');
const { repairCodeBlockMetadata } = require('./docs-authoring-rules');
+const { filterPathsByMintIgnore } = require('../../../operations/tests/utils/mintignore');
function loadPlugin(name) {
const plugin = require(name);
@@ -139,7 +140,7 @@ function shouldExcludeMarkdownPath(repoPath) {
if (!relPath) return true;
if (!isMarkdownFile(relPath)) return true;
- return (
+ if (
relPath.startsWith('.git/') ||
relPath.startsWith('node_modules/') ||
relPath.includes('/.git/') ||
@@ -152,7 +153,22 @@ function shouldExcludeMarkdownPath(repoPath) {
relPath.includes('/.next/') ||
relPath.endsWith('.bak') ||
relPath.endsWith('.disabled')
- );
+ ) {
+ return true;
+ }
+
+ // Respect .mintignore / non-published exclusions
+ if (relPath.startsWith('workspace/')) return true;
+ if (relPath.startsWith('v2/') && isExcludedV2ExperimentalPath(relPath)) return true;
+
+ const segments = relPath.split('/');
+ for (const segment of segments) {
+ if (segment === '_workspace' || segment === 'x-archived' || segment === '_archive') {
+ return true;
+ }
+ }
+
+ return false;
}
function isEligibleRepoMarkdownPath(repoPath) {
@@ -182,8 +198,9 @@ function walkMarkdownFiles(dirPath, repoRoot, out = []) {
if (!fs.existsSync(dirPath)) return out;
const entries = fs.readdirSync(dirPath, { withFileTypes: true });
+ const SKIP_DIRS = new Set(['.git', 'node_modules', '.venv', '__pycache__', '.next', '_workspace', 'x-archived', '_archive', 'workspace']);
for (const entry of entries) {
- if (entry.name === '.git' || entry.name === 'node_modules' || entry.name === '.venv' || entry.name === '__pycache__' || entry.name === '.next') {
+ if (SKIP_DIRS.has(entry.name)) {
continue;
}
@@ -204,7 +221,8 @@ function walkMarkdownFiles(dirPath, repoRoot, out = []) {
function getAllRepoMarkdownFiles(rootDir = REPO_ROOT) {
const repoRoot = getRepoRoot(rootDir);
- return walkMarkdownFiles(repoRoot, repoRoot).sort((left, right) =>
+ const files = walkMarkdownFiles(repoRoot, repoRoot);
+ return filterPathsByMintIgnore(files, { rootDir: repoRoot }).sort((left, right) =>
normalizeRepoPath(path.relative(repoRoot, left)).localeCompare(normalizeRepoPath(path.relative(repoRoot, right)))
);
}
diff --git a/tools/package-lock.json b/tools/package-lock.json
index 60e1fe61b..02434c1ce 100644
--- a/tools/package-lock.json
+++ b/tools/package-lock.json
@@ -29,6 +29,10 @@
"remark-parse": "^11.0.0",
"remark-stringify": "^11.0.0",
"unified": "^11.0.5"
+ },
+ "devDependencies": {
+ "flatted": "^3.4.2",
+ "picomatch": "^4.0.4"
}
},
"node_modules/@anthropic-ai/sdk": {
@@ -5916,6 +5920,13 @@
"pend": "~1.2.0"
}
},
+ "node_modules/flatted": {
+ "version": "3.4.2",
+ "resolved": "https://registry.npmjs.org/flatted/-/flatted-3.4.2.tgz",
+ "integrity": "sha512-PjDse7RzhcPkIJwy5t7KPWQSZ9cAbzQXcafsetQoD7sOJRQlGikNbx7yZp2OotDnJyrDcbyRq3Ttb18iYOqkxA==",
+ "dev": true,
+ "license": "ISC"
+ },
"node_modules/follow-redirects": {
"version": "1.15.11",
"resolved": "https://registry.npmjs.org/follow-redirects/-/follow-redirects-1.15.11.tgz",
@@ -10361,9 +10372,9 @@
"license": "ISC"
},
"node_modules/picomatch": {
- "version": "4.0.3",
- "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.3.tgz",
- "integrity": "sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==",
+ "version": "4.0.4",
+ "resolved": "https://registry.npmjs.org/picomatch/-/picomatch-4.0.4.tgz",
+ "integrity": "sha512-QP88BAKvMam/3NxH6vj2o21R6MjxZUAd6nlwAS/pnGvN9IVLocLHxGYIzFhg6fUQ+5th6P4dv4eW9jX3DSIj7A==",
"license": "MIT",
"engines": {
"node": ">=12"
diff --git a/tools/package.json b/tools/package.json
index c199fe30a..a77e69f00 100644
--- a/tools/package.json
+++ b/tools/package.json
@@ -84,5 +84,9 @@
"i18n:docs-json": "node ../operations/scripts/automations/content/language-translation/generate-localized-docs-json.js",
"i18n:validate": "node ../operations/scripts/automations/content/language-translation/validate-generated.js",
"test:i18n": "node --test ../operations/scripts/automations/content/language-translation/test/*.test.js"
+ },
+ "devDependencies": {
+ "flatted": "^3.4.2",
+ "picomatch": "^4.0.4"
}
}
diff --git a/v1/orchestrators/guides/install-go-livepeer.mdx b/v1/orchestrators/guides/install-go-livepeer.mdx
index e6e189498..fa5e64aeb 100644
--- a/v1/orchestrators/guides/install-go-livepeer.mdx
+++ b/v1/orchestrators/guides/install-go-livepeer.mdx
@@ -160,10 +160,16 @@ docker pull livepeer/go-livepeer:master
Building `livepeer` requires some system dependencies.
-#### Linux (Ubuntu Server 20.04 or newer)
+#### Linux (Ubuntu: 16.04 or 18.04)
```bash
-apt-get -y install build-essential pkg-config nasm libx264-dev
+apt-get update && apt-get -y install build-essential pkg-config autoconf git curl yasm
+```
+
+#### Linux (Ubuntu: 20.04 or newer)
+
+```bash
+apt-get -y install protobuf-compiler-grpc golang-goprotobuf-dev yasm pkg-config
```
#### Linux GPU support
diff --git a/v2/_workspace/archive/language-pages/es/cn/docs-guide/catalog/components-catalog.mdx b/v2/_workspace/archive/language-pages/es/cn/docs-guide/catalog/components-catalog.mdx
index a4010d392..c0997ef3e 100644
--- a/v2/_workspace/archive/language-pages/es/cn/docs-guide/catalog/components-catalog.mdx
+++ b/v2/_workspace/archive/language-pages/es/cn/docs-guide/catalog/components-catalog.mdx
@@ -18,14 +18,6 @@ Run when: Components are added, removed, renamed, or their exported signatures c
Run command: node tools/scripts/generate-docs-guide-components-index.js --write
*/}
-{/*
-generated-file-banner: generated-file-banner:v1
-Generation Script: tools/scripts/generate-docs-guide-components-index.js
-Purpose: Aggregate inventory of repository components from snippets/components for docs-guide maintenance.
-Run when: Components are added, removed, renamed, or their exported signatures change under `snippets/components`.
-Run command: node tools/scripts/generate-docs-guide-components-index.js --write
-*/}
-
- Scroll for more ↓
-
- )}
-
- );
-};
-
-/**
- * @component CardColumnsPostLayout
- * @category data
- * @tier composite
- * @status stable
- * @description Card Columns Post Layout data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, DiscordAnnouncements, LumaEvents, PostCard
- * @usedIn v2/community/livepeer-community/trending-topics.mdx, v2/home/trending.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/blog
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {number} [cols=2] - cols prop.
- * @param {Array} [items=[]] - items prop.
- * @param {any} limit - limit prop.
- * @example
- *
-
-
- - No announcements at this time. -
-
- {displayItems.map((announcement, index) => (
-
- );
-};
-
-/**
- * @component LumaEvents
- * @category data
- * @tier composite
- * @status stable
- * @description Luma Events data-driven component for rendering automated or API-backed documentation content.
- * @contentAffinity overview, reference
- * @owner docs
- * @dependencies BlogCard, CardBlogDataLayout, CardColumnsPostLayout, DiscordAnnouncements, PostCard
- * @usedIn v2/community/livepeer-connect/events-and-community-streams.mdx
- * @breakingChangeRisk low
- * @decision KEEP
- * @dataSource automationData/luma
- * @duplicates none
- * @lastMeaningfulChange 2026-03-10
- * @param {any} data - data prop.
- * @param {any} limit - limit prop.
- * @param {string} [type="upcoming"] - type prop.
- * @example
- *
-
- ))}
-
-
-
- {index < displayItems.length - 1 && (
-
-
-
- )}
- -
- No {type} events at this time. -
-
-
- {displayEvents.map((event, index) => (
-
-
- ))}
-
- );
-};
diff --git a/snippets/components/layout/examples/card-carousel-examples.mdx b/snippets/components/layout/examples/card-carousel-examples.mdx
deleted file mode 100644
index 1808c1389..000000000
--- a/snippets/components/layout/examples/card-carousel-examples.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: "CardCarousel Examples"
-description: "Examples of using CardCarousel component"
----
-
-import { CardCarousel } from "/snippets/components/layout/card-carousel.jsx";
-
-## CardCarousel
-
-A simple carousel that paginates through cards with navigation controls.
-
-### Basic Usage (3 visible)
-
-
- First card content
- Second card content
- Third card content
- Fourth card content
- Fifth card content
- Sixth card content
-
-
-### Two Cards Visible
-
-
-
- Begin your journey with Livepeer
-
-
- Explore the complete API
-
-
- Step-by-step guides
-
-
- Join the discussion
-
-
-
-### Single Card View
-
-
-
- Detailed description of the first feature with all the information you need.
-
-
- Detailed description of the second feature with comprehensive details.
-
-
- Detailed description of the third feature explained thoroughly.
-
-
-
-### Without Dots
-
-
- Content A
- Content B
- Content C
- Content D
-
-
-### Custom Gap
-
-
- Content
- Content
- Content
- Content
-
-
-### Feature Showcase
-
-
-
- Stream live video with low latency to audiences worldwide.
-
-
- Automatically transcode video into multiple formats and resolutions.
-
-
- Apply AI models to your video streams in real-time.
-
-
- Store and retrieve video content with decentralized infrastructure.
-
-
diff --git a/snippets/components/layout/examples/showcase-cards-examples.mdx b/snippets/components/layout/examples/showcase-cards-examples.mdx
deleted file mode 100644
index 371c93e72..000000000
--- a/snippets/components/layout/examples/showcase-cards-examples.mdx
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: "ShowcaseCards Examples"
-description: "Examples of using ShowcaseCards component for project galleries"
----
-
-import { ShowcaseCards } from "/snippets/components/layout/showcase-cards.jsx";
-
-## ShowcaseCards
-
-A filterable, paginated gallery of project cards with search, category filters, and product filters.
-
-### Basic Usage
-
-
-
- Filter projects by title, subtitle, or description
-
-
- Filter by category (Apps, Social Media, etc.)
-
-
- Filter by Livepeer product integration
-
-
- Navigate through large collections
-
-
-
----
-
-## Category Tags
-
-Available category colors:
-
-| Category | Badge Color |
-|----------|-------------|
-| Apps | Blue |
-| Social Media | Purple |
-| Video Streaming | Green |
-| Community | Yellow |
-| Marketplaces | Orange |
-| Developer Tools | Red |
-| AI-Powered Apps | Cyan |
-
----
-
-## Product Tags
-
-Projects can be tagged with Livepeer products:
-
-- Livepeer Studio
-- Livepeer Network
-- Daydream
-- Stream.place
-- Frameworks
-
-Each product tag includes a link to its documentation.
diff --git a/snippets/components/page-structure/examples/frame-mode-examples.mdx b/snippets/components/page-structure/examples/frame-mode-examples.mdx
deleted file mode 100644
index 3f5af113f..000000000
--- a/snippets/components/page-structure/examples/frame-mode-examples.mdx
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: "Frame Mode Components Examples"
-description: "Examples of using PageHeader, H1-H6, P, and Divider components"
-mode: wide
----
-
-import { ThemeData } from "/snippets/styles/themeStyles.jsx";
-import { PageHeader, H1, H2, H3, H4, H5, H6, P, Divider } from "/snippets/components/page-structure/frameMode.jsx";
-
-
-These components are designed for Mintlify's frame mode pages where default markdown headings may not render correctly. They require importing `ThemeData`.
-
-
-## Headings (H1-H6)
-
-Custom heading components with optional icons and alignment.
-
-### H1 - Main Heading
-
-
-Portal components are designed for frame mode pages and require importing `ThemeData` and `CustomDivider` in the MDX file.
-
-
-## Portal Components Overview
-
-These components create consistent portal page layouts with hero sections, content containers, and branding elements.
-
----
-
-## LogoHeroContainer
-
-Displays a centered logo image with optional suffix text.
-
-### Basic Logo
-
-
- Docs
-
-
----
-
-## PortalHeroContent
-
-Creates a complete hero section with title, subtitle, description, and optional elements.
-
-### Basic Usage
-
-
- This guide will walk you through setting up your first Livepeer integration in under 10 minutes.
-
- }
-/>
-
----
-
-## PortalContentContainer
-
-Wraps page content with proper margins and centering.
-
-
-
- Video streaming capabilities
-
-
- AI inference support
-
-
- Global CDN distribution
-
-
-
----
-
-## HeroSectionContainer
-
-Container for hero sections with background support.
-
-
-
-
-
-
----
-
-## Combined Example
-
-A complete portal page structure:
-
-
-
- Docs
-
-
-
-
-
-
- Get started in minutes
-
-
- Step-by-step tutorials
-
-
- API reference
-
-
-
-
----
-
-## Usage Notes
-
-
-Portal components use `className` properties like `frame-mode-hero-full` and `frame-mode-container` that are defined in global CSS. These classes provide the proper full-width and centered layouts.
-
-
-### Required Imports
-
-Always include these imports when using Portal components:
-
-```jsx
-import { ThemeData } from "/snippets/styles/themeStyles.jsx";
-import { CustomDivider } from "/snippets/components/elements/spacing/Divider.jsx";
-import {
- HeroSectionContainer,
- HeroContentContainer,
- PortalHeroContent,
- PortalContentContainer,
- LogoHeroContainer,
-} from "/snippets/components/page-structure/portals.jsx";
-```
diff --git a/snippets/components/primitives/examples/social-links-examples.mdx b/snippets/components/primitives/examples/social-links-examples.mdx
deleted file mode 100644
index 70daf6c09..000000000
--- a/snippets/components/primitives/examples/social-links-examples.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: "SocialLinks Examples"
-description: "Examples of using SocialLinks component"
----
-
-import { SocialLinks } from "/snippets/components/primitives/social-links.jsx";
-
-## SocialLinks
-
-Displays a row of social media icon links for Livepeer platforms.
-
-### Basic Usage
-
-
- Join the Livepeer community on your favorite platform:
-
-
-
-### In Footer Style
-
-
)
}
@@ -569,8 +496,8 @@ export const SearchTableV2 = ({
minWidth: 0,
}}
>
- {renderSearchTableCopyText(value, { flex: 1 })}
- {href ? renderSearchTableLinkIcon(href, 'var(--accent)') : null}
+
-
-
-
-
- View Event →
-
- - {event.title} -
-
-
- {event.location && !event.location.startsWith("https://") && (
-
-
- )}
- Simple H1 Heading
- -H1 with Icon
- -Centered H1 with Icon
- -### H2 - Section Heading - -Simple H2 Heading
- -H2 with Icon
- -Centered H2
- -### H3 - Subsection Heading - -Simple H3 Heading
- -H3 with Icon
- -### H4 - Minor Heading - -Simple H4 Heading
- -H4 with Icon
- -### H5 - Small Heading - -Simple H5 Heading
- -H5 with Icon
- -### H6 - Smallest Heading - -Simple H6 Heading
- -H6 with Icon
- ---- - -## Paragraph (P) - -Custom paragraph component with optional icons. - -- This is a simple paragraph without any icon. It uses theme-aware colors. -
- -- This paragraph has an info icon to draw attention. -
- -- A centered paragraph with a lightbulb icon for tips. -
- ---- - -## Divider - -Horizontal divider line with theme-aware styling. - -### Basic Divider - -Video Infrastructure
- -- Livepeer provides decentralized video infrastructure for developers and creators. -
- -Getting Started
- -- Follow our quickstart guide to begin building with Livepeer in minutes. -
- -API Reference
- -- Explore our comprehensive API documentation for all available endpoints. -
- ---- - -## Icon Alignment Options - -### Left Aligned (default) - -Left Aligned Heading
- -### Center Aligned - -Center Aligned Heading
- -### Right Aligned - -Right Aligned Heading
diff --git a/snippets/components/page-structure/examples/portals-examples.mdx b/snippets/components/page-structure/examples/portals-examples.mdx deleted file mode 100644 index 6ca4ec205..000000000 --- a/snippets/components/page-structure/examples/portals-examples.mdx +++ /dev/null @@ -1,174 +0,0 @@ ---- -title: "Portal Components Examples" -description: "Examples of using Portal page layout components" -mode: wide ---- - -import { ThemeData } from "/snippets/styles/themeStyles.jsx"; -import { CustomDivider } from "/snippets/components/elements/spacing/Divider.jsx"; -import { - HeroSectionContainer, - HeroContentContainer, - PortalHeroContent, - PortalContentContainer, - LogoHeroContainer, - HeroOverviewContent, -} from "/snippets/components/page-structure/portals.jsx"; - -
-
-
-### Multiple Rows with Different Sizes
-
-Follow Livepeer
-
-
diff --git a/snippets/components/wrappers/tables/SearchTable.jsx b/snippets/components/wrappers/tables/SearchTable.jsx
index bbc163616..0e8938772 100644
--- a/snippets/components/wrappers/tables/SearchTable.jsx
+++ b/snippets/components/wrappers/tables/SearchTable.jsx
@@ -28,81 +28,8 @@
* @param {object} [style={}] - Inline style overrides.
*/
'use client'
-
-const renderSearchTableCopyText = (text, style = {}) => {
- const handleCopy = () => {
- if (typeof navigator === 'undefined' || !navigator.clipboard?.writeText) {
- return
- }
- navigator.clipboard.writeText(text)
- }
-
- return (
-
-
- {text}
-
-
-
- )
-}
-
-const renderSearchTableLinkIcon = (
- href,
- color = 'var(--accent)',
- icon = 'arrow-up-right-from-square',
- size = 12
-) => {
- return (
-
- **Purpose**: Aggregate inventory of repository components from snippets/components for docs-guide maintenance.
@@ -927,68 +919,41 @@ import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx"; ```jsx lines Example import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx"; -
- **Defaults**: No explicit defaults detected. +
+ **Defaults**: `align="left"`, `header=false`, `style={}`
- **Defaults**: No explicit defaults detected. - -
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Defaults**: `header=false`, `hover=false`, `style={}`
- **Defaults**: None - -
- **Defaults**: `visibleCount=3`, `gap="1.5rem"`, `showDots=true` - -
- **Defaults**: `maxHeight=300`, `showHint=true`, `ariaLabel="Scrollable content"` - -
- **Defaults**: `variant="default"`, `padding="1rem"`, `borderRadius="8px"`, `style={}` - -
- **Defaults**: `width="fit-content"`, `align="center"` - -
- **Defaults**: `gap="1rem"` - -
- **Defaults**: `maxWidth="800px"`, `padding="0"`, `style={}` - -
- **Defaults**: `style={}` - -
- **Defaults**: None - -
- **Defaults**: `background='var(--card-background)'` - -
- **Defaults**: None - -
- **Defaults**: `width='80%'` - -
- **Defaults**: `direction="row"`, `gap="1rem"`, `align="flex-start"`, `justify="flex-start"`, `wrap=false`, `style={}` - -
- **Defaults**: `gap="1rem"`, `style={}` - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: `stepsConfig={}` - -
- **Defaults**: `icon="arrows-spin"`, `iconSize=50`, `iconColor="var(--accent)"`, `spinDuration="10s"` - -
- **Defaults**: `TableComponent=null`, `tableTitle=null`, `headerList=[]`, `itemsList=[]`, `monospaceColumns=[]`, `searchPlaceholder='Search...'`, `searchColumns=[]`, `categoryColumn='Category'` - -
- **Defaults**: `titleSize="h3"` - -
- **Defaults**: `iconSize="24px"` - -
- **Defaults**: `tableTitle=null`, `headerList=[]`, `itemsList=[]`, `monospaceColumns=[]` - -
- **Defaults**: `variant="default"`, `style={}` - -
- **Defaults**: `align="left"`, `header=false`, `style={}` - -
- **Defaults**: `header=false`, `hover=false`, `style={}` - -
- **Defaults**: None - -
- **Defaults**: `filename=""`, `icon="terminal"`, `language=""`, `highlight=""`, `expandable=false`, `wrap=true`, `lines=true`, `codeString=""`, `placeholderValue=""` - -
- **Defaults**: `fields={}` - -
- **Defaults**: `codeString=""`, `placeholderValue=""`, `wrap=true`, `lines=true`, `preNote=null`, `postNote=null` - -
- **Defaults**: `codeString=""`, `placeholderValue=""`, `wrap=true`, `lines=true`, `preNote=""`, `postNote=""`, `output=""` - -
- **Defaults**: `maxHeight="1000px"`, `icon="github"` - -
- **Defaults**: `className=""` - -
- **Defaults**: `className=""` - -
- **Defaults**: `frame=true`, `align='right'`, `spacing=true` - -
- **Defaults**: None - -
-``` -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: `fields={}` - -
- **Defaults**: `fields={}` - -
- **Defaults**: `component="accordion"`, `fields={}` - -
- **Defaults**: `post=null`, `label="value"`, `line=true` - -
- **Defaults**: None - -
- **Defaults**: `title="Embedded post"`, `hint=""`, `height="399"` - -
- **Defaults**: None - -
- **Defaults**: `arrow=false`, `borderRadius="12px"`, `style={}` - -
- **Defaults**: `title=""`, `author=""`, `href=""`, `controls=true`, `autoPlay=false`, `loop=false`, `muted=false` - -
- **Defaults**: `title=""`, `author=""`, `hint=""` - -
- **Defaults**: `caption=""` - -
- **Defaults**: `title=""`, `maxHeight="500px"`, `minWidth="100%"`, `showControls=false` - -
- **Defaults**: `coinId="arbitrum"` - -
- **Defaults**: `author="Livepeer Team"`, `datePosted=null`, `excerpt=null`, `icon="book-open"`, `authorIcon="user-pen"`, `dateIcon="calendar"`, `cta="Read More"`, `img=null` - -
- **Defaults**: `items=[]` - -
- **Defaults**: `cols=2`, `items=[]` - -
- **Defaults**: `items=[]` - -
- **Defaults**: `items=[]`, `cols=2` - -
- **Defaults**: `items=[]` - -
- **Defaults**: `items=[]` - -
- **Defaults**: `type="upcoming"` - -
- **Defaults**: `author="Unknown"`, `datePosted=null`, `replyCount=null`, `icon="book-open"`, `authorIcon="user-pen"`, `dateIcon="calendar"`, `cta="Read More"`, `img=null` - -
- **Defaults**: None - -
- **Defaults**: `height='700px'`, `width='100%'` - -
- **Defaults**: No explicit defaults detected. - -
- **Defaults**: `items=[]`, `limit=null`, `pageSize=10` - -
- **Defaults**: `items=[]`, `cols=2` - -
- **Defaults**: `density=1.1` - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: `minHeight="fit-content"` - -
- **Defaults**: `src="/snippets/assets/logos/Livepeer-Logo-Full-Theme.svg"`, `alt="Livepeer Logo"`, `width="100%"`, `margin="1rem auto 0 auto"`, `imgHeight="20px"`, `imgWidth="auto"`, `objectFit="contain"` - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: `zIndex=true`, `subtitle="Build - Explore - Create"`, `subtitleIcon="/snippets/assets/logos/Livepeer-Logo-Symbol-Green-Theme.svg"`, `divider=true`, `callout=null` - -
- **Defaults**: None - -
- **Defaults**: None - -
- **Defaults**: `margin="1.5rem 0"`, `opacity=0.2` - -
- **Defaults**: `iconSize=32`, `align="left"`, `gap="0.75rem"` - -
"}
- iconSize={32}
- iconColor={""}
- align={"left"}
- gap={"0.75rem"}
-/>
-```
-
- **Defaults**: `iconSize=28`, `align="left"`, `gap="0.75rem"` - -
"}
- iconSize={28}
- iconColor={""}
- align={"left"}
- gap={"0.75rem"}
-/>
-```
-
- **Defaults**: `iconSize=24`, `align="left"`, `gap="0.5rem"` - -
"}
- iconSize={24}
- iconColor={""}
- align={"left"}
- gap={"0.5rem"}
-/>
-```
-
- **Defaults**: `iconSize=20`, `align="left"`, `gap="0.5rem"` - -
"}
- iconSize={20}
- iconColor={""}
- align={"left"}
- gap={"0.5rem"}
-/>
-```
-
- **Defaults**: `iconSize=18`, `align="left"`, `gap="0.5rem"` - -
"}
- iconSize={18}
- iconColor={""}
- align={"left"}
- gap={"0.5rem"}
-/>
-```
-
- **Defaults**: `iconSize=16`, `align="left"`, `gap="0.5rem"` - -
"}
- iconSize={16}
- iconColor={""}
- align={"left"}
- gap={"0.5rem"}
-/>
-```
-
- **Defaults**: `iconSize=16`, `align="left"`, `gap="0.5rem"` - -
"}
- iconSize={16}
- iconColor={"
- **Defaults**: None - -
**Purpose**: Aggregate inventory of repository components from snippets/components for docs-guide maintenance.
@@ -927,68 +919,41 @@ import { DynamicTable } from "/snippets/components/wrappers/tables/Table.jsx"; ```jsx lines Example import { StyledTable } from "/snippets/components/wrappers/tables/Tables.jsx"; -
- **Defaults**: No explicit defaults detected. +
+ **Defaults**: `align="left"`, `header=false`, `style={}`
- **Defaults**: No explicit defaults detected. - -
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Defaults**: `header=false`, `hover=false`, `style={}`
- **Defaults**: No explicit defaults detected. +
+ **Defaults**: `align="left"`, `header=false`, `style={}`
- **Defaults**: No explicit defaults detected. - -
- **Defaults**: `size=20`, `gap="0.75rem"`, `justify="center"` - -
- **Defaults**: `size="1rem"`, `direction="vertical"` +
+ **Defaults**: `header=false`, `hover=false`, `style={}`
- -{/* ============================================================ - SECTION 1 - PROGRAMME OVERVIEW - ============================================================ */} - -
- -{/* ============================================================ - SECTION 2 - SEVERITY AND REWARDS - ============================================================ */} - -
- -### Focus Areas - -The programme focuses on preventing: - -- Direct theft of user funds (at-rest or in-motion, excluding unclaimed yield) -- Unexpected calls to privileged functions (for example, functions that should only be callable by the Governor contract) -- Any condition that results in permanent freezing of user funds - -
- -{/* ============================================================ - SECTION 3 - WHAT'S IN SCOPE - ============================================================ */} - -
- -{/* ============================================================ - SECTION 4 - HOW TO SUBMIT - ============================================================ */} - -
- -
- -{/* ============================================================ - SECTION 5 - RECENT ACTIVITY - ============================================================ */} - -
- -{/* ============================================================ - SECTION 6 - RELATED - ============================================================ */} - -
- -{/* ============================================================ - SECTION 1 - GRANT TYPES - ============================================================ */} - -
- -
- -{/* ============================================================ - SECTION 2 - ACCELERATOR PROGRAMME - ============================================================ */} - -
- -Selected teams receive: - -- Grant funding of up to $20,000 -- Infrastructure credits for AI inference and transcoding -- Expert technical mentorship from the Livepeer engineering team -- Early access to new AI video infrastructure and pipelines -- Co-marketing and partnership activation opportunities -- Investor networking and showcase opportunities - -The first cohort (August to October 2024) included eight startups: Flipguard, Katana, Newcoin, Operator, Origin Stories, Refraction, Supermodel, and StreamEth. Teams focused on incorporating generative AI features including text-to-image, image-to-image, image-to-video, upscaling, and speech-to-text into their applications, using existing Livepeer pipelines or building and deploying their own. - -A parallel programme run in partnership with Encode Club offers an eight-week accelerator for past Encode programme participants and others who wish to join, with weekly workshops, one-on-one sessions, and support for technical development, design, and fundraising. - -
- -{/* ============================================================ - SECTION 3 - COMFYUI HACKER PROGRAMME - ============================================================ */} - -
- -{/* ============================================================ - SECTION 4 - BOOTCAMP - ============================================================ */} - -
- -{/* ============================================================ - SECTION 5 - HACKATHONS - ============================================================ */} - -
- -{/* ============================================================ - SECTION 6 - APPLYING - ============================================================ */} - -
- -
- -{/* ============================================================ - SECTION 7 - RELATED - ============================================================ */} - -
- Data is sourced from the canonical
- Last verified: {lastVerifiedDate} -
Contract Registry"] + ServiceRegistry["ServiceRegistry
URI Mapping"] end - subgraph "Time" - RoundsManager["RoundsManager\nProtocol Rounds"] + subgraph "Economic Layer" + LPT["LivepeerToken
ERC20 Token"] + BondingManager["BondingManager
Staking & Rewards"] + TicketBroker["TicketBroker
Micropayments"] + Minter["Minter
Token Inflation"] end - subgraph "Governance" - BondingVotes["BondingVotes\nStake Checkpointing"] - Governor["Governor\nUpgrade Executor"] - LivepeerGovernor["LivepeerGovernor\nOn-chain Voting"] - Treasury["Treasury\nProtocol Treasury"] + subgraph "Time & Governance" + RoundsManager["RoundsManager
Protocol Rounds"] + Governor["LivepeerGovernor
Governance"] end subgraph "Participants" - Gateway["Gateway Node"] + Broadcaster["Broadcaster Node"] Orchestrator["Orchestrator Node"] - Delegator["LPT Holder"] + Delegator["Token Holder"] end Controller -.->|"Address Lookup"| LPT @@ -175,39 +91,33 @@ graph TB Controller -.->|"Address Lookup"| RoundsManager Controller -.->|"Address Lookup"| Minter Controller -.->|"Address Lookup"| ServiceRegistry - Controller -.->|"Address Lookup"| BondingVotes - Controller -.->|"Address Lookup"| LivepeerGovernor - Controller -.->|"Address Lookup"| Treasury + Controller -.->|"Address Lookup"| Governor - Delegator -->|"approve() LPT"| LPT - Delegator -->|"bond(amount, orch)"| BondingManager - Delegator -->|"castVote()"| LivepeerGovernor - BondingManager -->|"transferFrom()"| LPT - BondingManager -->|"checkpointBondingState()"| BondingVotes + Delegator -->|"Approve() LPT"| LPT + Delegator -->|"Bond(amount, orchestrator)"| BondingManager + BondingManager -->|"TransferFrom()"| LPT - Orchestrator -->|"transcoder(rewardCut, feeShare)"| BondingManager - Orchestrator -->|"setServiceURI(url)"| ServiceRegistry - Orchestrator -->|"reward()"| BondingManager - BondingManager -->|"createReward()"| Minter - Minter -->|"mint() new LPT"| LPT - Minter -->|"trustedTransferTokens()"| Treasury + Orchestrator -->|"Transcoder(cuts)"| BondingManager + Orchestrator -->|"SetServiceURI(url)"| ServiceRegistry + Orchestrator -->|"Reward()"| BondingManager + BondingManager -->|"CreateReward()"| Minter + Minter -->|"Mint() new LPT"| LPT - Gateway -->|"fundDepositAndReserve()"| TicketBroker - Orchestrator -->|"redeemWinningTicket()"| TicketBroker - TicketBroker -->|"winningTicketTransfer()"| LPT + Broadcaster -->|"Approve() LPT"| LPT + Broadcaster -->|"FundDepositAndReserve()"| TicketBroker + TicketBroker -->|"TransferFrom()"| LPT - RoundsManager -->|"currentRound()"| BondingManager - RoundsManager -->|"blockHashForRound()"| TicketBroker + Orchestrator -->|"RedeemWinningTicket()"| TicketBroker + TicketBroker -->|"Transfer() to orchestrator"| LPT + TicketBroker -->|"Update claimedReserve"| BondingManager - BondingVotes -->|"getPastVotes()"| LivepeerGovernor - LivepeerGovernor -->|"execute()"| Governor - Governor -->|"setContractInfo()"| Controller -``` + RoundsManager -->|"Round data"| BondingManager + RoundsManager -->|"Block hashes"| TicketBroker -
-- Central address registry for all protocol contracts -- Enables contract upgrades while keeping proxy addresses stable -- Provides `pause()`/`unpause()` for emergency system-wide halts -- Owner is the Governor contract – all upgrades must go through governance +On Ethereum mainnet, only the `LivepeerToken` and `BridgeMinter` contracts remain operational; all other contracts have migrated to Arbitrum One. This ensures the token has the higher security of the Ethereum mainnet while the network enjoys the higher throughput and lower fees of Arbitrum. -
There is currently no active public testnet on Arbitrum or Ethereum. -
You can run your own testnet using the full deploy script at [deploy/deploy_contracts.ts](https://github.com/livepeer/protocol/blob/streamflow/deploy/deploy_contracts.ts) -
It is never deployed on `mainnet` or `arbitrumMainnet`. - -
The migration is complete - no new migrations are possible - but both contracts remain registered in the Controller. -
Contract Registry"] + ServiceRegistry["ServiceRegistry
URI Mapping"] + end -Stores Merkle roots used to verify stake snapshots taken at the time of the Confluence migration. Used internally by L2Migrator to validate migration claims. No activity since deployment — its role was fulfilled during the migration window. + subgraph "Economic Layer" + LPT["LivepeerToken
ERC20 Token"] + BondingManager["BondingManager
Staking & Rewards"] + TicketBroker["TicketBroker
Micropayments"] + Minter["Minter
Token Inflation"] + end -
Protocol Rounds"] + Governor["LivepeerGovernor
Governance"] + end -**Purpose**: + subgraph "Participants" + Broadcaster["Broadcaster Node"] + Orchestrator["Orchestrator Node"] + Delegator["Token Holder"] + end -- Stores Merkle root snapshots (keyed by snapshot ID) set at migration time -- Provides `verify()` for L2Migrator to validate that a claimed stake amount was included in the original snapshot -- Read-only in practice; `setSnapshot()` is callable only by the Controller owner and has not been called since the migration + Controller -.->|"Address Lookup"| LPT + Controller -.->|"Address Lookup"| BondingManager + Controller -.->|"Address Lookup"| TicketBroker + Controller -.->|"Address Lookup"| RoundsManager + Controller -.->|"Address Lookup"| Minter + Controller -.->|"Address Lookup"| ServiceRegistry + Controller -.->|"Address Lookup"| Governor -**Key functions** (from `MerkleSnapshot.sol`): + Delegator -->|"Approve() LPT"| LPT + Delegator -->|"Bond(amount, orchestrator)"| BondingManager + BondingManager -->|"TransferFrom()"| LPT -
-
- Gateways are the core building block for those developers looking to productise applications built on top of the Livepeer protocol. - {/*
- Note: In earlier documentation, Gateways were referred to as Broadcasters
-
*/}
-
- }
- />
-
- *Mental Model*
-• Video Ingest
• AI Inference Requests
• WebRTC / HTTP"] - end - - subgraph Gateway["Gateway Layer (Livepeer Gateway)"] - B["Gateway Node
Cloud Analogy:
• API Gateway
• L7 Load Balancer
• Control Plane
Responsibilities:
• Auth & Rate Limits
• Stream Segmentation
• Job Routing
• Health Checks
• Retry & Failover"] - end - - subgraph Compute["Compute Layer (Supply Side)"] - C["Orchestrators
GPU Workers
Cloud Analogy:
• Auto-scaling GPU Fleet
• Managed Inference Pool"] - end - - subgraph Settlement["Coordination & Settlement"] - D["Ethereum + Livepeer Protocol
• Payments
• Accounting
• Slashing / Security"] - end - - A -->|Requests| B - B -->|Dispatch Jobs| C - C -->|Results / Streams| B - B -->|Responses| A - C -->|Usage & Proof| D - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style Clients fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
Video/AI Request"] - end - - subgraph Gateway["Gateway Layer"] - B["Livepeer Gateway
= L2 Sequencer
• Ingests Requests
• Segments/Preprocesses
• Selects Orchestrators
• Routes Jobs
• Returns Results"] - end - - subgraph Compute["Compute Layer"] - C["Orchestrators
GPU Workers
= L2 Execution Layer"] - end - - subgraph Settlement["Settlement Layer"] - D["Ethereum
Consensus & Payment Security"] - end - - A --> B - B --> C - C --> B - B --> A - C --> D - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style User fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Gateway fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Compute fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
• Owns delivery
• Sets constraints
• Chooses specialists
• Ensures quality"] - end - - subgraph Request["Act I - The Pitch"] - A["Incoming Request
• Live Video Stream
• AI Inference Job
• Quality & Latency Requirements"] - end - - subgraph Planning["Act II - Pre-Production"] - B["Gateway (Producer)
• Interpret the request
• Set budget & latency constraints
• Choose specialists
• Plan execution"] - end - - subgraph Crew["Act III - Production Crew"] - C["Orchestrators / GPU Workers
• Transcoding
• AI Inference
• Real-time Processing"] - end - - subgraph Delivery["Act IV - Final Cut & Release"] - D["Verified Output
• Stream / AI Result
• Quality checked
• Delivered on time"] - end - - subgraph Settlement["Credits & Accounting"] - E["Onchain Settlement
• Usage recorded
• Payments distributed
• Trust enforced"] - end - - P --> A - A --> B - B --> C - C --> B - B --> D - C --> E - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style Persona fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Request fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Planning fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Crew fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Delivery fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style Settlement fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - ``` - -
- Deploy your own Gateway on the Livepeer Protocol - no GPU required! -
-
:1935"] - HTTP["HTTP Upload
:8935"] - end - - GATEWAY["Gateway Node
LivepeerNode
-gateway mode"] - - INPUT --> GATEWAY - - subgraph MANAGER["Broadcast Session Manager"] - BSM["BroadcastSessionsManager
Manages transcoding sessions
Selects orchestrators"] - end - - GATEWAY --> BSM - - subgraph PROCESSING["Video Processing Pipeline"] - direction TB - SEG["Segment Video
Split into chunks"] - TRANS["Send to Orchestrators
with payment tickets"] - ORCH["Orchestrators
Transcode segments
Multiple renditions"] - RECEIVE["Receive Results
Transcoded segments"] - end - - BSM --> SEG --> TRANS --> ORCH --> RECEIVE - - subgraph OUTPUT["Output & Delivery"] - direction LR - HLS["HLS Manifest
.m3u8"] - RENDITIONS["Multiple Renditions
240p, 360p, 720p, 1080p"] - end - - RECEIVE --> HLS --> RENDITIONS - - subgraph PAYMENT["Payment System"] - direction TB - PM["Payment Manager
Generate tickets"] - TICKETS["Per-segment payments
Based on pixels transcoded"] - end - - TRANS --> PM --> TICKETS --> ORCH - - subgraph STORAGE["Storage (Optional)"] - OBJ["Object Store
S3/IPFS"] - end - - RENDITIONS -.-> OBJ - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef payment fill:#1a1a1a,color:#fff,stroke:#fbbf24,stroke-width:2px - class RTMP,HTTP,BSM,SEG,TRANS,ORCH,RECEIVE,HLS,RENDITIONS video - class PM,TICKETS payment - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGER fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PROCESSING fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style OUTPUT fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#fbbf24,stroke-width:1px - style STORAGE fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,stroke-dasharray: 5 5 -``` - -
:1935"] - HTTP["HTTP Upload
:8935"] - end - - GATEWAY["Gateway Node
LivepeerNode
-gateway mode"] - - INPUT --> GATEWAY - - subgraph MANAGER["Broadcast Session Manager"] - BSM["BroadcastSessionsManager
Manages transcoding sessions
Selects orchestrators"] - end - - GATEWAY --> BSM - - subgraph PROCESSING["Video Processing Pipeline"] - direction TB - SEG["Segment Video
Split into chunks"] - TRANS["Send to Orchestrators
with payment tickets"] - ORCH["Orchestrators
Transcode segments
Multiple renditions"] - RECEIVE["Receive Results
Transcoded segments"] - end - - BSM --> SEG --> TRANS --> ORCH --> RECEIVE - - subgraph OUTPUT["Output & Delivery"] - direction LR - HLS["HLS Manifest
.m3u8"] - RENDITIONS["Multiple Renditions
240p, 360p, 720p, 1080p"] - end - - RECEIVE --> HLS --> RENDITIONS - - subgraph PAYMENT["Payment System"] - direction TB - PM["Payment Manager
Generate tickets"] - TICKETS["Per-segment payments
Based on pixels transcoded"] - end - - TRANS --> PM --> TICKETS --> ORCH - - subgraph STORAGE["Storage (Optional)"] - OBJ["Object Store
S3/IPFS"] - end - - RENDITIONS -.-> OBJ - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef payment fill:#1a1a1a,color:#fff,stroke:#fbbf24,stroke-width:2px - class RTMP,HTTP,BSM,SEG,TRANS,ORCH,RECEIVE,HLS,RENDITIONS video - class PM,TICKETS payment - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGER fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PROCESSING fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style OUTPUT fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#fbbf24,stroke-width:1px - style STORAGE fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px,stroke-dasharray: 5 5 -``` - -
LivepeerNode"] - - INPUT --> GATEWAY - - subgraph MANAGERS["Session Managers"] - direction LR - BSM["BroadcastSessionsManager
Video Transcoding"] - ASM["AISessionManager
AI Processing"] - end - - GATEWAY --> BSM - GATEWAY --> ASM - - subgraph VIDEO["Video Pipeline"] - SEG["Segment Processing"] - ORCH_V["Orchestrators
Transcoding"] - HLS["HLS/DASH Output"] - end - - subgraph AI["AI Pipeline"] - PROC["AI Processing"] - ORCH_AI["Orchestrators
AI Models"] - OUT_AI["AI Output
Images/Video"] - end - - BSM --> SEG --> ORCH_V --> HLS - ASM --> PROC --> ORCH_AI --> OUT_AI - - subgraph PAYMENT["Payment"] - direction LR - PAY_SEG["Per Segment"] - PAY_PIX["Per Pixel"] - end - - ORCH_V --> PAY_SEG - ORCH_AI --> PAY_PIX - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - classDef video fill:#1a1a1a,color:#fff,stroke:#3b82f6,stroke-width:2px - classDef ai fill:#1a1a1a,color:#fff,stroke:#a855f7,stroke-width:2px - class RTMP,HTTP,BSM,SEG,ORCH_V,HLS,PAY_SEG video - class AI_REQ,ASM,PROC,ORCH_AI,OUT_AI,PAY_PIX ai - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style MANAGERS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style VIDEO fill:#0d0d0d,stroke:#3b82f6,stroke-width:1px - style AI fill:#0d0d0d,stroke:#a855f7,stroke-width:1px - style PAYMENT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px -``` - -
Daydream, ComfyUI, BYOC"] -->|Job Request| B["Gateway
Job Intake, Pricing, Capability Match"] - B -->|Route Job| C["Orchestrator
GPU Compute, AI Inference, Transcoding"] - C -->|Results| B - B -->|Response| A -``` - -
- -### Layered Architecture - -
Web, Mobile, TouchDesigner"] - end - subgraph GW[Gateway Layer] - G1[Job Intake] - G2[Capability Discovery] - G3[Pricing & Marketplace] - G4[Routing / Scheduling] - end - subgraph ORC[Orchestrator Layer] - O1[GPU Worker] - O2[AI Models / BYOC Containers] - O3[Transcoder] - end - X --> G1 - G1 --> O1 - O1 --> G1 - G1 --> X -``` - -
• Segment video
• Queue + order jobs
• AI pipeline routing
• Orchestrator selection
• Verification & receipts"] - - CAM -->|"Live stream"| GATEWAY - VID -->|"VOD upload"| GATEWAY - AIIN -->|"AI job request"| GATEWAY - - subgraph JOBS["Workflows"] - VJ["Video Transcoding Job"] - AIJ["AI Inference Job
(Daydream / ComfyStream / BYOC)"] - end - - GATEWAY --> VJ - GATEWAY --> AIJ - - subgraph ORCH["Orchestrator Network (GPU Operators)"] - O1["Orchestrator A
GPU Pool"] - O2["Orchestrator B
GPU Pool"] - O3["Orchestrator C
GPU Pool"] - end - - VJ -->|"Transcode segments"| O1 - VJ --> O2 - AIJ -->|"Run model / inference"| O1 - AIJ --> O3 - - subgraph OUTPUTS["Outputs"] - HLS["Adaptive Bitrate Video (HLS/LL-HLS)"] - AIOUT["AI Frames / Stylized Video"] - end - - O1 --> GATEWAY - O2 --> GATEWAY - O3 --> GATEWAY - - GATEWAY --> HLS - GATEWAY --> AIOUT - - ETH[("Arbitrum Blockchain
Payments • Tickets • Rewards")] - GATEWAY --> ETH - O1 --> ETH - O2 --> ETH - O3 --> ETH - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px`} - /> -
- -**TODO:** - -- Verify all content -- Add a real link for community submissions -- Not happy with contribution layout -
-
-
- ```bash lines icon="terminal" curl wrap - curl -LO https://ftp.gnu.org/gnu/wget/wget-1.21.4.tar.gz - tar -xzf wget-1.21.4.tar.gz - cd wget-1.21.4 - ./configure && make && sudo make install - ``` -
-
-## Introduction Gateways are essential infrastructure in the Livepeer network. They -provide the service coordination layer (routing & verification) that connects applications -to the decentralized GPU compute layer (DePIN). This guide explains the requirements, -setup steps, and best practices for running a Gateway node." - -## Gateway Modes - -You can run a gateway - --
• Ingest (RTMP/HTTP/WebRTC)
• Segment video
• Queue + order jobs
• AI pipeline routing
• Orchestrator selection
• Verification & receipts"] - - CAM -->|"Live stream"| GATEWAY - VID -->|"VOD upload"| GATEWAY - AIIN -->|"AI job request"| GATEWAY - - subgraph JOBS["Workflows"] - VJ["Video Transcoding Job"] - AIJ["AI Inference Job
(Daydream / ComfyStream / BYOC)"] - end - - GATEWAY --> VJ - GATEWAY --> AIJ - - subgraph ORCH["Orchestrator Network (GPU Operators)"] - O1["Orchestrator A
GPU Pool"] - O2["Orchestrator B
GPU Pool"] - O3["Orchestrator C
GPU Pool"] - end - - VJ -->|"Transcode segments"| O1 - VJ --> O2 - AIJ -->|"Run model / inference"| O1 - AIJ --> O3 - - subgraph OUTPUTS["Outputs"] - HLS["Adaptive Bitrate Video (HLS/LL-HLS)"] - AIOUT["AI Frames / Stylized Video"] - end - - O1 --> GATEWAY - O2 --> GATEWAY - O3 --> GATEWAY - - GATEWAY --> HLS - GATEWAY --> AIOUT - - ETH[("Arbitrum Blockchain
Payments • Tickets • Rewards")] - GATEWAY --> ETH - O1 --> ETH - O2 --> ETH - O3 --> ETH - - classDef default fill:#1a1a1a,color:#fff,stroke:#2d9a67,stroke-width:2px - style INPUT fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style JOBS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style ORCH fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - style OUTPUTS fill:#0d0d0d,stroke:#2d9a67,stroke-width:1px - -``` -
- -## Gateway Operator Journey - -
-
-
-
-
-
-
diff --git a/v2/home/mission-control.mdx b/v2/home/mission-control.mdx
index 1ba6183df..10217bd11 100644
--- a/v2/home/mission-control.mdx
+++ b/v2/home/mission-control.mdx
@@ -20,12 +20,13 @@ keywords:
'og:image': 'https://raw.githubusercontent.com/livepeer/docs/docs-v2-assets/snippets/assets/domain/00_HOME/Eric%20Shreck%20Gif.gif'
---
-import { PortalHeroContent, HeroImageBackgroundComponent, LogoHeroContainer, HeroContentContainer, HeroSectionContainer, PortalCardsHeader, PortalContentContainer } from '/snippets/components/scaffolding/portals/Portals.jsx';
+import { PortalHeroContent, HeroImageBackgroundComponent, LogoHeroContainer, HeroContentContainer, HeroSectionContainer, PortalCardsHeader, PortalContentContainer } from '/snippets/components/scaffolding/portals/Portals.jsx'
import { Starfield } from "/snippets/components/scaffolding/heroes/HeroGif.jsx";
-import { H1, H2, P } from '/snippets/components/scaffolding/frame-mode/FrameMode.jsx';
-import { BlinkingIcon } from '/snippets/components/elements/links/Links.jsx';
-import { LivepeerIcon } from '/snippets/components/elements/icons/Icons.jsx';
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx';
+import { H1, H2, P } from '/snippets/components/scaffolding/frame-mode/FrameMode.jsx'
+import { BlinkingIcon } from '/snippets/components/elements/links/Links.jsx'
+import { LivepeerIcon } from '/snippets/components/elements/icons/Icons.jsx'
+import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
+
diff --git a/v2/index.mdx b/v2/index.mdx
index eaa686aca..7a37e55e4 100644
--- a/v2/index.mdx
+++ b/v2/index.mdx
@@ -694,7 +694,7 @@ Run command: node operations/scripts/generators/content/catalogs/generate-pages-
## Resources
- [Help Center](resources/help-center.mdx)
- [⚠️ Resource Hub](resources/portal.mdx)
-- [⚠️ Resource Portal](resources/resources-portal.mdx)
+- [⚠️ Resource Portal](resources/portal.mdx)
### Changelog
- [Changelog](resources/changelog/changelog.mdx)
diff --git a/v2/orchestrators/resources/glossary.mdx b/v2/orchestrators/resources/glossary.mdx
index 179e882df..72feda5e2 100644
--- a/v2/orchestrators/resources/glossary.mdx
+++ b/v2/orchestrators/resources/glossary.mdx
@@ -555,7 +555,7 @@ Terms covering GPU setup, AI pipeline configuration, staking mechanics, payment
**Definition**: On-chain transaction (`Reward()`) that an active orchestrator submits once per round to mint and distribute new LPT inflation rewards.
- **Context**: Missing a reward call permanently forfeits that round's rewards. Gas cost on Arbitrum is approximately $0.01-$0.12 per call. Orchestrators typically automate reward calling via a cron job or dedicated service.
+ **Context**: Missing a reward call permanently forfeits that round's rewards. Gas cost on Arbitrum is approximately $0.01–$0.12 per call. Orchestrators typically automate reward calling via a cron job or dedicated service.
**Status**: current
diff --git a/v2/orchestrators/x-archived/unclassified/dep-quickstart-add-your-gpu-to-livepeer.mdx b/v2/orchestrators/x-archived/unclassified/dep-quickstart-add-your-gpu-to-livepeer.mdx
deleted file mode 100644
index 61ebc74d3..000000000
--- a/v2/orchestrators/x-archived/unclassified/dep-quickstart-add-your-gpu-to-livepeer.mdx
+++ /dev/null
@@ -1,125 +0,0 @@
----
-title: Configure your Orchestrator
-sidebarTitle: Add your GPU to Livepeer
-description: >-
- Configure go-livepeer after installation: Arbitrum connection, pricing, service address, and optional transcoding or
- AI config.
-audience: orchestrator
-purpose: tutorial
-keywords:
- - livepeer
- - orchestrators
- - configuration
- - pricePerUnit
- - serviceAddr
- - transcoding
- - AI
-'og:image': /snippets/assets/domain/SHARED/LivepeerDocsLogo.svg
----
-
-{/* Legacy configuration page retained for reference after the new quickstart and setup guides became canonical. */}
-
-
-
-import { CustomCodeBlock } from '/snippets/components/content/code.jsx'
-
-After [installing go-livepeer](/v2/orchestrators/setup/rs-install), configure the node so gateways can discover you and send work. This page covers core flags and optional config files.
-
-## Core configuration
-
-### Network and wallet
-
-- **-ethUrl** - Arbitrum RPC URL. See [Connect to Arbitrum](/v2/orchestrators/setup/sc-connect).
-- **-ethAcctAddr** - (Optional) ETH account address if you already have a keystore.
-- **-network** - Use `arbitrum-one-mainnet` for production.
-
-### Orchestrator identity and pricing
-
-- **-serviceAddr** - Public hostname or IP and port (e.g. `orchestrator.example.com:8935`). Prefer a hostname you control; changing it later requires an on-chain update.
-- **-pricePerUnit** - Price in wei per pixel (transcoding). Required at startup; can be updated later via CLI or on-chain.
-- **-pixelsPerUnit** - Pixels per pricing unit (default 1). Affects how price is calculated per segment.
-
-### GPU and mode
-
-- **-orchestrator** - Run in orchestrator mode.
-- **-transcoder** - Enable GPU transcoding.
-- **-nvidia** - Comma-separated NVIDIA GPU IDs (e.g. `0,1`). Omit for CPU-only.
-
-Example minimal run:
-
- \\
- -serviceAddr \\
- -pricePerUnit \\
- -nvidia 0,1`}
- language="bash"
- icon="terminal"
-/>
-
-## Optional: transcoding options
-
-You can define transcoding profiles in a JSON file and reference them. Example structure:
-
-
-
diff --git a/v2/resources/documentation-guide/contributing/contribute-to-the-docs.mdx b/v2/resources/documentation-guide/contributing/contribute-to-the-docs.mdx
index 6920c478b..6cb331b5a 100644
--- a/v2/resources/documentation-guide/contributing/contribute-to-the-docs.mdx
+++ b/v2/resources/documentation-guide/contributing/contribute-to-the-docs.mdx
@@ -587,7 +587,7 @@ v2/
├── delegators/ # Delegators tab
│ └── delegator-portal.mdx
└── resources/ # Resources tab
- ├── resources-portal.mdx
+ ├── portal.mdx
└── documentation-guide/
```
diff --git a/v2/resources/glossary-data.json b/v2/resources/glossary-data.json
index 2215ccf6a..2070535f5 100644
--- a/v2/resources/glossary-data.json
+++ b/v2/resources/glossary-data.json
@@ -1015,7 +1015,7 @@
},
{
"term": "CRF (Constant Rate Factor)",
- "definition": "Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0-51 with lower values producing higher quality.",
+ "definition": "Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0–51 with lower values producing higher quality.",
"category": "video:encoding",
"tabs": [
"solutions"
@@ -4262,7 +4262,7 @@
},
{
"term": "Segment",
- "definition": "A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2-10 seconds for HLS delivery.",
+ "definition": "A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2–10 seconds for HLS delivery.",
"category": "livepeer:protocol",
"tabs": [
"about",
@@ -4779,7 +4779,7 @@
},
{
"term": "SVD (Stable Video Diffusion)",
- "definition": "Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image.",
+ "definition": "Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image.",
"category": "ai:model",
"tabs": [
"developers"
diff --git a/v2/resources/glossary.mdx b/v2/resources/glossary.mdx
index 377567ca6..16205cc67 100644
--- a/v2/resources/glossary.mdx
+++ b/v2/resources/glossary.mdx
@@ -143,7 +143,7 @@ Complete reference of terms used across all Livepeer documentation — covering
{ Term: "Controller", Category: "livepeer:contract", Tabs: "about, resources", Definition: "The registry smart contract that manages all protocol contract addresses and coordinates protocol upgrades on Arbitrum." },
{ Term: "ControlNet", Category: "ai:model", Tabs: "orchestrators, resources", Definition: "A neural network architecture that adds spatial conditioning controls — such as edge maps, depth, or pose — to pretrained diffusion models." },
{ Term: "CORS (Cross-Origin Resource Sharing)", Category: "technical:dev", Tabs: "solutions", Definition: "HTTP mechanism that lets servers specify which origins outside their own domain are allowed to make browser requests to their resources." },
- { Term: "CRF (Constant Rate Factor)", Category: "video:encoding", Tabs: "solutions", Definition: "Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0-51 with lower values producing higher quality." },
+ { Term: "CRF (Constant Rate Factor)", Category: "video:encoding", Tabs: "solutions", Definition: "Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0–51 with lower values producing higher quality." },
{ Term: "Cryptoeconomic Primitives", Category: "web3:concept", Tabs: "about", Definition: "Fundamental building blocks that combine cryptography and economic incentives to enable secure, decentralized protocols." },
{ Term: "CUDA (Compute Unified Device Architecture)", Category: "ai:framework", Tabs: "orchestrators", Definition: "NVIDIA's parallel computing platform and programming API enabling GPUs to be used for general-purpose processing and deep learning." },
{ Term: "CPU (Central Processing Unit)", Category: "technical:hardware", Tabs: "gateways, orchestrators, developers, about", Definition: "The primary general-purpose processor in a computer; in Livepeer, CPU handles node software overhead while GPU handles intensive transcoding and AI inference workloads." },
@@ -398,7 +398,7 @@ Complete reference of terms used across all Livepeer documentation — covering
{ Term: "Scaling", Category: "operational:process", Tabs: "gateways", Definition: "Increasing gateway capacity to handle more concurrent requests, either horizontally (deploying additional gateway nodes) or vertically (adding resources to an existing node)." },
{ Term: "SDXL (Stable Diffusion XL)", Category: "ai:model", Tabs: "developers, resources", Definition: "Stable Diffusion XL — advanced text-to-image model with a 3× larger UNet and dual text encoders, generating images at 1024×1024 resolution." },
{ Term: "SDK (Software Development Kit)", Category: "technical:dev", Tabs: "solutions", Definition: "Collection of tools, libraries, and documentation enabling developers to build applications that integrate with a platform's APIs." },
- { Term: "Segment", Category: "livepeer:protocol", Tabs: "about, solutions, gateways, orchestrators, resources", Definition: "A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2-10 seconds for HLS delivery." },
+ { Term: "Segment", Category: "livepeer:protocol", Tabs: "about, solutions, gateways, orchestrators, resources", Definition: "A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2–10 seconds for HLS delivery." },
{ Term: "Segmentation", Category: "video:processing", Tabs: "solutions, developers, orchestrators", Definition: "(1) Video: the process of dividing a continuous video stream into short discrete chunks for HTTP-based delivery. (2) AI: task partitioning a digital image into regions by assigning a semantic label to every pixel." },
{ Term: "Self-Hosted", Category: "technical:deployment", Tabs: "developers, gateways", Definition: "A deployment model in which the operator runs their own infrastructure rather than relying on a managed cloud service; Livepeer gateways and AI nodes can be self-hosted on any compatible hardware." },
{ Term: "Service Margin", Category: "economic:pricing", Tabs: "gateways", Definition: "A markup that gateway operators add on top of orchestrator costs when reselling gateway access to end users." },
@@ -438,7 +438,7 @@ Complete reference of terms used across all Livepeer documentation — covering
{ Term: "Subgraph", Category: "web3:concept", Tabs: "orchestrators", Definition: "Custom open API defining how Livepeer on-chain data is indexed and queried via GraphQL, built on The Graph protocol." },
{ Term: "Supply", Category: "web3:tokenomics", Tabs: "lpt", Definition: "The total number of LPT tokens in existence at any given time, starting from a genesis supply of 10 million and growing continuously through inflationary issuance." },
{ Term: "Surge strategy", Category: "economic:treasury", Tabs: "community", Definition: "Concentrated treasury spending approach targeting high-impact growth initiatives during strategic market windows." },
- { Term: "SVD (Stable Video Diffusion)", Category: "ai:model", Tabs: "developers", Definition: "Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image." },
+ { Term: "SVD (Stable Video Diffusion)", Category: "ai:model", Tabs: "developers", Definition: "Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image." },
{ Term: "Synthetic Data", Category: "ai:application", Tabs: "home", Definition: "Artificially generated data produced by algorithms rather than real-world events, used for training AI models when real data is scarce or sensitive." },
{ Term: "TAM (Total Addressable Market)", Category: "economic:business", Tabs: "resources", Definition: "The total potential revenue opportunity available to a product or service if it captured 100% of its target market." },
{ Term: "Target Bonding Rate", Category: "web3:tokenomics", Tabs: "lpt", Definition: "The 50% participation threshold for the ratio of bonded LPT to total supply; the inflation mechanism adjusts the per-round issuance rate to push toward this target." },
@@ -511,7 +511,7 @@ Complete reference of terms used across all Livepeer documentation — covering
- **Definition**: Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0-51 with lower values producing higher quality.
+ **Definition**: Encoding quality control parameter that targets consistent perceptual quality by adjusting quantization per frame; scale runs 0–51 with lower values producing higher quality.
**Tags**: `video:encoding`
@@ -5125,7 +5125,7 @@ Complete reference of terms used across all Livepeer documentation — covering
**Tabs**: about, developers, orchestrators, community, lpt
- **Context**: Reward calls are an orchestrator's operational responsibility each round; missing reward calls means forfeiting inflationary LPT for that round, which also harms delegators who rely on that income. Gas cost on Arbitrum is approximately $0.01-$0.12 per call.
+ **Context**: Reward calls are an orchestrator's operational responsibility each round; missing reward calls means forfeiting inflationary LPT for that round, which also harms delegators who rely on that income. Gas cost on Arbitrum is approximately $0.01–$0.12 per call.
**Status**: current
@@ -5365,7 +5365,7 @@ Complete reference of terms used across all Livepeer documentation — covering
- **Definition**: A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2-10 seconds for HLS delivery.
+ **Definition**: A time-sliced chunk of multiplexed audio and video data that is independently transcoded for parallel processing in Livepeer's pipeline; typically 2–10 seconds for HLS delivery.
**Tags**: `livepeer:protocol`, `video:processing`
@@ -5933,7 +5933,7 @@ Complete reference of terms used across all Livepeer documentation — covering
- **Definition**: Stability AI's latent diffusion model generating 14-25 frame video clips at 576×1024 resolution conditioned on a single input image.
+ **Definition**: Stability AI's latent diffusion model generating 14–25 frame video clips at 576×1024 resolution conditioned on a single input image.
**Tags**: `ai:model`
diff --git a/v2/resources/index.mdx b/v2/resources/index.mdx
index a92c04023..48fd51343 100644
--- a/v2/resources/index.mdx
+++ b/v2/resources/index.mdx
@@ -27,7 +27,7 @@ Run command: node operations/scripts/generators/content/catalogs/generate-pages-
- [Help Center](help-center.mdx)
- [⚠️ Resource Hub](portal.mdx)
-- [⚠️ Resource Portal](resources-portal.mdx)
+- [⚠️ Resource Portal](portal.mdx)
## Changelog
- [Changelog](changelog/changelog.mdx)
diff --git a/v2/resources/portal.mdx b/v2/resources/portal.mdx
index 0847375ea..b288b0473 100644
--- a/v2/resources/portal.mdx
+++ b/v2/resources/portal.mdx
@@ -1,17 +1,30 @@
---
-mode: frame
-title: 'Resource Hub'
+title: Resource Portal
sidebarTitle: Resource Portal
-description: 'Welcome to the Resource Hub: Changelogs, Guides, Documentation, and Help'
+description: Livepeer Resource Compendium
keywords:
- - livepeer
- - resources
- - resource hub
- - resource portal
- - changelogs
- - guides
+ - home
+ - index
+ - landing
- help
- - documentation
+ - support
+ - contact
+ - faq
+ - resource
+ - resources
+ - reference
+ - references
+ - compendium
+ - livepeer resource
+ - livepeer resources
+ - livepeer reference
+ - livepeer references
+ - livepeer compendium
+ - livepeer resource portal
+ - livepeer resources portal
+ - livepeer reference portal
+ - livepeer references portal
+ - livepeer compendium portal
'og:image': /snippets/assets/media/og-images/fallback.png
'og:image:alt': Livepeer Docs social preview image
'og:image:type': image/png
@@ -19,82 +32,10 @@ keywords:
'og:image:height': 630
pageType: landing
audience: everyone
-lastVerified: 2026-03-30
+lastVerified: 2026-03-17
purpose: landing
-tag: Start Here
---
-import { PortalHeroContent, HeroImageBackgroundComponent, LogoHeroContainer, HeroContentContainer, HeroSectionContainer, PortalCardsHeader, PortalContentContainer } from '/snippets/components/scaffolding/portals/Portals.jsx'
-import { H1, H2, H5, P } from '/snippets/components/scaffolding/frame-mode/FrameMode.jsx'
-import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
-import { BlinkingIcon } from '/snippets/components/elements/links/Links.jsx'
-import { Starfield } from "/snippets/components/scaffolding/heroes/HeroGif.jsx";
-import { SocialLinks } from '/snippets/components/elements/social/SocialLinks.jsx'
-import { BorderedBox } from '/snippets/components/wrappers/containers/Containers.jsx'
-import { CustomCardTitle } from '/snippets/components/elements/text/CustomCardTitle.jsx'
-
-
-
-
-
-
-
-
- Changelogs, guides, glossaries, and help resources for the Livepeer ecosystem.
- Track releases across core infrastructure, AI compute, SDKs, and documentation.
-
-
-
-
- }
- />
-
-
-
-
-
-
-
-
-
-
-
-
+## Resources Portal
+All resources and references in one place!
diff --git a/v2/resources/resource-hub-terms-data.json b/v2/resources/resource-hub-terms-data.json
index bfcc5faf2..351ebba07 100644
--- a/v2/resources/resource-hub-terms-data.json
+++ b/v2/resources/resource-hub-terms-data.json
@@ -130,7 +130,7 @@
},
{
"term": "Cold Start",
- "definition": "The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5-90 seconds.",
+ "definition": "The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5–90 seconds.",
"category": "ai",
"tags": [
"ai"
diff --git a/v2/resources/resource-hub-terms.mdx b/v2/resources/resource-hub-terms.mdx
index 5c51dacf4..6443dee8c 100644
--- a/v2/resources/resource-hub-terms.mdx
+++ b/v2/resources/resource-hub-terms.mdx
@@ -86,7 +86,7 @@ Key terms used across the Livepeer Resources section — spanning protocol mecha
{ Term: "CPU (Central Processing Unit)", Category: "technical", Niche: "hardware", Definition: "The primary general-purpose processor in a computer; in Livepeer, CPU handles node software overhead while GPU handles intensive transcoding and AI inference workloads." },
{ Term: "CLI", Category: "technical", Niche: "dev", Definition: "A text-based interface for interacting with software by typing commands, used to configure and operate Livepeer gateway and orchestrator nodes." },
{ Term: "Codec", Category: "video", Niche: "encoding", Definition: "Software or hardware that compresses and decompresses digital video using a defined algorithm, typically employing lossy compression." },
- { Term: "Cold Start", Category: "ai", Niche: "concept", Definition: "The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5-90 seconds." },
+ { Term: "Cold Start", Category: "ai", Niche: "concept", Definition: "The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5–90 seconds." },
{ Term: "ComfyStream", Category: "livepeer", Niche: "product", Definition: "A Livepeer project implementing a ComfyUI custom node that runs real-time media workflows for AI-powered video and audio processing on live streams." },
{ Term: "Configuration Parameters", Category: "livepeer", Niche: "config", Definition: "CLI flags and environment variables that control node behavior including payment settings, pricing, preferred orchestrators, and network mode." },
{ Term: "ControlNet", Category: "ai", Niche: "model", Definition: "A neural network architecture that adds spatial conditioning controls — such as edge maps, depth, or pose — to pretrained diffusion models." },
@@ -605,7 +605,7 @@ Key terms used across the Livepeer Resources section — spanning protocol mecha
- **Definition**: The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5-90 seconds.
+ **Definition**: The latency incurred when an AI model must be loaded from storage into GPU memory before it can serve its first inference request, typically 5–90 seconds.
**Also known as**: Cold model
diff --git a/v2/resources/resources-portal.mdx b/v2/resources/resources-portal.mdx
deleted file mode 100644
index b288b0473..000000000
--- a/v2/resources/resources-portal.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Resource Portal
-sidebarTitle: Resource Portal
-description: Livepeer Resource Compendium
-keywords:
- - home
- - index
- - landing
- - help
- - support
- - contact
- - faq
- - resource
- - resources
- - reference
- - references
- - compendium
- - livepeer resource
- - livepeer resources
- - livepeer reference
- - livepeer references
- - livepeer compendium
- - livepeer resource portal
- - livepeer resources portal
- - livepeer reference portal
- - livepeer references portal
- - livepeer compendium portal
-'og:image': /snippets/assets/media/og-images/fallback.png
-'og:image:alt': Livepeer Docs social preview image
-'og:image:type': image/png
-'og:image:width': 1200
-'og:image:height': 630
-pageType: landing
-audience: everyone
-lastVerified: 2026-03-17
-purpose: landing
----
-
-
-## Resources Portal
-All resources and references in one place!
diff --git a/v2/solutions/daydream/changelog.mdx b/v2/solutions/daydream/changelog.mdx
index 8f2f15672..e935a46b4 100644
--- a/v2/solutions/daydream/changelog.mdx
+++ b/v2/solutions/daydream/changelog.mdx
@@ -19,7 +19,7 @@ keywords:
pageType: changelog
purpose: changelog
audience: builder
-lastVerified: 2026-04-06
+lastVerified: 2026-03-25
---
import { CustomDivider } from '/snippets/components/elements/spacing/Divider.jsx'
@@ -39,107 +39,11 @@ Track releases for
-
-April 2026
}>
- ## Scope: v0.2.1
-
- -
-