ATAMO coin logo ATAMO

Documentation

This section provides the structured documentation of the ATAMO system, including protocol architecture, administrative model, verification guidance, participation infrastructure, release verification, and public references.

Documentation role

ATAMO documentation explains how the system is structured and how it should be verified.

Documentation is not the source of truth by itself. Verified smart contracts, on-chain data, signed Git tags, signed checksum manifests, and official release artifacts define the actual system state.

Documentation should be used together with those sources to understand and validate the protocol.

1. Project overview

ATAMO is an Ethereum Mainnet ERC-20 infrastructure system built around disclosed administrative control, Safe multisig authorization, Timelock execution, participation infrastructure, and verifiable public references.

Core structure

  • 2-of-3 Safe multisignature governance root
  • Timelock-delayed execution of sensitive actions
  • UUPS upgradeable SecureToken proxy architecture
  • TokenActionRecorder for Safe-only governance action records
  • ATMSParticipationVault for staking, proposal support, and rewards
  • signed Git tag and signed release checksum manifest
  • public contract references and verification guidance

Design priorities

  • security-focused administrative model
  • deliberate execution of critical actions
  • public verifiability of contracts and references
  • transparent long-term protocol control
  • clear separation between participation and execution authority
  • cryptographically verifiable release artifacts

2. System layers

ATAMO separates authorization, delayed execution, token logic, action recording, and participation coordination into distinct layers.

Custodian Safe

2-of-3 multisignature authorization layer for sensitive protocol actions.

Timelock

Delayed execution layer providing a review window before privileged actions are executed.

SecureToken

The ATAMO ERC-20 token proxy and implementation enforcing transfer, pause, mint, upgrade, and supply-cap logic.

TokenActionRecorder

Safe-only governance action recorder for mint, pause, unpause, and upgrade operation metadata.

Participation Vault

Staking, proposal registry, proposal support, participation rights, and penalty-funded reward infrastructure.

3. Official Ethereum Mainnet addresses

Component Address Role
ATAMO Custodian Safe 0xe3b72bdb899364ce86949746D31CCba5f384b949 2-of-3 multisignature governance root
Timelock Proxy 0x2778BC96422AeD7D7Ac7CE21372Aa42c525A86B8 Delayed governance execution layer
SecureToken Proxy 0x38604c42c16e29BbFbc5479668453f18cB6cf335 Canonical user-facing ATMS ERC-20 token
ATMSParticipationVault 0x01273Ef57CE09C4Aa615E3bd95eF2b9DD54fd0E4 Staking, proposal, support, and rewards layer
TokenActionRecorder 0xAA7152784479Ed53147A12514602968327c9965E Governance-action metadata recorder

4. How to use this documentation

For users

  • verify the official token proxy before interacting
  • use the verification guide to confirm authenticity
  • check contract addresses against official deployment references
  • verify signed Git tags and signed checksum manifests when relying on release files
  • avoid relying on third-party sources without cross-checking

For auditors and exchanges

  • validate contract addresses and roles using the contracts page
  • review the protocol model for execution and governance structure
  • confirm administrative controls using the admin powers page
  • verify releases and source code against signed release artifacts
  • review the Participation Vault separately from token execution authority
  • confirm the canonical token address is the SecureToken proxy

5. Documentation map

Contracts

Official deployment references and contract roles.

View contracts

Protocol Model

Administrative architecture, Safe control, Timelock execution, and upgrade flow.

Protocol model

Admin Powers

Disclosure of administrative authority and restrictions.

Admin powers

Verification

How to validate contracts, releases, addresses, and references.

Verification guide

Release Verification

Signed Git tag, PGP key, SHA256SUMS, and release artifact verification.

Release verification

Security

Security principles, disclosure process, assumptions, and reviewer expectations.

Security policy

Tokenomics

Supply model, distribution, issuance rules, and launch transparency.

Tokenomics

6. Official references

Primary release verification files

  • releases/v1.0.0/deployment-manifest.mainnet.json
  • releases/v1.0.0/deployment-records-full.mainnet.json
  • releases/v1.0.0/ATAMO_DEPLOYMENT_STATEMENT_mainnet_2026-05-16.txt
  • releases/v1.0.0/SHA256SUMS
  • releases/v1.0.0/SHA256SUMS.asc
  • releases/v1.0.0/ATAMO_RELEASE_PGP_PUBLIC_KEY.asc
  • docs/DEPLOYMENT.md
  • docs/VERIFYING.md

Security and operations files

  • SECURITY.md
  • docs/SECURITY_MODEL.md
  • docs/THREAT_MODEL.md
  • docs/PROTOCOL_INVARIANTS.md
  • docs/MONITORING.md
  • docs/RUNBOOK.md
ATAMO should be evaluated using verified contracts, signed Git tags, signed checksum manifests, public documentation, release artifacts, and on-chain behavior together rather than relying on any single source.

Official Links

Community

𝕏 💬