Admin Powers
This page defines which administrative powers exist in the ATAMO system, which powers do not exist in the current token logic, and which hard limits restrict administrative authority.
ATAMO does not present itself as immutable. Where administrative authority exists, it is disclosed clearly and paired with structural restrictions.
Administrative Control Summary
Available only through Safe-approved Timelock execution and restricted by the hard supply cap.
Available only through Timelock-controlled execution.
Available through delayed approval flow and Timelock execution.
Not present in current token logic.
1. Official administrative addresses
| Component | Address | Administrative role |
|---|---|---|
| ATAMO Custodian Safe | 0xe3b72bdb899364ce86949746D31CCba5f384b949 | 2-of-3 multisignature governance root |
| Timelock Proxy | 0x2778BC96422AeD7D7Ac7CE21372Aa42c525A86B8 | Delayed execution layer for privileged actions |
| SecureToken Proxy | 0x38604c42c16e29BbFbc5479668453f18cB6cf335 | Canonical user-facing ATMS token proxy |
| SecureToken Implementation | 0xD0E06380aF1927c5d929625406d7E9896a80C09c | Current token logic implementation |
2. Administrative powers overview
| Question | Answer | Enforced meaning |
|---|---|---|
| Can admins mint tokens? | Yes | Minting exists only through the Safe → Timelock execution path and cannot exceed the hard maximum supply. |
| Can admins pause the token? | Yes | Pause and unpause authority exists, but execution follows the Timelock path rather than instant direct wallet action. |
| Can admins upgrade token logic? | Yes | The token uses an upgradeable architecture with delayed approval flow and Timelock-controlled execution. |
| Can admins blacklist wallets? | No | No wallet blacklist function exists in the current token logic. |
| Can admins set transfer taxes? | No | The token contract does not include buy-tax, sell-tax, or transfer-tax controls. |
| Can admins trap sellers through token-tax logic? | No | No token-tax mechanism exists to impose punitive sell fees or seller traps through the current token logic. |
| Can admins exceed maximum supply? | No | The token contract enforces the supply cap during mint execution and rejects minting above that limit. |
3. Detailed administrative controls
Minting authority
ATAMO includes a mint function, but minting is not available as arbitrary public access and is not presented as a direct personal-wallet power.
Mint execution is restricted to the Safe-approved Timelock path.
The token contract enforces a hard maximum supply of 200,000,000 ATMS. Minting cannot increase supply above this limit through the defined execution path.
Pause authority
The protocol includes pause and unpause functionality as an emergency control mechanism.
Pause authority exists, but it is restricted to Timelock-controlled execution rather than unrestricted instant action.
This means pause control is disclosed as real authority, but not as a hidden or immediate admin shortcut.
Upgrade authority
ATAMO uses an upgradeable architecture. This means logic changes remain possible through the defined governance and Timelock process.
Upgrade authority is not the same as immutability, and it is not hidden. It exists and is disclosed directly.
Upgrades require delayed approval flow and Timelock-controlled execution rather than instant replacement through a single direct wallet action.
Blacklist authority
The token logic does not include a wallet blacklist mechanism.
No function exists in the current token model for targeting individual wallets and blocking them through blacklist controls.
Tax authority
The token contract does not include buy-tax, sell-tax, or transfer-fee controls.
This means the current token logic does not provide a built-in admin path for introducing token-level trading taxes.
Sell-trap clarification
Some unsafe token designs use punitive sell taxes, hidden fee switches, or specialized transfer restrictions to trap sellers after launch.
The ATAMO token logic does not include that type of token-tax trap mechanism.
This should be understood separately from pause authority. “No sell-tax trap” does not mean “no administrative controls exist.”
Supply-cap enforcement
The maximum supply is enforced by contract logic during mint execution.
Administrative authority does not override the cap through the defined mint path.
4. Structural limits on administrative authority
ATAMO does not claim that no administrative power exists. Instead, the system defines administrative authority and restricts it through structure.
Multisignature entry
Sensitive actions enter the system through a Safe multisignature authority rather than a single operator key.
Timelock delay
Administrative actions are routed through Timelock scheduling and cannot execute instantly through the normal governance path.
On-chain observability
Scheduled actions remain visible on-chain before execution, allowing public review and monitoring.
The ATAMO model therefore relies on disclosed authority, delayed execution, and public observability rather than pretending administrative control does not exist.
5. Upgrade authority clarification
Because ATAMO uses an upgradeable architecture, upgrade authority is one of the most important reviewer questions.
The correct interpretation is: upgrades remain possible, but they are not presented as an unrestricted instant admin override.
Upgrade control properties
- upgrades require the defined approval flow
- upgrades require Timelock-controlled execution
- upgrades are delayed rather than instant
- upgrade activity remains observable before execution
- upgradeability is disclosed openly as a controlled governance power
6. Release verification
ATAMO v1.0.0 release verification is based on a signed Git tag and a signed SHA256 checksum manifest.
- 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
7. Reviewer guidance
What this page answers
This page answers the direct reviewer question: What can admins still do, and what prevents abuse of those powers?
How to review it
This page should be read together with verified contract source code, deployment addresses, protocol-model documentation, tokenomics documentation, signed release artifacts, and public verification references.
8. Transparency principle
ATAMO is intended to be presented honestly. Where authority exists, it is disclosed. Where hard limits exist, they should be contract-verifiable. Plain-English disclosure is part of the project's transparency and security model.