Central governance router and permissions hub for Ramses.Documentation Index
Fetch the complete documentation index at: https://tech.ramses.xyz/llms.txt
Use this file to discover all available pages before exploring further.
AccessHub coordinates protocol changes across the factory, voter, xRAM, R33, fee-routing contracts, and AutoVault. It mixes three different control surfaces:
- Role-gated actions
- Treasury / multisig-only actions
- Timelock-only actions
Roles
SWAP_FEE_SETTER
Intended for fast operational actions such as:setSwapFees()- Some fee-related CL and legacy operations
compoundR33()
PROTOCOL_OPERATOR
Broader operational role for:- Gauge creation, revival, and kill flows
- Governance whitelist changes
- xRAM whitelist and operator management
- Emissions-ratio and reward-token management
- VoteModule and Minter operational updates
Treasury and Timelock
Some sensitive functions are not role-based:onlyMultisigfunctions are restricted to the treasury addresstimelockedfunctions are restricted to the timelock address
Representative Functions
setSwapFees
setFeeSplitCL / setFeeSplitLegacy
createCLGauge / createLegacyGauge
updateEmissionsMultiplierInMinter
Minter.
setNewVoteModuleCooldown
VoteModule cooldown.
execute
Key Concepts
AccessHubis the main operational control plane for Ramses governance.- It centralizes fee updates, xRAM/R33 administration, gauge management, treasury routing, and several emergency functions.
- Many functions are batched so governance can update several pools or gauges in a single transaction.
- It also owns newer integrations such as
AutoVaultand reward-validator management.
