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
  • Migration of The RAM token โŒ›
  • Partner Grants Restructuring (Monolithic Voter)โŒ›
  • Optionality of NonFungiblePositions โŒ›
  • Gas Savings โŒ›
  • Pool Immutability โŒ›
  1. RAMSES VIII (V3) [WIP]

Stage II : Full Migration

Last updated 1 year ago

This final stage will encompass all the significant changes to the fundamental code structure of our platform, and will include a migration from V2->V3.

Migration of The RAM token

The current RAM token (Deployed over a year ago) is behind a Proxy contract. While upgradability of the token has been killed, we believe removing the existence of a Proxy on the token will help bolster trust and security of the overall token. Slightly modified tokenomics and emission schedules will be released as well.

Partner Grants Restructuring (Monolithic Voter)

V3 introduces a "Monolithic Voter" contract which will house all partner NFT grants, and will allow them the same functionality they currently have-- but gives permissionless abilities to recast votes and do upkeep without partner's needing to stay on a cadence.

The MonolithicVoter also prevents the possibility of there ever being any malignant behavior from any partner, deterring the ability of voting on pools other than their own + splitting off.

Optionality of NonFungiblePositions

NonFungiblePositions (NFPs) are a great way to track CL-type positions and boosts, but with the boost removal and our already accounted for indexing of identical positions; we no longer need to enforce this on the UI. Benefits of the optionality of NFPs in the core are significant gas improvements, user experience enhancement, and an overall cleaner flow.

Gas Savings

To further enhance the gas savings of our V3 implementation, we will be optimizing our contracts and upgrading from 0.7.6 to ^0.8

Pool Immutability

In our V3 deployment, we will be making all pool contracts fully immutable, and unable to be upgraded or modified. While this is a drastic change from our previous iterations which relied on proxy contracts for storage-- with our optimizations we are able to deploy immutable pools. This change allows users to have a deeper sense of safety and security when interacting with Ramses.

2๏ธโƒฃ
โŒ›
โŒ›
โŒ›
โŒ›
โŒ›