Central voting, gauge-management, and emissions-routing contract for Ramses. The current implementation is address-based, not NFT-based. Voting power comes fromDocumentation Index
Fetch the complete documentation index at: https://tech.ramses.xyz/llms.txt
Use this file to discover all available pages before exploring further.
VoteModule.balanceOf(owner), and votes are stored per owner address and per weekly period.
Core Functions
vote
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
owner’s votes for the upcoming period.
poke
VoteModule are propagated into the stored next-period vote weights.
distribute
FeeCollector.
createGauge / createCLGauge
claimIncentives / claimClGaugeRewards / claimRewards
Key Concepts
- Votes are recorded for
getPeriod() + 1, not the current period. vote()internally clears prior next-period votes before writing the new allocation.FeeDistributorbalances are keyed by owner address, which is whyVoterdeposits and withdraws vote weight there duringvote()andreset().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.
