/// Reading the chain
/// The Senate
The Senate
Each DAO governs itself through a standard OpenZeppelin Governor — propose, vote, timelock, execute — voted in the governance token. A quorum floor keeps the grant from carrying its own votes, and a permissionless rescue keeps a quiet DAO from locking up forever.
/// The lifecycle
Propose → vote → timelock → execute
1 · ProposeAny voterover the proposal threshold
2 · VoteFor / againstvoting power = gTOKEN
3 · TimelockDelayqueued before it can run
4 · ExecuteOn-chainanyone can trigger it
Governance runs the familiar OpenZeppelin Governor path. A holder with enough voting power submits a proposal; voters cast for/against with power measured in the DAO's governance token — the gROHM-style gTOKEN you get by staking and wrapping. A proposal that passes quorum is queued into a timelock and only becomes executable after the delay, which gives holders a window to react — including to rage-quit — before anything lands. Once the delay elapses, execution is permissionless: anyone can push the queued call through.
/// Fixed by the protocol
The quorum floor, and the rescue
Quorum terms — set by the protocolthe grant cannot self-quorum
- ✦a quorum floor sits above the 2.5% ROHME grant
- ✦so the grant's own gTOKEN can never reach quorum by itself
- ✦governance needs real, independent turnout to pass anything
- ✦QuorumRescue is permissionless — anyone may call it
- ✦it prevents a dead-quorum lockout on a quiet DAO
Two failure modes get closed off at the protocol level. The quorum floor is set high enough that the 2.5% grant ROHME receives as gTOKEN can never, on its own, meet quorum — the grant can vote, but it cannot rubber-stamp proposals into passing without genuine independent participation.
The opposite risk — a DAO so quiet that quorum becomes unreachable and governance freezes — is handled by QuorumRescue, a permissionless path anyone can invoke to break a dead-quorum lockout. Governance can be hard to capture without also being impossible to use.
/// Two hands on the same lever
Who controls bond pricing
The creator's path1-hour queue
The creator steers bond pricing through an announced queue: they call queuePriceAction, wait out a one-hour delay, and then anyone can permissionlessly fire executePriceAction. Every price move is telegraphed an hour ahead, so the market sees it coming and no change can be slipped through silently.
The Senate's pathdirect
The Senate has a direct route to the same controls — governance can act on bond pricing without the creator's queue. The two paths coexist: the creator gets a fast, pre-announced hand on the lever for day-to-day tuning, and the token holders keep an independent one through the Governor. Neither displaces the other.
Both paths still answer to the same protocol limits — a bond market can't open more than a 5% discount to the token TWAP, and bond markets stay excess-reserve gated. Bond mechanics are covered in full on the bonds page.