Terms of Use

1. Acceptance, eligibility, and scope

1.1 By using an interactive feature after these Terms have been presented to you, you agree to these Terms and any applicable feature-specific terms. Read the Risk Disclosure before committing assets. The Privacy Policy explains our handling of personal information; accepting these Terms is not blanket consent to optional data processing.

1.2 You must be at least 18 and have reached the age of legal majority where you live to create an account or participate in financial, staking, or bonded contribution features. If you act for an organization, you represent that you have authority to bind it and to use the relevant wallet and assets.

1.3 Do not use a feature where its provision or your participation is prohibited, where required authorization has not been obtained, or where you fail its stated eligibility requirements. Do not evade geographic, sanctions, onboarding, wallet, or other access restrictions. Technical accessibility is not a determination of legal eligibility.

1.4 Availability depends on the particular network, deployment, release, market, and operational state. Devnet and other test environments may use test tokens, seeded observations, and demonstration activity. These do not establish a claim to real money, production tokens, an airdrop, compensation, or migration to a later deployment.

2. No advice or assurance of returns

2.1 Amoeba does not provide personalized investment, trading, legal, tax, accounting, procurement, or risk-management advice through these services. Benchmarks, charts, examples, model outputs, and transaction previews are tools and information, not recommendations tailored to your circumstances.

2.2 You make your own decisions about participation, sizing, counterparties, and suitability. A bounded payoff, a reserve calculation, or the absence of routine mark-to-market liquidation does not establish that a position is safe, profitable, liquid, or an effective hedge.

2.3 No displayed return, quoted premium, bounty estimate, staking exchange rate, or historical result guarantees future income. A software test, mathematical verification, reproducible build, or deployment receipt is not regulatory approval or a guarantee against loss.

3. Markets, contracts, and writer participation

3.1 Current synthetic products reference defined benchmarks such as RAMX and NANDX. They do not transfer ownership of memory, storage devices, inventory, warehouse receipts, manufacturing capacity, or a producer's future output. Any future physical-delivery or financing product would require its own terms and explicit availability.

3.2 Monthly maturities do not necessarily mean one-month contracts. The current design uses a rolling three-month ladder, adding a new far-month contract through each monthly source-selection cycle. The exact listing and expiry timestamps, rather than a maturity label alone, determine a series' term.

3.3 Before acting, review the network, program and token identities, benchmark and methodology version, expiry, direction, strike, participation and unit scaling, payout cap, quantity, premium, fees, settlement asset, and applicable execution limits. A quoted maximum payout is gross settlement proceeds, not maximum net profit.

3.4 A buyer of a capped option can lose the entire premium paid, together with applicable transaction and service costs. Writers and Flat holders can lose some or all of their committed capital. These descriptions concern the intended contractual payoff; they do not limit losses caused by compromised credentials, excessive approvals, software failure, or other risks described on the Risk Disclosure page.

3.5 The writer-liquidity design offers backed options through the native Amoeba DLMM, alongside trading of existing options. Issuance and writer-funded purchases remain subject to the applicable pricing, collateral, risk-policy, oracle-security, expiry, and spending conditions. Posting liquidity does not guarantee a sale or an immediate premium. Writer-funded buybacks are limited by the frozen policy and do not guarantee an exit for option holders. Funds previously committed to an auction remain subject to that auction's applicable execution, refund, and settlement conditions.

3.6 A writer sleeve pools settlement assets for eligible series sharing the applicable settlement group. Writer principal and locked primary premiums contribute to that pool. Required collateral is based on the aggregate maximum external payout under the implemented reserve rules, rather than an assumption that every call and put simultaneously pays its individual maximum. This pooling does not protect writer principal from loss.

3.7 Flat represents an economic interest in the relevant sleeve's residual assets under its rules. It is not equity in the Amoeba operator and does not itself convey protocol-governance, pricing, or policy-control rights. The sleeve's book may change through permitted operations within its applicable policy. Transferability does not guarantee a buyer, a quoted market, or redemption at the original deposit amount.

3.8 Funding-stage withdrawals are available only when the program's conditions are satisfied. Once a sleeve is active, ordinary on-demand withdrawal is not available. A permitted early close requires the specified Flat amount and proportional option-claim basket, together with the program's deadlines, amount limits, reserve, and other checks. Acquiring and delivering that basket can require separate transactions. Locked primary premiums are not distributed to an early exiter through this path. Final residual redemption follows the settlement lifecycle.

3.9 The deployed V1 DLMM uses managed liquidity. The presence of a liquidity interface does not mean unrestricted public liquidity provision is available. Neither Amoeba nor a liquidity manager is obliged by these Terms to maintain a continuous quote, repurchase a position, or support a particular market price.

3.10 Premiums and execution prices are distinct from protocol fees, network costs, account costs, and any third-party charges. Review the applicable disclosures and signed transaction. Unfilled orders, refunds, claim recovery, and cancellation follow the relevant workflow; they are not necessarily immediate. A failed transaction may still incur network costs.

4. Oracle, settlement, and controlling records

4.1 Each market is tied to a defined product, source structure, and settlement methodology. Product basket weights and the treatment of individual observation sources are different concepts. In the current oracle, admitted sources within a governed SKU bucket have equal standing for deterministic median aggregation; backing cash does not buy a larger percentage contribution to the index.

4.2 The oracle measures an accepted source's movement relative to its own opening state. It does not represent that unrelated retail listings, distributor prices, assessments, and other price environments clear at one universal raw price. Source identity, product specification, price basis, timing, and evidence eligibility matter.

4.3 The current process includes source selection, coverage checks, challenges, opening observations, ongoing updates, and final settlement. A source-selection or coverage delay can postpone effective listing without extending the series' expiry. The applicable rules determine admissible observations, aggregation, unchanged-source carry-forward, lookback extensions, and emergency outcomes.

4.4 A chart, live index preview, source update, and finalized settlement are not interchangeable. Settlement depends on the required observation and dispute processes, authorized publication, and on-chain acceptance. Eligibility to settle at a particular time does not guarantee that publication, redemption, or payment will occur at that time.

4.5 For transaction execution, verify the applicable deployed program and finalized records. A stale interface cannot change the transaction that was signed or the state accepted by the program. This operational distinction does not waive mandatory legal rights, excuse a misleading representation, or make software defects legally binding simply because they occurred on-chain.

4.6 Product-specific terms and versioned rules control their stated subject matter where they validly supplement these Terms. These Terms do not grant an administrator a power to rewrite an existing contract, source recipe, or settlement record that the applicable mechanism does not provide. Upgrade and emergency powers that do exist carry separate risks.

5. Oracle contributions, staking, and rewards

5.1 Submit only source definitions, values, archive references, explanations, and other material permitted by the current workflow, that you have the right to provide, and that you reasonably believe is accurate. A public URL, screenshot, or assertion is not automatically acceptable settlement evidence.

5.2 Do not conceal a material difference in SKU, variant, quantity tier, currency, region, seller, condition, timestamp, tax, shipping, or the field being measured. Do not submit fabricated evidence, unauthorized personal information, confidential material, or content obtained through unlawful access.

5.3 Source backing, listing bonds, update bonds, challenge bonds, and rewards have distinct rules. Funds may remain committed until the applicable claim, challenge, or refund lifecycle is complete. An incorrect claim, failed challenge, missed requirement, or adverse dispute outcome can cause loss of committed assets or reward eligibility.

5.4 Rewards depend on the applicable budget, funding, deadlines, finality, and eligibility rules. A displayed task or estimate is not guaranteed income, employment, a wage, or a promise that a treasury will always have funds. Do not assume that repeating an unchanged source earns a reward.

5.5 AMBA and sAMBA are distinct from option collateral and Flat. sAMBA represents a share of the applicable AMBA staking pool. Activation, cancellation, unstaking, redemption, and emergency voting follow their own rules and may involve waiting periods, output limits, and temporary restrictions.

5.6 Current oracle emergency voting uses escrowed sAMBA. A decisive outcome can redistribute losing and unrevealed commitments; specified failed-consensus outcomes instead provide for refunds. Ordinary software-upgrade council governance is a different mechanism. Holding AMBA, sAMBA, or Flat does not by itself grant a council seat.

5.7 By submitting material, you grant Amoeba a non-exclusive, worldwide, royalty-free permission, limited to the rights you possess, to process, reproduce, store, and display it as reasonably necessary to operate the relevant feature, resolve disputes, maintain lawful audit records, and protect the service. You do not transfer ownership of your material or grant rights you do not hold in a third party's content. Personal information remains subject to the Privacy Policy and applicable law.

6. Accounts, wallets, APIs, and transactions

6.1 Keep your account information accurate and protect your devices, wallet access, authentication methods, and credentials. External-wallet sign-in and embedded-wallet sign-in have different recovery arrangements. Amoeba does not guarantee recovery of lost wallet access or reversal of a finalized blockchain transaction.

6.2 Review the purpose and effect of every message or transaction you sign. A login signature is different from authorization to transfer assets. Check token approvals, destinations, amounts, network, expiry, minimum output, and any additional instructions before approval.

6.3 Preparing a transaction, signing it, submitting it, and obtaining finality are separate events. Prepared operations can expire or become invalid when deployment identity, governance state, market conditions, or account state changes. Do not repeatedly submit an operation without checking whether an earlier attempt succeeded.

6.4 The website, CLI, SDK, and APIs can expose different capabilities. Software support for an operation does not establish permission to execute it. Use supported releases and authorized interfaces; automated clients and agents must comply with these Terms, applicable limits, and the same eligibility and transaction requirements as other users.

6.5 Wallet, identity, blockchain, RPC, storage, and payment providers may impose separate terms. A funding integration, including an onramp, is available only when enabled and supported for the selected environment. Its presence in source code is not a promise of approval, availability, or a successful fiat-to-token purchase.

7. Prohibited use and permitted research

7.1 Do not use the services to violate law, evade restrictions, manipulate a benchmark or market, fabricate activity, misappropriate funds, abuse rewards, interfere with settlement, or deceive other participants.

7.2 Do not bypass access controls, obtain unauthorized data, distribute malware, overload infrastructure, or execute an exploit against accounts or assets without authorization. Report suspected vulnerabilities through our support contact and avoid exposing private information in a public report.

7.3 These restrictions do not override rights provided by applicable law or an open-source license. Lawful inspection, independent analysis, permitted automation, and non-disruptive security research are not prohibited merely because they examine how the system works. This paragraph does not authorize access to protected systems or exploitation of live funds.

8. Availability, governance, and changes

8.1 We may change or restrict hosted features for maintenance, security, legal compliance, or product reasons. Separate on-chain governance, pause, upgrade, and recovery mechanisms may affect what operations are possible. Restricting a website does not necessarily stop independent blockchain access, and keeping a website online does not guarantee that a transaction can execute.

8.2 Outages or restrictions can prevent trading, contribution, voting, claims, or withdrawals while deadlines continue to run. We do not guarantee uninterrupted operation, continued listing, timely third-party responses, or successful recovery after an incident.

8.3 We may revise these Terms prospectively. The updated page will identify its revision date, and material changes will receive notice appropriate to the circumstances and any consent required by law. A website revision does not, by itself, retroactively alter an executed transaction or a frozen product term. Stop entering new commitments if you do not accept applicable revised terms; existing obligations and mandatory rights remain subject to their governing rules.

9. Intellectual property and software licenses

9.1 Amoeba and its licensors retain rights in their respective branding, interfaces, documentation, software, and other protected materials. Users and third parties retain rights in their own material. Public visibility is not a transfer of ownership or an endorsement by a source publisher.

9.2 Where a software component is distributed under an open-source or other separate license, that license governs the rights it grants. These Terms do not revoke those rights. Access to hosted infrastructure, restricted data, and the Amoeba name or logo is not automatically included in a software license.

9.3 We may use voluntarily supplied product feedback to improve the services without an obligation to pay for it, unless a separate agreement provides otherwise. This does not override confidentiality commitments, personal-data rights, or third-party intellectual-property rights.

10. Disclaimers and limits of liability

10.1 To the extent permitted by applicable law, the services and associated information are provided as available and without warranties of uninterrupted operation, accuracy, fitness for a particular purpose, or a particular trading or economic result. No disclaimer creates an exemption from an obligation that cannot lawfully be excluded.

10.2 We do not guarantee a correct source observation, profitable strategy, stable token value, continuous liquidity, successful claim, timely settlement, or the security of every dependency. Review the Risk Disclosure for the material ways losses can occur.

10.3 To the extent permitted by applicable law, we exclude liability for indirect, incidental, special, consequential, exemplary, and punitive damages, including consequential lost profits, opportunities, or data. Responsibility for direct losses and any other recoverable loss remains subject to applicable law and any valid feature-specific agreement.

10.4 Nothing in these Terms excludes or limits liability for fraud, intentional misconduct, gross negligence where it cannot lawfully be excluded, or any other liability or consumer right that applicable law does not permit us to exclude or limit. A risk acknowledgment does not waive a right that cannot legally be waived.

11. Additional terms and general provisions

11.1 A specific market, writer sleeve, auction, contribution program, API, staking feature, or third-party service may have additional terms. Their scope and applicable version must be identified. In a valid conflict, the more specific terms govern that feature, subject to mandatory law and Section 4.

11.2 If a provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law. A failure to enforce a provision on one occasion is not a permanent waiver. Provisions that by their nature concern existing obligations, lawful records, intellectual property, or liability continue after you stop using the service.

12. Contact and notices

12.1 For questions about these Terms or a suspected service or security issue, contact [email protected].

12.2 Identify the relevant network, market, transaction, or account issue without sending a private key, recovery phrase, password, or active authentication token. Contacting support does not suspend a blockchain deadline or guarantee that an irreversible action can be undone.