RAMSES
  • INTRODUCTION TO RAMSES
    • ๐Ÿ”†What is RAMSES?
      • ๐Ÿš€Why Arbitrum? ๐Ÿ’™๐Ÿงก
    • ๐Ÿซ‚Our Partners
    • โ˜ฏ๏ธve(3,3) Fundamentals
      • Dilution Protection (Rebase)
      • veRAM (veNFT)
        • ๐Ÿ’ฐveRAM Revenue Distribution Schedule
        • ๐ŸคThe RAMSES Bazaar (PaintSwap)
    • ๐Ÿ”ฎDEX Functionalities
      • Swaps
      • Voting
      • Bribing
      • Vesting (veNFT Management)
      • LP Staking (Legacy)
    • ๐ŸŽ“RAMSES Analytics
    • โš”๏ธThe Competitive Edge
      • Expert Risk Management
      • User Focused, Not Competitor Focused
      • Novel Changes & Codebase Restructuring
  • RAMSES CL (V2)
    • ๐Ÿ—ฏ๏ธOverall Changelog
    • ๐Ÿค”Concentrated Liquidity
      • ๐Ÿ”ขDefault Fee Tiers / Tickspacing
      • ๐ŸฆญFee Distribution
      • ๐Ÿ“’Improvements From UniswapV3
    • ๐Ÿ†CL Gauges
      • ๐Ÿ’ฅCL Boosting [DEPRECATED]
    • ๐ŸCompetitive Farming
    • ๐Ÿ“œBUSL-1.1 License
      • ๐Ÿ”’Protected Contracts
  • RAMSES VIII (V3) [WIP]
    • ๐Ÿ‘‘The Next Iteration For The Kingdom
    • ๐Ÿ›ฃ๏ธThe Road Ahead
    • 1๏ธโƒฃStage I : Initial Changes
    • 2๏ธโƒฃStage II : Full Migration
  • RAM Tokenomics
    • ๐Ÿ“ŠRAM Token Distribution
    • ๐Ÿ“ˆEmissions Schedule
    • โŒxRAM
      • How is xRAM obtained?
      • How is xRAM used?
      • โ˜ธ๏ธxRAM "Flywheel"
    • ๐ŸŒ€Dilution Protection (3,3) Rebases
    • ๐Ÿ’งRAM LGE - Liquidity Generation Event
      • Price Determination
  • ๐ŸงธRAMSES Services
    • ๐Ÿ›ซLaunchpad & LGE
    • ๐Ÿ†˜Solidly Model Vulnerability Support
    • ๐Ÿ”„ve(3,3) Advisory
      • ๐Ÿง Projects Supported (Case Studies)
  • Resources
    • ๐Ÿ“„Deployed Contract Addresses
    • ๐Ÿ“ฑdApp and Socials
    • ๐Ÿ“ธRAMSES Media Kit
    • ๐ŸŒ‰Bridging To Arbitrum One
    • ๐Ÿ“ƒWhitelisting Process
  • Security and Legal Considerations
    • ๐Ÿ–‹๏ธFormal Audits
    • ๐Ÿ›Fixed Solidly Vulnerabilities
    • ๐Ÿ› ๏ธWhy Proxy Contracts?
    • ๐Ÿ”Contract Timelock
    • ๐Ÿ˜ŽInherited Security
    • โš–๏ธRisks and Legal Disclosures
Powered by GitBook
On this page
  1. RAMSES CL (V2)
  2. CL Gauges

CL Boosting [DEPRECATED]

RAMSES CL has a boosting mechanism that allows you to attach your veRAM NFT to a position in order to earn more rewards

Last updated 1 year ago

Boost was removed from RAMSES as of April 2024

The RAMSES CL implementation has a unique boosting feature akin to that of the V1 AMM. A max total boost of 2.5x, as before, has been retained and can be calculated easily through the contracts (along with the front-end). There are two (tranches) for rewards of the epoch: - 40% of emissions/rewards are allocated to the Base Tranche - 60% of emissions/rewards are allocated to the Boost Tranche The 40% represents the base yield of 1.0x, while the 60% is an extra 1.5x. Summated these achieve the max total boost of 2.5x.

Simple Boost Formula:

Boost=(boostedLiquidityย รทliquidity)ย +1Boost = (boostedLiquidity \ \div liquidity) \ + 1 Boost=(boostedLiquidityย รทliquidity)ย +1

These values can be found on the GaugeV2 contracts for the associated pair (e.g. ARB/ETH 0.05%), by inputting the NFP ID.

Boost can also be viewed as a % ratio of your TVL in the pool, in relation to your veRAM % of the pool. If you are 20% of the TVL in a pool, you need >= 20% of the veRAM attached to the pool to maintain a 2.5 MAX boost.

An example of the Boosting interface can be seen below:

๐Ÿ†
๐Ÿ’ฅ
https://ramses.exchange/boost-cl