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)

BUSL-1.1 License

RAMSES CL is safeguarded under a BUSL-1.1 license

Why?: In light of the recent changes to the RAMSES codebase, we have made the decision to fortify our CL implementation with a BUSL-1.1 license. This approach allows users to easily review our code and understand the nature of their interactions, while also providing protection against potential malicious forking and intellectual property theft.

Authorized Forking: The RAMSES team is open to providing authorized forking of the codebase, based on our discretion. Any team that wishes to use our CL model is free to reach out to us, and we can work on reaching an amicable agreement on the terms.

Benefits of a BUSL-1.1 License for unique solidity contracts:

  1. Transparency: The license allows users to review the code and understand how it functions. This transparency promotes trust and confidence in the codebase.

  2. Protection against malicious forking: The license helps safeguard against unauthorized or malicious forking of the codebase. It ensures that modifications and derivative works are done with proper authorization and under specific terms.

  3. Intellectual property protection: By using the BUSL-1.1 license, the code's intellectual property rights are clearly defined and protected. This helps prevent unauthorized use, copying, or distribution of the code without proper permission.

  4. Collaboration: The license encourages collaboration by allowing authorized forking. It provides a framework for potential users or teams to engage with the codebase and work together on improvements or modifications.

  5. Legal clarity: The BUSL-1.1 license provides a legally recognized framework for the distribution and use of the code. It establishes clear terms and conditions that govern the rights and responsibilities of both the original code creators and any users or forking parties.

Overall, the BUSL-1.1 license promotes transparency, protects intellectual property, and facilitates collaboration while ensuring that the codebase's integrity and security are maintained.

Last updated 1 year ago

๐Ÿ“œ