Livepeer Discord Protocol Data Bot & Public Protocol Data API

Retroactive Grant Applications
1

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.

:link: Live + documented:


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 — /subscribe lets users receive DM alerts for orchestrator Reward / Bond / Unbond / Rebond / Fee Share / Reward Cut activity.
  • On-demand network visibility — /orchestrator delegators | rewards | tickets exposes 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


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.

5 Likes
Pre-Proposal: Network Engineering SPE
2

@MikeZupper Thank you for the official application to the retroactive grants, the next step is review from the team for confirmation.

1 Like
3

Amazing work, Mike. From an impact perspective, the Discord poll is a strong signal, with 10 people already saying they’re using the bot. That’s great evidence that this is creating real value for the community.

I’m attaching the screenshot here as evidence of that usage.

image
image990×1472 121 KB

Screenshot 2026-06-30 at 15.58.11
Screenshot 2026-06-30 at 15.58.112206×276 54.6 KB

2 Likes
4

Retro Grant Pre-Screen — Livepeer Discord Protocol Data Bot & Public Protocol Data API

Applicant: MikeZupper (Cloud-SPE)
Application: Livepeer Discord Protocol Data Bot & Public Protocol Data API — Retroactive Grant Applications
Amount requested: $3,500 USD-equivalent in LPT (under the $5k max)
Screened against: Network Engineering SPE — Retro Grants Funding Process (rubric + execution standards)

Verdict

:white_check_mark: READY FOR REVIEW — Recommend APPROVE.

Clears every gate with no Return or Decline condition, and maps to the rubric’s strongest cell: high importance × broad confirmed reach → Approve. This is production-grade public infrastructure (a free, keyless protocol API plus a live Discord observability bot) that fills documented gaps the subgraph and the basic payout bot do not, is endorsed by the Foundation’s own technical lead, and shows multiple confirmable adopters. The $3,500 request sits below the ceiling and is well-justified.

Rubric scorecard

Criterion Result Notes
Scope (3 eligible areas) :white_check_mark: Pass Squarely in Delegators / Governance & Network Observability (dashboards, Explorer improvements, data pipelines) and Orchestrators / Tooling & Infrastructure
Shipped & reviewable :white_check_mark: Pass Production-deployed: live API + Swagger docs, OpenAPI spec, three open-source repos, deterministic indexing verified in CI. Not a PoC
Community proof point (required) :white_check_mark: Met (strong) rickstaa (Foundation) runs it on the Livepeer Test Server and suggested the submission; bot live in the official Livepeer Discord
Impact — importance of need :green_circle: High Free keyless REST/OpenAPI (no GRT), block-precise reproducible USD pricing, delegator/orchestrator Discord observability — fills real, named gaps in existing tooling
Impact — breadth already solved :green_circle: Broad Live in 3 named servers (Video Miner Group, Foundation Test Server, official Livepeer Discord #payments); direct API consumers in production; ~10 community members report active use in a Discord poll
Quality & completeness :green_circle: High 60+ endpoints, snapshot-tested embeds, reorg/finality handling, OpenAPI drift detection in CI, full protocol history since Arbitrum genesis
Proportionality :green_circle: Reasonable $3,500 (below $5k cap), itemized, partly offsets real ongoing infra cost (dedicated server, paid archive RPC, monitoring)
Red-flag check (AI-slop / speculative) :white_check_mark: Clean Substantive production system with ongoing maintenance commitment; not speculative

Matrix placement: high importance × broad reach → Approve.

Sources: Protocol Data Bot thread · Retro Grants Funding Process — Network Engineering SPE · Skill:Review Retroactive Grant

5
  • @rickstaa (Livepeer Foundation) runs the bot on the Livepeer Test Server and suggested this work be submitted as a retroactive grant

Confirming the statement above. Over the past year, I have used Mike’s bot and tools almost daily in my test server alongside the explorer to track paid tickets and identify which gateways processed those payments as it did provide more accurate and complete data than the old payment bot.

Note: As stated on Discord, to ensure an objective review, I stepped down from the review board for this grant only, as I am biased since I was already using this tool before the grant was submitted. This message therefore merely here to acknowledge I do use the tool.

1 Like
6

@MikeZupper
For the record, please add your wallet address to the grant application.

7

you can just use my xodeapp.xyz address 0xd00354656922168815fcd1e51cbddb9e359e3c7f

2 Likes
8

Review Team recommendation: Approve — $3,500 USD-equivalent

The Review Team verified a substantial, publicly deployed Livepeer observability system comprising a Rust/Postgres protocol indexer, a 62-path keyless REST/OpenAPI service, two web UIs—the bundled Protocol Explorer and separate React Tools UI—and a Discord bot supporting payout digests, network summaries, commands, subscriptions, and direct alerts.

The live API returns canonical, finalized records beginning at Arbitrum block 6,072,093 on 15 February 2022, corresponding to Livepeer’s Confluence migration, and extends through current finalized blocks. It provides block-anchored ETH and LPT valuation outcomes for monetary events. The architecture also demonstrates meaningful attention to reorg handling, deterministic replay, testing, and API consistency. While we did not independently replay the complete history, source review and live sampling support the project’s core technical claims.

The project addresses a relevant gap in Livepeer observability, accounting, and Discord-native access. Its public deployments and community use provide credible adoption evidence, and the requested amount is proportional to the completed scope.

For future improvements, we recommend a unified landing page explaining the different interfaces, a public indexing and pricing-health dashboard, improving discord onboarding with orchestrator search, a test-DM confirmation, configurable alert preferences, and clearer delivery-status guidance. Also availability of privacy-preserving adoption metrics, and operational documentation to reduce reliance on a single maintainer would be meaningful upgrade.

2 Likes
9

Thanks @jjassonn69 and review team for the support and feedback. I will be taking these improvements and applying them to the project roadmap.