Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions v2/resources/changelog/go-livepeer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,14 @@ keywords:
'og:image:height': 630
purpose: changelog
audience: everyone
lastVerified: 2026-03-21
lastVerified: 2026-03-24
---

Release notes for the Livepeer node software. For protocol-level changes, see the [Livepeer Improvement Proposals (LIPs)](https://github.com/livepeer/LIPs). For full release binaries, see the [GitHub releases page](https://github.com/livepeer/go-livepeer/releases).

<CustomDivider />

<Update label="Development — March 2026" description="Webcam input for Livepeer Box and Live AI usage tracking" tags={["Livepeer Box", "Live AI"]} rss={{ title: "go-livepeer development updates — March 2026", description: "Webcam input support for Livepeer Box and Live AI session usage tracking" }}>
<Update label="Development — March 2026" description="BYOC auth tokens, webcam input for Livepeer Box, and Live AI usage tracking" tags={["BYOC", "Livepeer Box", "Live AI"]} rss={{ title: "go-livepeer development updates — March 2026", description: "BYOC worker auth tokens, webcam input for Livepeer Box, and Live AI session usage tracking" }}>
## Development updates

### New features
Expand All @@ -37,6 +37,7 @@ Release notes for the Livepeer node software. For protocol-level changes, see th

### Updates

- **BYOC worker authentication** — BYOC workers now register with an authentication token, matching the same auth pattern used by AI runner workers. This prevents unauthorized workers from joining an orchestrator's pool. Orchestrators running [BYOC pipelines](/v2/gateways/guides/tutorials/tutorial-2-byoc-cpu-pipeline) benefit from this without any configuration changes.
- **Live AI usage tracking** — Live AI sessions now emit usage events for each payment interval, enabling more accurate usage-based billing for gateway operators. This lays the groundwork for improved billing visibility in future releases.

</Update>
Expand Down
Loading