Disclaimer

Using Ramses involves material risk. The protocol is noncustodial, and users are responsible for understanding each transaction, the contracts and networks involved, and the effect of any approvals they grant before interacting with the platform.

No Guarantees or Advice

Ramses does not set or guarantee the market price, liquidity, rewards, returns, or future benefits of RAM, xRAM, hyperRAM, liquidity positions, or any other asset. Protocol mechanisms such as emissions, fee routing, burns, and market operations may affect supply or demand but do not guarantee value.

Nothing in these docs is legal, tax, investment, or financial advice, or a promise of profit. Nothing here should be read as a legal conclusion about how any asset, transaction, or activity is classified. Classification and legal obligations depend on the facts, the user, the transaction, and the applicable jurisdiction. Users should obtain advice from qualified professionals where appropriate.

Key Protocol Risks

• Smart-contract risk: Contracts may contain defects, unexpected behavior, integration failures, or vulnerabilities. Audits and testing reduce risk but do not eliminate it.
• Market and liquidity risk: Asset prices, liquidity, fees, incentives, and expected execution can change rapidly. Liquidity providers may experience impermanent loss, inventory imbalance, out-of-range positions, or loss exceeding earned fees and incentives.
• Administrative and governance risk: Authorized roles, multisigs, timelocks, voters, and connected governance contracts can change supported parameters and protocol configuration. Compromised keys, governance failures, or unexpected administrative actions may cause loss.
• Oracle and integration risk: Ramses may depend on tokens, price feeds, routers, aggregators, lending markets, bridges, interfaces, and other external contracts. Failure or manipulation of an external dependency can affect Ramses transactions and positions.
• Cross-chain risk: Bridged or omnichain assets can be affected by bridge, messaging, relayer, validator, finality, replay, depegging, or destination-chain failures.
• Network and execution risk: Congestion, chain reorganization, sequencer or validator outages, gas-price changes, failed transactions, slippage, sandwiching, arbitrage, and other MEV can alter execution or cause loss.
• Wallet and interface risk: Compromised devices, wallets, frontends, RPC providers, domain names, token approvals, or signatures may result in unauthorized transactions or loss. Users should independently verify contract addresses and transaction details.
• Legal, regulatory, and tax risk: Laws, regulatory treatment, access restrictions, reporting duties, and tax consequences vary by jurisdiction and may change.

Users should conduct their own research, assess whether these risks are appropriate for them, and consider all potential outcomes before using Ramses.