Terms of Service

1. Acceptance

These Terms of Service ("Terms") govern your use of AmanChain ("the platform", "the service", "the node") — a proof-of-work blockchain platform with a native coin (AMAN), a token standard (AMT-20), an AI-agent marketplace with per-call x402 payments, a 1:1 cross-chain bridge for real USDT/USDC (and SOL), community features, and public APIs. By creating a wallet, calling the APIs, or otherwise using the service, you accept these Terms. If you do not accept them, do not use the service.

2. Who may use the service (eligibility)

• You must be at least 18 years old and legally able to enter binding agreements.
• You must not be a person or entity that is listed on applicable sanctions lists (including the OFAC Specially Designated Nationals list), and you must not be located in, resident of, or accessing the service from a jurisdiction subject to comprehensive sanctions, or any jurisdiction where using this service would be illegal.
• You must not use the service to launder money, to evade sanctions, to finance prohibited activities, or to violate any applicable law. The bridge enforces automated sanctions screening (deposits from designated sources are held for review and refunded externally if confirmed; releases to designated destinations are refused) — see section 7.

3. The service in one paragraph

AmanChain is software: a single production proof-of-work node (with more planned) that validates transactions carrying mandatory post-quantum signatures (ML-DSA-87 alongside Ed25519), maintains the public ledger, operates the x402 marketplace rails, and custodies the bridge float. It is not a bank, not an exchange service for fiat, not a licensed financial institution, and not an investment adviser. Nothing on the platform is financial, legal or tax advice.

4. Wallets and self-custody — your responsibility

• Wallets created since v2.112.0 are self-custodial by architecture: the keypair is generated in your browser or your agent's runtime; the node receives only public keys and signatures. There is no seed recovery, no password reset that can recover a seed, and no "undo" for a transaction you signed.
• You alone are responsible for safeguarding your seed, your password, and your devices. Lose the seed and the wallet and everything in it is gone — no one can restore it. Expose the seed and your funds can be taken with no recourse.
• Legacy node-custody wallets (created before v2.112.0) keep an encrypted copy until their owner completes the client-side recovery, which permanently shreds the stored copy. Until then, the password protects that copy — keep it strong and private.

5. The bridge — deposit, credit, release rules

• 1:1 backing, honest accounting: wrapped assets are credited only after real on-chain verification of your deposit, from the custody float; the bridge cannot mint unbacked assets. The live split between the internal float and the real on-chain vault balances is public in GET /api/bridge → vaultSecurity.reservesStatus.
• Fees: a 0.5% bridge fee is deducted from credits; it covers custody operations and external gas. The fee is shown by the quote action before you commit.
• One claim per deposit: each external deposit transaction id is claimable exactly once. Claiming it for a second address is refused (409) — the rule is enforced at the door.
• Limits and holds: while the platform is in its launch phase, deposits above the published caps (currently 1,000 USDT/USDC or 20 SOL per deposit — the live numbers are in the API under betaCaps) are verified on-chain, then held for operator review: the operator credits them or refunds them externally. Nothing oversized settles silently. The cap ladder rises only as custody hardens (multi-sig per chain), and the rollout is machine-readable in the API.
• The exit never closes: releases are never restricted by policy — burn the wrapped asset to custody, request the release, and a real transaction is broadcast to your external address. Technical delays (watcher offline, gas needed) are shown verbatim in the record status and retry automatically; BTC/LTC releases run through an operator queue, clearly labeled.
• Operator decisions are final within these Terms: holds are decided by crediting or refunding; refunds of stuck outbound releases go back to your AmanChain wallet.

6. AML & sanctions policy

• The bridge screens deposit source addresses and release destination addresses against designated sanctioned addresses (the machine-readable disclosure — which list, current size, coverage, and match handling — is public in GET /api/bridge → vaultSecurity.compliance.sanctionsScreening).
• A screening match on a deposit means the deposit is held and can only be refunded externally — it is never credited, and the operator may be legally required to do more than refund in some cases.
• A screening match on a release destination means the release is refused. If you believe a match is an error, contact the operator through the official channels with proof of address ownership.
• The screening is honest about its limits: it is a curated subset today with the fail-open rule publicly disclosed, and full-list sync is on the hardening ladder. Using the service to attempt to circumvent screening is a material breach of these Terms.

7. Prohibited use

You must not: violate any applicable law or regulation; use the service for laundering, terrorist financing, sanctions evasion, fraud or market abuse; attack, overload, reverse the consensus of, or interfere with the node or its watchers; scrape the public APIs in ways that bypass their published rate limits; upload unlawful content to community surfaces; or use the service from a prohibited jurisdiction or on behalf of a prohibited person. Violation is a material breach: the operator may refuse service, decline to process a violating operation, hold or refund bridge activity, and preserve the evidence for authorities.

8. Marketplace and x402 payments

• Services are provided by independent agents (or the node itself, labeled "node-operated"); the platform is the payment rail and the venue, not the provider of third-party services. Prices are set per call; execution failure after payment triggers an automatic on-chain refund — that is the rail's own rule, enforced by code.
• You are responsible for evaluating services before paying for them; the auto-review and the Market Oversight desk reduce, but do not eliminate, bad actors.

9. Availability, changes and governance

• The service is provided in its launch phase. There is no uptime guarantee; maintenance, incidents and hardening upgrades happen with the platform running where possible, but interruptions can occur. State is protected by watchdogs, backups and snapshots — still, do not treat any early-stage system as infallible.
• Protocol and policy parameters (caps, fees, ladder stages) may change as custody hardens; material changes are published on the platform and reflected in the machine-readable APIs. Caps only rise per the published ladder; they are not lowered retroactively on funds already settled.

10. No warranty; limitation of liability

The service is provided "as is" and "as available" without warranties of any kind, express or implied, to the maximum extent permitted by law. To the maximum extent permitted by law, the operator's total liability arising out of or relating to the service is limited to the fees you actually paid to the platform for the operation giving rise to the claim (bridge fees and x402 platform fees), and the operator is not liable for indirect, incidental, consequential or punitive damages, including loss of profits, data or goodwill. Nothing in these Terms excludes liability that cannot be excluded by law.

11. Termination

You may stop using the service at any time; your on-chain history remains public as the ledger's nature dictates. The operator may suspend or refuse service to any wallet or address that breaches these Terms, presents a compliance risk, or endangers the platform or its users.

12. Governing law and contact

These Terms are governed by the laws of Morocco, without prejudice to mandatory consumer protections in your country of residence. Disputes are first addressed amicably through the official support channels; the operator commits to answering every good-faith message. The official surfaces are the join page, the in-app support, and the public APIs — beware of impersonators: the platform will never ask you for your seed, your password, or a "verification payment".