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

Inherited Security

Last updated 1 year ago

The Solidly codebase underwent a partial security audit on January 30, 2022, specifically focusing on the AMM component. The audit was conducted by PeckShield, and the full audit report can be downloaded from the Solidly GitHub repository at:

Furthermore, the inherited codebase used by Velodrome Finance underwent a comprehensive security audit and peer review as part of the Code4rena bug bounty contest. Details of the audit can be found at: . Additionally, a thorough MythX deep scan was performed on the Velodrome contracts.

Velodrome Finance conducted a bug bounty contest from May 23rd to 30th, 2022, on Code4rena (). The contest aimed to cover all the new changes to both the new and original contracts, with rewards of up to $75,000 available.

Solidly launched its bug bounty program in February 2022 on Immunefi.com. To date, no claims have been made for the offered $200,000 rewards. Details of the bug bounty program can be found on their GitHub page: ().

The Ramses team has been instrumental in the development and enhancement of this protocol since its inception over a year ago. We have contributed significantly to various improvements and have deep knowledge of the codebase, making us one of the most knowledgeable teams operating in this space. The Competitive EdgeFixed Solidly Vulnerabilities

While audits can sometimes be seen as primarily serving marketing purposes, we emphasize that our protocol offers both reputable brand name audits and a track record of over a year without any exploits. Additionally, our team possesses an exceptional understanding of the codebase, providing a strong foundation for security and reliability.

๐Ÿ˜Ž
https://github.com/solidlyexchange/solidly/blob/master/audits/e456a816-3802-4384-894c-825a4177245a.pdf
https://code4rena.com/reports/2022-05-velodrome/
https://code4rena.com/contests/2022-05-velodrome-finance-contest
https://github.com/solidlyexchange/solidly/blob/master/SECURITY.md