Loading…

ATA Coin

Auditable Trust Architecture

A fixed-supply digital asset on Base. Every promise it makes is enforced by code anyone can verify — not by trusting the team.

Trust guarantees

These six are properties of the deployed bytecode, not policies:

  1. The supply can never grow. Exactly 1,000,000,000 ATA exist; there is no mint function in the contract.
  2. Nobody can freeze, pause, or censor transfers. Those functions don't exist, and a test in the repository fails if anyone ever adds one.
  3. The deployer never holds the supply. 100% is minted atomically at deployment, straight to vesting contracts and multisigs.
  4. The founder cannot sell early. The 10% founder allocation sits in a public vesting contract: nothing withdrawable for 12 months, fully vested only at year 5.
  5. The treasury cannot be dumped. Half the supply (50%) vests linearly over 4 years to a disclosed multisig.
  6. The community fund streams — it never sits. The 25% community allocation releases linearly over 3 years; nobody, including its own multisig, can move it faster.

The consequence of the six: 85% of the supply is locked in on-chain vesting streams that nobody — founder included — can accelerate. The remaining 15% is different, and this page says so plainly rather than rounding it up to a stronger claim.

One launch commitment — the liquidity lock

The 15% liquidity allocation is minted liquid so it can seed the launch DEX pool. Pairing it with ETH and locking or burning the LP tokens is a required launch step (LAUNCH.md, Phase 5), not a property of the bytecode. Until the lock transaction hash is committed to the repository and shown on this page, that float is held by — and movable by — the disclosed Treasury Safe, which is founder-controlled at launch (TREASURY-POLICY.md). Verify the lock happened; don't take this page's word for it.

This website is part of the same discipline: it is a static page with no backend, no cookies, no analytics, no external scripts, and no wallet connection — its content-security policy only permits reading public blockchain RPC endpoints. The source of this page is in the repository.

Live on-chain state

Tokenomics

The allocation below is 100% of the supply — there are no hidden allocations, no pre-sales, and no side deals. It is defined in a single configuration file consumed by both the deployment and the test suite, and rendered here from the same data.

AllocationShareAmountCustodyLock-up

Vesting timeline

Vesting is enforced by on-chain contracts. Withdrawals before the cliff are impossible; the schedule cannot be accelerated by anyone, including the beneficiary. Full details in TOKENOMICS.md.

Verify it yourself

Don't take this page's word for anything. Every claim above can be checked in a few minutes:

  1. Open the token contract on Basescan's Read Contract tab. Call totalSupply() — it returns 1,000,000,000 × 1018 and can never change.
  2. Look at the contract's function list. There is no mint, no pause, no blacklist, no owner. What isn't there cannot be abused.
  3. Check the token's holder list. It matches the allocation table above, and the deployer holds zero.
  4. Open a vesting wallet and read cliff(), end() and releasable(token) — the lock-ups above are live on-chain state, not promises.
  5. The source code of every contract is published and verified on the explorer, and the repository history shows how it was built and tested.

Using ATA

ATA is a standard ERC-20 token. It works in the wallet you already have — MetaMask, Coinbase Wallet, Rabby, Ledger, Trezor — with no special software. There is deliberately no "ATA wallet": custom wallets concentrate risk, and the standard is the feature.

To see ATA in your wallet, add the contract address published on this page as a custom token, on the network shown in the badge above. Only addresses published here and in the repository README are real — anyone can deploy a fake token with the same name.

For AI assistants, the repository ships a read-only MCP server that answers questions about supply, vesting, and treasury state from live chain data.