ATAMO
ATAMO is a security-focused digital asset protocol built on transparent administrative control, delayed execution, participation infrastructure, and publicly verifiable Ethereum Mainnet contracts.
This website is the official public reference for the ATAMO system. It publishes documentation, contract references, verification guidance, and security information required to independently review the protocol.
ATAMO does not rely on hidden authority or unverifiable claims. Where administrative control exists, it is disclosed. Where protocol claims are made, they are intended to be verifiable through public references, signed release artifacts, and on-chain data.
Protocol Status
Ethereum Mainnet
ATAMO (ATMS)
2-of-3 Safe authorization with Timelock execution
Official reference role
This website functions as the official ATAMO public reference layer.
It should be used together with verified blockchain records, verified contract source code, signed Git tags, signed checksum manifests, and the official repository.
If information conflicts across sources, verified on-chain data, verified contract source code, signed release artifacts, and signed deployment records take precedence.
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 |
Core protocol properties
ATAMO is structured as a controlled protocol with disclosed authority, delayed execution, public verifiability, and separated participation infrastructure.
Transparent administrative control
Sensitive administrative actions are routed through a disclosed Safe multisignature and Timelock execution model rather than hidden direct control.
Delayed execution path
Timelock delays create a review window before sensitive actions are executed on-chain.
Verifiable contract infrastructure
Contract references, proxy addresses, implementation addresses, and verification guidance are published for independent review.
Security-focused operating model
The protocol separates authorization, scheduling, execution, and participation coordination in order to reduce single-actor control risk.
Security model
ATAMO is designed around disclosed administrative authority, structured control layers, deliberate execution delays, and public verification.
The protocol does not present itself as immutable. Instead, it defines what authority exists and how that authority is restricted, delayed, and monitored.
Multisignature authorization
Administrative entry is controlled through a 2-of-3 Safe multisignature structure.
Timelock execution
Sensitive actions follow a delayed execution path before they can take effect.
Public observability
Reviewers can compare documentation, contract references, signed releases, and on-chain behavior.
Protocol architecture
ATAMO uses a layered control model separating authorization, delayed execution, token logic, governance-action records, and participation coordination.
Custodian Safe
2-of-3 multisignature authorization layer
Timelock
Delayed execution and review window
SecureToken
ERC-20 token proxy, token logic, and supply enforcement
TokenActionRecorder
TokenActionRecorder is Safe-only governance action recording infrastructure. It records proposal metadata and Timelock execution parameters for mint, pause, unpause, and upgrade actions.
ATMSParticipationVault
The Participation Vault supports staking, proposal creation, proposal support, execution-link tracking, and penalty-funded rewards. It does not directly execute privileged token governance actions.
Official token reference
The official ATAMO token on Ethereum Mainnet is the SecureToken proxy:
0x38604c42c16e29BbFbc5479668453f18cB6cf335
Users, exchanges, wallets, explorers, analytics providers, and integrations should use the proxy address for token interaction. Implementation contracts are for verification and audit review, not as normal user-facing token addresses.
Release verification
ATAMO v1.0.0 release verification is based on a signed Git tag and a signed SHA256 checksum manifest.
Canonical release tag:
v1.0.0
Release directory:
releases/v1.0.0/
Primary release verification files:
- deployment-manifest.mainnet.json
- deployment-records-full.mainnet.json
- ATAMO_DEPLOYMENT_STATEMENT_mainnet_2026-05-16.txt
- SHA256SUMS
- SHA256SUMS.asc
- ATAMO_RELEASE_PGP_PUBLIC_KEY.asc
Release verification should confirm the signed Git tag, the PGP signature on SHA256SUMS, and the hashes of all listed release artifacts.
Reviewer path
Contracts
Official deployment references, proxy and implementation addresses, and contract roles.
View contractsProtocol Model
Administrative architecture, execution flow, Timelock rules, and upgrade structure.
View protocol modelAdmin Powers
Plain-English disclosure of what authority exists, what does not exist, and what limits apply.
View admin powersVerification
How to validate official references, releases, and contract authenticity.
Open verification guideRelease Verification
Signed Git tag, PGP fingerprint, SHA256SUMS, and release artifact verification.
Release verificationSecurity
Security principles, disclosure channel, assumptions, and reviewer expectations.
Security policy