Authors: Anna Riabokon (RARI Foundation) & Kaf — Anode Status: Request for Comment / Temperature Check Target outcome: Community alignment
TL;DR
RARI DAO does not have a single governance problem; it has several overlapping governance design issues that now need to be addressed together.
First, authority is split across two live governance surfaces: Rari DAO v1 on Ethereum and RARI DAO v2 on RARI Chain. Second, delegate onboarding remains harder than it should be, especially for new participants trying to understand where and how to participate. Third, the recent uncertainty around Tally’s future exposed the need for a more explicit infrastructure resilience plan.
This RFC proposes a coordinated governance cleanup process around three goals:
- Clarify one canonical venue for binding governance decisions.
- Clarify the role of RARI Chain in ecosystem coordination, signaling, and chain-specific activity.
- Relaunch delegate onboarding through a clearer, more accountable, and more sustainable delegate track.
The current preferred direction is to re-establish Ethereum mainnet as the primary venue for binding governance decisions, while continuing to position RARI Chain as an important venue for ecosystem coordination, signaling, and chain-specific activity. We want to be transparent that this is the direction we currently lean toward, but this RFC is intentionally being published as a temperature check before any binding RRCs are drafted, and the final direction should ultimately be shaped by community feedback.
The delegate program is included here because governance structure and delegate participation are closely linked. However, depending on community feedback, delegate onboarding and renewal may later be advanced as a separate RRC once the broader governance direction is clarified.
1. Why now
Three things converged in Q1–Q2 2026 that make this the right moment to address governance architecture as a whole rather than in pieces:
Infrastructure resilience came into focus. Tally, the governance UI most of the DAO uses today, announced corporate shutdown. ScopeLift subsequently took over operation of the Tally governance platform, and by early May the working assumption stabilized around continuity. While the Tally governance app appears to remain operational under ScopeLift’s stewardship, the episode made clear that RARI should treat the governance UI as replaceable infrastructure, not as the governance system itself. That argues for standard, portable contracts (OpenZeppelin Governor) underneath whatever UI we use.
The migration to RARI Chain delivered partial results. The Season 1 staking program moved RARI from near-zero activity on the new chain to 196,792 RARI delegated, 751 active stakers, 26 active delegates, and 42 unique voters. That is real progress. It also represents roughly 45% of the 300k RARI migration target, and recent v2 proposals still draw 15–23 voting addresses. The migration moved some activity, but not the constitutional center of gravity, and we should be honest about that before designing the next phase.
Treasury management evolved. RRC-51 transferred operational treasury management to the Foundation in late 2025, and the Q1 2026 transparency report shows continued treasury diversification efforts, operational treasury activity (including ETH staking and OTC treasury operations), and ongoing separation across Operations, Treasury, and Ecosystem Growth allocations. As treasury stewardship and ecosystem initiatives continue to expand, the governance venue where strategic oversight is exercised should remain unambiguous. The cleaner the venue, the more credible the oversight.
2. Diagnostic snapshot
| Signal | What we see today | What it suggests |
|---|---|---|
| Two live governance surfaces | v1: 68 proposals, 1.19K delegates, ~$300 residual treasury, last vote RRC-55 (defeated, Feb 2026). v2: 9 proposals, 237 delegates, 0 treasury sources, last vote Jan 2026 (ETH staking activation). | Legitimacy is split; new delegates don’t know which venue is authoritative |
| Electoral depth | 12–18 addresses on recent v1 votes; 15–23 on recent v2 votes | The challenge is not only “more voters” — it’s that participation is diluted across two surfaces |
| Onboarding friction | Forum thread reports no working route to convert RARI → veRARI for new v1 delegates | Without a fixed entry path, incentive programs end up rewarding insiders who already know how to navigate the flow |
| Documentation gap | Governance onboarding post still carries TBD fields for submission threshold and quorum after token migration | The process exists but rests on a moving base |
| Infrastructure dependency | Tally corporate shutdown → ScopeLift takeover → working continuity within ~60 days | Governance should be portable across UI vendors by design, not by luck |
| Delegate program evolution | Launchpad (2023) → DIP (2024) → DIP replacement (May 2025) → DIP v2.0 (Nov 2025) covering both v1 and v2 | Good instincts, but the structure has changed often enough that delegates can’t reliably build careers on it |
The diagnostic is not “RARI governance is failing.” Governance is functioning — RRC-51, RRC-53, RRC-54, the staking program, and the security council election all executed. The diagnostic is: we are running a healthy governance through an architecture that fragments its own authority, and the cost shows up at the margins — new delegates, treasury legibility, infrastructure portability.
3. Direction we are leaning toward
We want to be clear: this section describes our current preferred direction, not a settled plan. The community feedback in this thread is what will determine whether this is the right shape, whether it needs significant adjustment, or whether a different path serves RARI better.
3.1 Explore re-anchoring canonical governance on Ethereum mainnet
The historical argument against mainnet was cost. That argument has weakened materially:
- Gas cost. Etherscan recently showed standard gas around 0.107 gwei. Even under stress scenarios (10–30 gwei), a single vote costs roughly $1.70–$5.10 — and with Tally Relay (or equivalent gasless infrastructure) sponsoring votes and delegations, the cost to the participant is zero. ENS already operates this way.
- Standards and portability. A standard OpenZeppelin Governor + Timelock with a Tally-compatible wrapper over the existing RARI token is a well-understood pattern. The original RARI Chain migration documentation already contemplated a wrapper approach for multichain governance.
- Inherited legitimacy. Mainnet would inherit the full v1 delegate base, the full proposal history, and the institutional credibility of the longer-running surface — rather than asking v2 to rebuild that from scratch.
What could live where, under this direction:
| Layer | Function | Nature |
|---|---|---|
| Forum | Idea, debate, technical review, rationale, conflict-of-interest disclosure | Off-chain |
| Temp check | Discourse poll, optionally Snapshot, non-binding signal | Off-chain |
| Governor + Timelock on Ethereum mainnet | Treasury, upgrades, fees, budgets, charters, elections, structural grants | On-chain, binding |
| Security Council | Emergency pause, hotfix, veto of clearly harmful payloads only | Exceptional |
| Foundation & committees | Execution within DAO-approved mandates; quarterly reporting | Operational |
| RARI Chain | Primary venue for ecosystem activity, signaling, and chain-specific execution | Subordinate to the canonical governance layer for constitutional decisions |
Initial parameter ideas for community discussion (these are starting points, not proposals):
| Parameter | Starting point |
|---|---|
| Proposal threshold | max(5,000 RARI, 0.25% of delegated supply) |
| Quorum | max(20,000 RARI, 2% of delegated supply), For + Abstain |
| Voting period | 5–7 days |
| Voting delay | 0–1 day |
| Timelock | 3 days for constitutional / treasury / permissions changes |
| Emergency action validity | All emergency actions expire if not ratified on-chain within 30 days |
| Review cadence | Parameters reviewed at 90 days, then quarterly |
These numbers are anchored in the original veRARI design (5-day vote, 2-day cooldown, 5,000 threshold) and standard practice for governance contracts at comparable DAO scale.
3.2 Narrow the Security Council mandate
The Security Council approved in 2025 (3/5 veto safe, 4/5 upgrade safe, annual mandate, 60,000 RARI annual cost) is a useful safety net and we are not proposing to remove it. We would propose to narrow it under the new architecture:
- Three powers only: temporary pause, short-term operational reversal, blocking of manifestly harmful payloads.
- No discretion over strategy, treasury allocation, or resource assignment.
- Every use produces a public report within 24 hours and automatically opens an on-chain ratification or revocation proposal.
- Sunset clause on the mandate, with renewal requiring an affirmative DAO vote.
Delegate renewal and onboarding
This section is included here because governance architecture, delegate participation, and delegation incentives are closely linked. Depending on community feedback, delegate onboarding and delegate structure may later move into a separate RRC once the canonical governance direction is finalized.
One of the clearest lessons from the current governance structure is that onboarding new delegates remains harder than it should be. Participation is fragmented across multiple governance surfaces, documentation is inconsistent, and newer contributors often lack a clear path into meaningful governance participation.
At the same time, existing delegates have already built governance history, participation records, and community legitimacy across both Ethereum mainnet and RARI Chain governance. The goal of governance cleanup is not to reset participation from zero, but to reduce fragmentation and create a clearer long-term structure.
As part of this process, we propose reopening delegate onboarding through a smaller, more focused cohort-based structure while also clarifying delegation continuity if canonical governance is re-anchored on Ethereum mainnet.
Initial direction for discussion:
- Smaller cohorts (for example 6–8 delegates rather than larger intake rounds)
- Delegates selected based on demonstrated governance activity, ecosystem contributions, and relevant expertise
- Temporary delegated voting power distributed by the DAO to help new delegates meaningfully participate from day one
- Public delegate profiles and rationale transparency expected as baseline requirements
- Periodic review of delegate activity and participation
- Clearer continuity between onboarding, delegation incentives, and long-term governance participation
- Clear delegation migration guidelines if governance architecture changes
The goal is not simply to increase the number of delegates, but to create a clearer and more sustainable pathway for capable contributors to become long-term governance participants.
More detailed structures around delegate evaluation, incentives, accountability mechanisms, delegation migration, or long-term delegate compensation can be proposed separately after the canonical governance direction is finalized.