ATAMO coin logo ATAMO

Contracts

This page is the official public registry of ATAMO mainnet contract addresses and verification references. All addresses listed here should be validated against verified blockchain records, signed release artifacts, and official repository references before interaction.

Registry principle

This page defines the official ATAMO contract registry for Ethereum Mainnet.

Contract interaction should rely only on addresses published through official ATAMO references and confirmed through public blockchain verification.

If any address conflicts with verified explorer data, signed release artifacts, deployment records, or the official repository, it should be treated as untrusted until resolved.

1. Official deployment registry

The addresses below are the official ATAMO Ethereum Mainnet deployment references. Reviewers should validate each entry against explorer verification, repository references, and signed release artifacts.

ATAMO Token

Role Canonical user-facing ERC-20 token proxy
Token Proxy
0x38604c42c16e29BbFbc5479668453f18cB6cf335 View on Etherscan
Token Implementation
0xD0E06380aF1927c5d929625406d7E9896a80C09c View on Etherscan
Token Name ATAMO
Token Symbol ATMS
Decimals 18
Max Supply 200,000,000 ATMS
Network Ethereum Mainnet

Timelock

Role Delayed execution layer for sensitive administrative actions
Timelock Proxy
0x2778BC96422AeD7D7Ac7CE21372Aa42c525A86B8 View on Etherscan
Timelock Implementation
0xb0d8dc6a08Cb4F93a795c53867ac990C8ce4B0E0 View on Etherscan
Minimum Delay 2 days / 172800 seconds
Grace Period 60 days / 5184000 seconds
Owner ATAMO Custodian Safe

Custodian Safe

Role Multisignature authorization entry point for sensitive protocol actions
Multisig Safe
0xe3b72bdb899364ce86949746D31CCba5f384b949 View on Etherscan
Safe Interface
Open in Safe
Threshold 2 of 3
Network Ethereum Mainnet

TokenActionRecorder

Role Safe-only governance action recorder for mint, pause, unpause, and upgrade proposal metadata
Contract Address
0xAA7152784479Ed53147A12514602968327c9965E View on Etherscan
Timelock 0x2778BC96422AeD7D7Ac7CE21372Aa42c525A86B8
Safe 0xe3b72bdb899364ce86949746D31CCba5f384b949
Interaction note Governance metadata infrastructure only; not the primary user-facing token address

ATMS Participation Vault

Role Participation, staking, proposal coordination, and penalty-funded reward distribution contract
Vault Contract
0x01273Ef57CE09C4Aa615E3bd95eF2b9DD54fd0E4 View on Etherscan
Token 0x38604c42c16e29BbFbc5479668453f18cB6cf335
Controller
0xe3b72bdb899364ce86949746D31CCba5f384b949 View on Etherscan
Minimum Stake 50,000 ATMS
Support Threshold 100,000 ATMS
Reward Eligibility Age 30 days
Max Active Stake Lots 5
Network Ethereum Mainnet

2. Verification references

3. Reviewer guidance

How users should verify

Users should verify the token proxy address, compare it with the official contract references, confirm explorer verification, and avoid relying on screenshots, social posts, or copied addresses from untrusted sources.

How exchanges and auditors should verify

Exchanges and auditors should validate proxy and implementation addresses, Timelock configuration, Safe configuration, repository references, release provenance, signed Git tag verification, and signed checksum manifest integrity.

Verification rule

If an address, contract role, or deployment reference does not match across the official site, verified blockchain records, signed release artifacts, and the official repository, interaction should stop until the mismatch is resolved.

4. Interaction guidance

  • Use the SecureToken proxy address for primary token interaction
  • Use implementation addresses for code verification and audit review, not as default user interaction targets
  • Treat TokenActionRecorder and Timelock contracts as protocol infrastructure, not as standard token entry points
  • Confirm Safe and Timelock references before evaluating administrative control claims
  • Use the Participation Vault only for staking, proposal, support, and reward-related interactions
  • Verify signed release artifacts before relying on downloaded deployment records

5. Deployment provenance

Deployment provenance should be validated through the official repository, signed Git tag, deployment manifest, full deployment records, deployment statement, checksum manifest, and signed checksum manifest.

These references exist to allow independent verification that published addresses and release data are consistent across official sources.

Recommended verification commands

git tag -v v1.0.0

gpg --verify releases/v1.0.0/SHA256SUMS.asc releases/v1.0.0/SHA256SUMS

sha256sum -c releases/v1.0.0/SHA256SUMS

Always compare contract addresses and deployment references against verified blockchain records, signed release artifacts, and the official ATAMO repository before interaction.

Official Links

Community

𝕏 💬