What did you build?
A production Livepeer observability stack: a Rust + Postgres Protocol API that indexes every Livepeer protocol event on Arbitrum One since genesis with block-precise USD pricing, plus a production Discord Network Bot that turns that data into live payout digests, network summaries, slash commands, and per-user DM alerts.
Live + documented:
- Swagger UI - Protocol API
- https://livepeer-network.cloudspe.com - Bundled UI with Protocol API
- https://tools.livepeer.cloud - Example React UI
Why does it matter?
Livepeer already has a subgraph and a basic payout bot, but there are two important gaps for operators, delegators, developers, and accounting workflows:
- The subgraph is useful for “what happened,” but its USD values come from an LPT price that updates once per round, so every event in a round shares one static price and the pricing is not reproducible.
- The existing payout bot is a simple webhook notifier. It does not provide summaries, slash commands, subscriptions, delegator/reward tracking, or DMs.
This work closes both gaps as one usable system:
- Block-precise pricing — every Reward, ticket redemption, bond, fee, and related monetary event is priced at its own block via Uniswap V3 30-min TWAP x Chainlink ETH/USD, with a Chainlink L2 sequencer-uptime liveness gate.
- Byte-deterministic indexing — every RPC call is cached; the full dataset re-derives identically and that invariant is enforced in CI. Numbers are auditable, not just trusted.
- Free, keyless REST + OpenAPI access — plain REST + Swagger, no API key, no GRT tokens, 60+ endpoints covering events, valuations, leaderboards, gateway cash-flow, stake-by-block, governance vote aggregates, CSV exports, and historical price endpoints.
- Delegator-grade Discord access —
/subscribelets users receive DM alerts for orchestrator Reward / Bond / Unbond / Rebond / Fee Share / Reward Cut activity. - On-demand network visibility —
/orchestrator delegators | rewards | ticketsexposes live stake, reward, and ticket summaries; daily, weekly, and monthly network summaries are posted automatically.
The API does not replace the subgraph. It serves the precise-USD, reproducible-pricing, and free-REST needs the subgraph does not. The bot then makes that data usable inside the Discord workflows where delegators and orchestrators already spend time.
Link to the work
- Live API + interactive docs: Swagger UI
- OpenAPI spec: https://livepeer-network-api.cloudspe.com/openapi.json
- Live UI accessing the API: https://livepeer-network.cloudspe.com
- Protocol API (and UI) source: GitHub - Cloud-SPE/livepeer-protocol-explorer · GitHub
- Example React UI accessing the API source: GitHub - Cloud-SPE/livepeer-tools-ui · GitHub
- Network Bot source: GitHub - Cloud-SPE/livepeer-network-bot · GitHub
- Bot live in: Video Miner Group, Livepeer Test Server, Livepeer Official Discord
Evidence of impact
- Protocol API powers the Livepeer Network Bot, which is already in production for the Video Miner Group and @rickstaa’s Livepeer Test Server (Livepeer Foundation), And Livepeer’s Official Discord (#payments channel for payouts webhook).
- Direct API consumers in production: https://livepeer-network.cloudspe.com, https://tools.livepeer.cloud, Many other web hits from several different clients.
- Complete protocol history — all Livepeer protocol data since Arbitrum launch on Feb 15, 2022; ~30 tables; reorg + finality handling; determinism verified in CI.
- Full bot feature set live: webhook digests, period summaries, 5+ slash commands, per-user DM subscriptions, delivery-failure auto-unsubscribe, snapshot-tested embeds, and CI with OpenAPI drift detection.
- Real ongoing cost: dedicated server infrastructure, paid archive Arbitrum RPC, monitoring, and alerting because indexing can fail. This maintenance burden is currently carried solo while the community benefits from the resulting public infrastructure. In addition, the work will continue. I enjoy this project and will continue supporting the features and enhancements as the network/protocol changes.
Community proof points
- @rickstaa (Livepeer Foundation) runs the bot on the Livepeer Test Server and suggested this work be submitted as a retroactive grant
- Bot usage by orchestrators: Many Livepeer Orchestrator/Community Member’s public support of the project found in the Livepeer Discord Payout Bot Grant channel
Amount requested
$3,500 USD-equivalent. Rationale:
- Protocol API scope — full-history indexer, deterministic on-chain pricing engine, historical LPT/ETH pricing oracle, 60+ endpoint REST API, SPA, OpenAPI docs, CSV exports, and determinism CI, all production-deployed.
- Network Bot scope — production Discord service with pollers, period summaries, slash commands, per-user subscriptions, DM delivery system, snapshot-tested embeds, and OpenAPI drift detection.
- Capability gap — block-precise, reproducible USD valuation and Discord-native delegator/orchestrator observability that the existing subgraph and basic payout bot do not provide.
- Infrastructure — partially offsets real ongoing cost for dedicated server infrastructure, paid archive Arbitrum RPC, monitoring, alerting, and maintenance.