Eligibility Requirements

Eligibility Criteria

As stated in clause 3.3(a) of the Terms of Use: “You represent and warrant that you (i) have the necessary technical expertise and ability to review and evaluate the security, integrity, and operation of the Protocol and your Digital Wallet; (ii) have the knowledge, experience, understanding, professional advice and information to make your own evaluation of the merits, risks, and applicable compliance requirements under applicable laws of any use of your Digital Wallet and the Protocol; (iii) know, understand, and accept the risks associated with your Digital Wallet and the Protocol; and (iv) accept the risks associated with blockchain technology generally, and are responsible for conducting your own independent analysis of the risks specific to your use of the Services”.

In line with this principle, we have defined a baseline set of eligibility criteria to ensure that investors engaging with our sophisticated products possess a fundamental understanding of their technical features, associated risks, and operational processes. The following represent the minimum requirements, and additional criteria may apply depending on the specific product or market conditions.

Technical and Operational Proficiency

  • Proficient in using non-custodial wallets (e.g., MetaMask, Rabby, Safe etc.).

  • Capable of safely storing and managing private keys or seed phrases.

  • Experienced with Layer 2 networks or alternative blockchain ecosystems (e.g., Arbitrum, Optimism, Base, Berachain etc.).

  • Skilled in approving, signing, and revoking on-chain transactions.

  • Familiar with interactions on decentralized exchanges (DEXs), aggregators, or DeFi aggregators.

  • Understands basic decentralized finance (DeFi) concepts such as LP tokens, slippage, gas fees, and transaction costs.

  • Knowledgeable about delta-neutral strategies, differences between APY and APR, and implications of impermanent loss.

  • Familiar with risks associated with smart contracts, oracles, and potential protocol-level vulnerabilities.

  • Understands collateralization methods, liquidation triggers, and redemption mechanisms.

  • Regularly reviews protocol documentation prior to interacting with smart contracts.

  • Consistently verifies contract addresses and protocol user interfaces (UIs) before initiating transactions.

  • Utilizes on-chain analytics tools (e.g., DeBank, Zapper, Arkham) to monitor and manage positions.

  • Has awareness and experience in managing tax implications of crypto investments.

  • Demonstrates capability to assess and evaluate third-party audits and security reports.

  • Uses hardware wallets or advanced security measures to enhance asset protection.

  • Comfortable navigating market volatility and managing emotional decision-making during adverse market conditions.

  • Must be of legal age to enter into financial agreements. (typically 18 or older, depending on local jurisdiction)

  • Must comply with all applicable local regulations and laws governing cryptocurrency and financial products.

  • Not a resident or national of jurisdictions explicitly restricted by Ember Protocol due to regulatory or compliance constraints (including but not limited to jurisdictions subject to international sanctions, regulatory prohibitions, or financial restrictions).

  • Acknowledges responsibility to verify jurisdiction-specific legal constraints regarding cryptocurrency investments.

  • Confirms that the source of funds used for investment is legitimate and not linked to illicit activities.

Restricted Jurisdictions

Not for the distribution to any U.S. Person or any person or address in the United States. Ember Protocol does not sell its tokens to U.S. Persons or for the account or benefit of U.S. Persons, and tokens are not marketed or solicited in the U.S. or in any other prohibited jurisdiction. Further the offering is restricted in the U.K. China and sanctioned countries. For a full list of prohibited and restricted countries and review of legal documentation, please visit Ember Gitbook Docs.

Last updated