Skip to main content
Central voting, gauge-management, and emissions-routing contract for Ramses. The current implementation is address-based, not NFT-based. Voting power comes from VoteModule.balanceOf(owner), and votes are stored per owner address and per weekly period.

​
Core Functions

​
vote

Casts or recasts votes for owner into the next weekly period. The raw weights array is normalized against the owner’s current VoteModule balance, so it does not need to sum to a fixed constant. The call can be made by:
  • owner
  • An approved delegate/admin recognized by VoteModule
  • AccessHub

​
reset

Clears owner’s votes for the upcoming period.

​
poke

Recasts the owner’s last vote weights using the owner’s current voting power. This is how balance changes in VoteModule are propagated into the stored next-period vote weights.

​
distribute

Advances emissions and distributes them to a specific gauge. For CL gauges, this flow also triggers protocol-fee collection from the pool through FeeCollector. When DLMM is configured and the target is a registered DLMMRewarder, it sends RAM to the rewarder, updates its streaming rate, and synchronizes the pool’s fee-routing state.

​
createGauge / createCLGauge

Governance-only gauge creation entrypoints for legacy and concentrated-liquidity pools.

​
createDLMMRewarder

Governance-only DLMM onboarding. It:
  1. Verifies the pool belongs to the configured DLMMFactory
  2. Collects any pre-rewarder protocol fees
  3. Deploys and links a beacon-proxy rewarder
  4. Creates the pool’s FeeDistributor
  5. Registers the pool/rewarder mappings
  6. Marks the rewarder alive and sets the pool’s gauged protocol share
Related governance functions configure the DLMM factory, rewarder factory, rewarded-bin range, and authorized router/manager list.

​
claimIncentives / claimClGaugeRewards / claimRewards

Helpers for collecting fee-distributor incentives and gauge rewards.

​
Key Concepts

  • Votes are recorded for getPeriod() + 1, not the current period.
  • vote() internally clears prior next-period votes before writing the new allocation.
  • FeeDistributor balances are keyed by owner address, which is why Voter deposits and withdraws vote weight there during vote() and reset().
  • distribute() coordinates both emissions and fee routing, making it one of the central weekly-maintenance flows in the system.
  • Whitelisting, gauge lifecycle changes, reward-validator configuration, and other privileged actions are gated through governance and AccessHub.
  • DLMM users vote for the pool address; the associated DLMMRewarder is the emission target stored in gaugeForPool.
  • A DLMM rewarder is a hook, not a GaugeV3 contract.
At the Robinhood snapshot at block 22,674,244, the DLMM factory reported a zero voter() address, so these rewarder flows were not live there.