Katana: control-plane safety record
1 indexed control-plane surface for Katana, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xd512…C8C4
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-5Evidence: katana-admin-multisig-3-of-5-s37: … Admin multisig address, next to the 3-of-5 statement): a Safe, getThreshold() …
- 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=0xd512543315c95506E4209805b888414EEF15C8C4"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xd512543315c95506E4209805b888414EEF15C8C4"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xd512543315c95506E4209805b888414EEF15C8C4"})Katana Admin multisig (Ethereum): 3-of-5 Safe (docs: 3-of-5)
Observed onchain. Katana Admin 0xd512543315c95506E4209805b888414EEF15C8C4 (Ethereum; the governance page names it as the Admin multisig address, next to the 3-of-5 statement): a Safe, getThreshold() = 3 of getOwners() = 5; guard slot empty; getModulesPaginated() lists no module. The same page says upgrades proposed by the Admin enter a 10-day timelock; that timelock is not identified here (no Katana-specific timelock is readable without event logs), so this record compares only the documented quorum.
Documented. '**3-of-5 multisig**, controlled by major network partners Katana Foundation, GSR, and Polygon Labs.' (docs.katana.network/katana/core-concepts/governance/index.md)
cast call 0xd512543315c95506E4209805b888414EEF15C8C4 \ "getThreshold()" \ --block 26458556 --rpc-url "$ETH_RPC_URL" cast block 26458556 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xe258bb1cbcc988e2dfdba4ba173f9f8690520dba3647cdcae18e0651822769d2
Embed Live Control-Plane Badge
Show Katana'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/katana/)
<a href="https://pacta.wtf/protocols/katana/"><img src="https://pacta.wtf/badges/katana.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/katana.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/katana.svg (5-minute cache).
Operating Katana? 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.