Zama: control-plane safety record
1 indexed control-plane surface for Zama, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xA12C…f4f3
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: zama-token-not-upgradeable-s33: ZAMA token 0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3 (Ethereum; not a proxy: EIP-1967 implementation, admin and beacon slots all empty; verified source) …
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Strong · Chain matches or is stronger than the documentation
Each slice is derived only from the pinned records on this page and their controller facts (/api/v1/scorecards.json). A hollow slice is not determined by the published evidence (never a guess); docs-vs-chain parity is uncompared for RPC-observed protocols. How to read it.
Check it live (free)
The pre-flight API re-reads the controller, proxy and capabilities of one contract at the latest block. No key, no wallet. The score rates that single contract, not the whole protocol.
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3"})ZAMA token: not a proxy, no upgrade function
Observed onchain. ZAMA token 0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3 (Ethereum; not a proxy: EIP-1967 implementation, admin and beacon slots all empty; verified source): totalSupply() = 11,391,483,307.90. The runtime code holds no selector of mint(uint256), upgradeTo(address), upgradeToAndCall(address,bytes). This record checks the upgrade claim only: minting is role-gated in the token (documented as staking rewards).
Documented. '**Some contracts cannot be upgraded**: $ZAMA token' (docs.zama.org/protocol/protocol-apps/governance/governance.md); '| Zama Token | [`0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3`]' (docs.zama.org/protocol/protocol-apps/addresses/mainnet/ethereum.md)
cast call 0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3 \ "totalSupply()" \ --block 26452373 --rpc-url "$ETH_RPC_URL" cast block 26452373 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x63bfaa16f0019d8b37e757265d351bd135ad41e6ffa46207284198917123c55d
Embed Live Control-Plane Badge
Show Zama's Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.
[](https://pacta.wtf/protocols/zama/)
<a href="https://pacta.wtf/protocols/zama/"><img src="https://pacta.wtf/badges/zama.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/zama.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/zama.svg (5-minute cache).
Operating Zama? Add Continuous Control-Plane Monitoring
Continuous Control-Plane Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.