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
- Operator-routed DLMM pool and rewarder creation
- 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
createDLMMPool / createDLMMRewarder
PROTOCOL_OPERATOR entrypoints for operator-routed DLMM onboarding. createDLMMPool() can add tokenY to the factory quote-asset list before creating the pool. Regular users create pools directly through an open factory preset.
DLMM fee setters
setFeeSplitDLMM() accepts the configured Voter or a SWAP_FEE_SETTER; protocol share is measured out of 10,000. The full AccessHub changes only each pool’s base factor, preserving its other fee fields. AccessHubSatellite accepts the full packed static-fee parameter set instead. Check the deployed implementation before encoding an operator transaction.
Multisig-only DLMM controls include:
- Configuring the factory and rewarder factory in
Voter - Updating the beacon implementation used by existing rewarders
- Granting or revoking hook-manager and authorized-manager status
- Accepting factory ownership
- Changing a rewarder’s eligible bin range
- Updating the global preset protocol share for future pools
- Repairing the fee collector’s
Voteraddress
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. - For DLMM, it owns material economic and hook configuration, but the reviewed pool interface does not expose an AccessHub function that withdraws arbitrary user LP principal.
