Arbitrum OpCo Dashboard

DAO Programs & Initiatives Operation Company (OpCo)
1

You might have seen the Notion dashboard that we’ve put together to keep track of DAO initiatives. As a natural extension of that, we’ve put OpCo’s programs on one site: dashboard.arbitrum-opco.com.

There are two parts to it. The first is a page per initiative, pulling together the info that can help delegates get an overview of each initiative at a glance. The second is a live status page for RAD delegates, which is new in kind rather than just a tidier presentation of things we already publish.

The Dashboard

The programs that the OpCo runs currently are on the dashboard: RAD, Firestarters, the wind-down of the AGV, the Code of Conduct, and the Watchdog each have a page covering status, financials, the wallets involved, governance history, reporting cadence, and the latest updates.

The live RAD status page

For delegates enrolled in RAD, we’ve also built a ‘My RAD’ page

It shows:

  • Open votes with no vote recorded from you, and when they close.
  • Votes you cast where the 5-day rationale window is still open and we cannot see a rationale yet.
  • Any proposal where your voting power sat below the 200,000 floor, since that proposal earns nothing regardless of anything else.
  • How you are tracking against the monthly participation threshold.
  • A provisional figure for the month, with a proposal-by-proposal breakdown covering every proposal that counts toward it, including the ones you did not vote on.

The provisional figure might be different from the RAD payout at the end of the month

There is nothing to log into and no wallet to connect. Everything on the page is built from data that’s already public. You just click on your card, and you can see the pending items, or if you’re all set. The URLs are also ‘personalized’ so you can bookmark your page for quick access.

Where the numbers come from

Votes come from Snapshot, for both the off-chain space and the two on-chain governors. Rationales come from the forum. Both are re-checked regularly throughout the day, and the page states when it was last updated; it’s not 100% live.

Feedback

Both parts are new and were, for lack of a better word, vibecoded, so please treat it as a beta. If something feels wrong, if you have feedback we could use to make the dashboard more useful, or if there’s anything you’d like to see added, we’re happy to hear from you. You can reach out to Sinkas at any time.

2 Likes
2

@OpCo (Sinkas) Excellent initiative. Centralizing the state of RAD participation and OpCo programs is a massive upgrade for delegate UX.

Regarding the “vibecoded” beta state: Bootstrapping this via direct Snapshot/Tally queries into a Notion-style interface is the perfect MVP. However, as you scale this for a DAO of Arbitrum’s size, you will inevitably hit architectural friction.

Relying on live, recurring queries directly to Snapshot/Tally to render user-facing pages creates two immediate vulnerabilities:

1. Rate-Limiting & State Sync: High-traffic voting epochs will throttle the API calls, causing the dashboard to fall out of sync or return blank states to delegates right when they need the data most.

2. Historical Immutability: Tally/Snapshot APIs do not cleanly preserve “as-of” historical states. If a proposal’s metadata changes, or a delegate’s power shifts mid-epoch, a live query might overwrite the historical truth needed to calculate RAD payouts accurately.

The Production Upgrade Path:
To harden this from beta to production-grade, OpCo should decouple the visualization layer from the ingestion layer. The ideal architecture requires a lightweight, dedicated backend indexer that polls Snapshot/Tally, mathematically resolves the voting power states, and stores them in a deterministic SQL database. Your frontend then queries this cached, immutable database via a REST API (sub-100ms latency), completely shielding you from upstream API outages.

I architect deterministic governance data pipelines and Impact Oracles. If OpCo is looking to harden this dashboard into permanent, scalable infrastructure, I would be happy to provide a technical review of your current stack or map out the caching architecture for you.

Great work getting the V1 shipped.

2 Likes
3

Clean UX, but transparency needs more depth. Please add wallet level flows, evidence for milestones, and proposal to payout tracking so delegates can verify outcomes, not just read summaries.

1 Like