# Terms and policies *Last updated on March 24th, 2026* Welcome to Ferra ("Ferra," "we," "our," or "the Protocol"), a decentralized trading protocol offering permissionless spot swaps and liquidity provision via smart contracts. This document outlines the legally binding Terms of Use and Privacy Policy governing your use of Ferra, including its frontend interface at [ferra.ag](https://ferra.ag/) direct on-chain interactions, or third-party integrations. By accessing or using Ferra in any manner, you agree to be bound by these terms and policies. ### 1. Definitions * **Ferra:** A decentralized protocol that enables spot trading through Concentrated Liquidity Market Maker (CLMM), Dynamic Liquidity Market Maker (DLMM), and Dynamic Automated Market Maker (DAMM) models. Ferra may also integrate with third-party protocols to provide additional functionalities, including perpetual futures trading (“Perps”) and margin trading. In addition, Ferra includes certain social features designed to facilitate user engagement and interaction within its ecosystem. * User or You: Any individual or entity interacting with Ferra’s smart contracts, frontend, or integrated services. * Frontend: The user interface at [ferra.ag](https://ferra.ag/) or mirror domains. * Smart Contracts: Immutable, open-source code deployed on-chain for Ferra's core functionalities. * Protocol Contributors: Anonymous or pseudonymous developers, community members, or DAOs contributing to Ferra. * Third-Party Services: External tools or integrations (e.g., wallets, RPC nodes, analytics, oracles) used with Ferra. ### 2. Acceptance of Terms By interacting with Ferra (e.g., browsing the frontend, connecting a wallet, trading, providing liquidity, or accessing documentation), you: * Confirm you have read, understood, and agree to these Terms and Privacy Policy. * Are at least 18 years old and legally eligible to use decentralized financial applications in your jurisdiction. * Are solely responsible for complying with applicable laws, including tax obligations and regulatory requirements. * Acknowledge that Ferra is a permissionless protocol, and you use it at your own risk. If you do not agree, you must stop using Ferra immediately. ### 3. Platform Description Ferra is a non-custodial, permissionless protocol that enables: * **Spot Trading:** Through CLMM, DLMM, and DAMM models, allowing liquidity providers to concentrate capital within specific price ranges for greater capital efficiency. * **Perpetual Trading:** Ferra may provide access to perpetual futures trading (“Perps”) through integrations with third-party protocols, including but not limited to Hyperliquid. * **Margin Trading:** Ferra may develop or integrate margin trading solutions, such as DeepBook. Users interact with the Ferra frontend while orders are executed via integrated third-party protocols. * **Liquidity Provision:** Users can supply liquidity to pools and earn fees based on active price ranges. * **Trading Terminal:** Enables users to monitor real-time market data, analyze charts, execute buy/sell orders, and manage portfolios across various DeFi protocols, offering faster and more advanced tools. * **SocialFi:** Features that enable users to stay connected, share ideas, and participate in community guilds within the Ferra or Sui ecosystem. * **Mobile Trading Application:** Ferra may develop a mobile trading application to provide a more convenient user experience. This application may connect to Ferra’s core trading engine and/or integrate with third-party partners to enable trading and related functionalities. Ferra is not a broker, intermediary, centralized exchange, or licensed financial service provider. The frontend serves solely as a convenience layer for interacting with immutable smart contracts. ### 4. Eligibility and Jurisdictional Restrictions To use Ferra, you must: * Be at least 18 years old. * Not be a citizen, resident, or located in jurisdictions where decentralized protocols are prohibited (e.g., United States, OFAC-sanctioned countries, or regions with explicit DeFi bans). * Not use Ferra for illicit purposes, including money laundering, terrorist financing, or on behalf of sanctioned entities. We may geo-block frontend access in restricted jurisdictions to comply with local laws, but smart contract interactions remain permissionless. You are responsible for ensuring compliance with your local regulations ### 5. User Responsibilities You agree to: * Use Ferra in good faith, avoiding malicious activities (e.g., front-running, oracle manipulation, or exploiting smart contract vulnerabilities). * Secure your private keys, wallet credentials, and recovery phrases. Ferra does not store or manage your keys. * Not impersonate others, engage in fraud, or use Ferra for illegal activities. * Monitor and manage your liquidity positions (e.g., withdrawing assets when price ranges are crossed). * Accept that all blockchain transactions are irreversible and publicly visible. * Bear all risks associated with your transactions, including losses due to market volatility or smart contract errors. ### 6. Privacy and Data Handling **Information We Do Not Collect** Ferra does not collect or require: * Personal identifiable information (e.g., names, emails, phone numbers, or government-issued IDs). * KYC (Know Your Customer) documentation or physical addresses. * Private keys, seed phrases, or wallet credentials. Never share sensitive personal data with Ferra interfaces, community channels, or third parties claiming affiliation. **Information We May Access** When using Ferra, we may access or temporarily process: * Public Wallet Address: Required for smart contract interactions, visible on the blockchain. * Transaction Data: All trades, swaps, and liquidity provisions are recorded publicly on-chain. * Device & Browser Metadata: Anonymized data like screen size, browser type, or language preferences for UX optimization. * Frontend Interaction Logs: Anonymized data on feature usage (e.g., swaps, deposits) to improve performance. * Analytics Data: Aggregated, anonymized usage trends via privacy-first tools (e.g., Plausible, Umami). This data is not linked to individuals and is used solely to enhance functionality and user experience. **Cookies and Local Storage** The Ferra frontend may use: * Session Cookies: To maintain UI settings during your session. * Local Storage: To cache preferences (e.g., wallet connection status, language settings). Cookies are not used for tracking, profiling, or advertising. You can disable cookies via browser settings, though this may affect functionality. **Third-Party Services** Ferra may integrate with third-party services, including but not limited to: * **Wallets:** Such as Sui Wallet (Slush), Phantom, or other compatible wallets. * **RPC/Node Infrastructure:** To enable reliable blockchain connectivity and transaction processing. * **Analytics Tools:** Privacy-focused tools used to analyze usage trends and improve the platform. * **Price Feeds/Oracles:** To provide accurate, real-time market data. * **DEX Aggregators:** To route and execute trades at optimal rates with minimal slippage. * **Perpetual and Margin Protocols:** To facilitate the execution of perpetual futures and margin trading orders. These services have their own privacy policies, and Ferra is not responsible for their data practices. Review third-party policies before use. **Data Retention** Ferra does not store data on centralized servers. Data is: * Stored locally in your browser (cache or localStorage). * Queried directly from the blockchain (public and immutable). * Retained in anonymized, aggregated form for analytics (if applicable). Blockchain data is permanent and cannot be deleted. **Your Privacy Responsibilities** * Safeguard your private keys, wallet credentials, and recovery phrases. * Verify transactions before signing to avoid phishing or malicious contracts. * Understand that blockchain activity (e.g., wallet addresses, transactions) is public and traceable by anyone. * Use privacy tools (e.g., anonymous wallets) if desired, as Ferra does not provide anonymity. Ferra contributors will never request sensitive information. **Transparency in Decentralized Context** As a decentralized protocol, Ferra’s on-chain activities are transparent. Anyone can view transaction data on the blockchain. True privacy must be managed at the wallet or chain level. ### 7. No Warranties Ferra is provided “as-is” and “as-available.” As an experimental DeFi protocol, it may contain bugs, vulnerabilities, or unexpected behavior. We make no warranties regarding: * Uptime or availability of the frontend or smart contracts. * Accuracy of data displayed (e.g., prices, balances, or order history). * Fitness for any financial, legal, or commercial purpose. * Security against exploits or hacks, as seen in incidents like the Cetus exploit. You use Ferra at your own risk and should conduct independent research. ### 8. Risk Disclosures You accept the following risks: * Market Volatility: Digital assets may lose all value due to price fluctuations. * Smart Contract Risks: Bugs or exploits may lead to loss of funds (e.g., manipulation of price curves, as seen in the Cetus exploit). * MEV (Miner Extractable Value): Front-running or transaction reordering by miners or validators. * Market Manipulation: Third-party actions like wash trading or pump-and-dump schemes. * Liquidity Risks: Low liquidity may cause high slippage or inability to withdraw funds. * Regulatory Risks: Potential future restrictions or enforcement actions in your jurisdiction. * Impermanent Loss: Liquidity providers may face losses due to price divergence in pools * Third-Party Risks: Reliance on external wallets, oracles, or infrastructure. Conduct due diligence and consult professional advisors before using Ferra or any DeFi protocol. ### 9. No Fiduciary Relationship Your interaction with Ferra does not create a fiduciary, agency, partnership, or joint venture relationship. Protocol Contributors owe no duties or liabilities beyond maintaining the open-source protocol. ### 10. Intellectual Property * The Ferra name, logo, and frontend UI may be protected by copyright or trademark. * Smart contracts and documentation are open-source under permissible licenses (e.g., MIT, GPL), unless stated otherwise. * You may not misuse Ferra's branding, impersonate contributors, or infringe intellectual property rights of others. ### 11. Fees and Protocol Sustainability Ferra may apply the following types of fees: * **Swap Fees:** A percentage of each transaction is distributed to liquidity providers. * **Protocol Fees:** A portion of swap fees may be retained to support Ferra’s development and the broader ecosystem. * **Gas Fees:** Users are responsible for blockchain transaction costs. Fee structures may be adjusted through decentralized governance. * **Funding and Liquidation Fees:** These fees apply to perpetual trading and may vary over time depending on market conditions and the underlying protocol. * **Performance Fees:** These fees may apply to certain products or features, including the trading terminal, Smart LP, vault strategies, or other yield-generating services. * **Anti-Spam Fees:** A small fee that may be applied to prevent spam or abuse in certain activities, such as daily check-in quests or joining community features. ### 12. Modification or Termination Ferra contributors may: * Modify, upgrade, or shut down the frontend without notice. * Deploy updated smart contracts with or without backward compatibility. * Restrict frontend access for legal, ethical, or technical reasons (e.g., compliance with sanctions).Direct smart contract access or third-party frontends remain unrestricted, as Ferra is permissionless. ### 13. Limitation of Liability To the maximum extent permitted by law, Protocol Contributors are not liable for: * Errors, bugs, or exploits in smart contracts or frontend code. * Loss of funds, private keys, or assets due to user error or external attacks. * Incorrect data display or frontend downtime. * Regulatory or legal actions against users. * Any indirect, incidental, special, punitive, or consequential damages.Your sole remedy is to stop using Ferra. ### 14. Indemnification You agree to indemnify and hold harmless Ferra contributors from claims, losses, damages, or expenses (including legal fees) arising from your: * Violation of these Terms or Privacy Policy. * Misuse of the protocol (e.g., fraud, market manipulation). * Violation of applicable laws or regulations. * Infringement of intellectual property or third-party rights. ### 15. Dispute Resolution As a decentralized protocol, Ferra operates without a single jurisdiction. Disputes should be resolved informally through community governance channels (e.g., forums, DAOs). Formal arbitration may not be feasible due to Ferra's decentralized nature. You waive any right to class action lawsuits or centralized legal proceedings. ### 16. Changes to Terms and Privacy Policy We may update this document periodically via community governance or contributor discretion. Changes are effective upon publication on the frontend or official channels (e.g., Discord, X, GitHub). Continued use of Ferra constitutes acceptance of updates. ### 17. Governing Law As a decentralized protocol, Ferra is not governed by any national legal system. Disputes or interpretations are subject to the principles of decentralized governance and blockchain consensus, not centralized regulatory jurisdiction. ### 18. Security and Audits * Ferra's smart contracts undergo audits by reputable firms, but audits do not guarantee security. * In case of exploits (e.g., the $260M Cetus exploit), Ferra may pause contracts for safety and work with validators to mitigate damage. * You are encouraged to report vulnerabilities via official channels for potential bounties. ### 19. Prohibited Activities You may not: * Engage in market manipulation (e.g., wash trading, pump-and-dump). * Deploy malicious code, viruses, or denial-of-service attacks. * Use Ferra for illegal activities, including money laundering or terrorist financing. * Solicit information from minors or engage in harmful, defamatory, or discriminatory behavior. Violations may result in frontend access restrictions or community governance actions ### 20. Contact For questions, concerns, or vulnerability reports, engage via community governance channels (e.g., Discord, X, GitHub, or forums). Ferra contributors do not provide direct customer support, as the protocol is non-custodial. ***By using Ferra, you acknowledge that you understand, accept, and agree to be bound by these Terms of Use and Privacy Policy in full.*** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ferra.ag/resources/terms-and-policies.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.