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. Security and Legal Considerations

Contract Timelock

Last updated 1 year ago

In order to instill further confidence during the early stages of the project, we are implementing a timelock mechanism for all necessary proxies. The inclusion of a timelock offers several benefits, as it prevents the proposer from executing any transaction to upgrade or modify the contracts until the designated timelock period has elapsed. This mechanism enhances security and provides reassurance to the users and protocols utilizing the Ramses platform.

To ensure transparency and community awareness, any proposed calls to the timelock will be openly shared with the community. This allows for proper notification of any changes prior to their implementation. We utilize the OpenZeppelin Defender platform () to automate notifications within our Discord community.

The Ramses team is committed to regularly providing updates and information to the community. This includes sharing insights into future upgrades, code changes, and upcoming feature implementations. We strive to maintain open communication and keep our community well-informed about the project's development and progress.

The RamsesTimelock is currently at a 86400s delay (24 hours)

๐Ÿ”
https://www.openzeppelin.com/defender