This guide provides a technical overview for developers looking to integrate with Ramses Exchange Official, focusing on its core Ramses ve(3,3) DEX architecture and how to interact with its liquidity and governance mechanisms on Ramses on Arbitrum.
Step 1: Understanding the ve(3,3) Architecture
Ramses is a powerful DEX built on the "ve(3,3)" model, a game-theoretic design for incentivizing liquidity, adapted for the Arbitrum network.
Tokenomics: It uses a dual-token system: RAM Token Staking (the utility token) and veRAM (vote-escrowed RAM).
Mechanism: Users lock RAM to receive veRAM. veRAM holders receive protocol fees, bribes, and the power to direct Ramses Emissions to specific Ramses Liquidity Pools through Ramses Gauge Voting.
Step 2: Providing Liquidity and Earning Emissions
Developers can build interfaces for users to become liquidity providers (LPs).
Deposit: Users deposit an equivalent value of two tokens into a chosen pool.
Receive LP Tokens: They receive LP tokens, which must then be staked in the corresponding "Gauge" contract.
Gauge Rewards: The amount of RAM emissions earned by LPs in a specific pool is directly proportional to the votes (veRAM weight) that pool receives. Your dApp can query the gauge contracts to display current emission rates (APRs).
Step 3: Interacting with veRAM Governance
For developers building governance-focused dApps or analytics tools, veRAM is the key.
Locking RAM: Users lock their RAM for a chosen duration to receive veRAM.
Voting: veRAM holders vote weekly on which gauges should receive RAM emissions. This is the core of the ve(3,3) model.
Bribes: Protocols can attach "bribes" to gauges to incentivize veRAM holders to vote for their pools. Your dApp can display these bribes to inform voters.
Step 4: Swaps and Security
To Trade on Ramses, users interact with its AMM router contracts. The security model, a key part of answering "Is Ramses Exchange Safe?", relies on its audited codebase and the transparent, on-chain nature of the ve(3,3) system.
For all smart contract ABIs, gauge addresses, and SDK documentation, refer to the Full Official Documentation.
Top comments (0)