Angstrom: control-plane safety record
1 indexed control-plane surface for Angstrom, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x0000…fad4
Control-plane scorecard
Aligned Docs and chain match
- Upgradeability
- Strong · Immutable or ownership renouncedEvidence: angstrom-hook-controller-timelock-s34: … 0x0000000aa232009084Bd71A5797d089AA4Edfad4 (Ethereum, not a proxy; verified source): storage slot 0 (TopLevelAuth._controller, …
- Timelock floor
- Strong · 5d minimum enforced delay across control surfacesEvidence: angstrom-hook-controller-timelock-s34: observed_delay_seconds = 432000
- 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=0x0000000aa232009084Bd71A5797d089AA4Edfad4"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x0000000aa232009084Bd71A5797d089AA4Edfad4"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x0000000aa232009084Bd71A5797d089AA4Edfad4"})Hook controller = documented ControllerV1; its owner = documented Timelock (5-day min delay)
Observed onchain. Angstrom Hook 0x0000000aa232009084Bd71A5797d089AA4Edfad4 (Ethereum, not a proxy; verified source): storage slot 0 (TopLevelAuth._controller, required by every onlyController configuration and token-pull function) = ControllerV1 0x1746484EA5e11C75e009252c102C8C33e0315fD4, whose ANGSTROM() = the hook and owner() = Timelock 0x60D41d9708BBEfd29000d1486C6406Ef23526c01, an OpenZeppelin TimelockController (verified) with getMinDelay() = 432,000 s that holds its own DEFAULT_ADMIN_ROLE: the three addresses of the deployments page's L1 table, in that control order.
Documented. 'Angstrom Hook 0x0000000aa232009084Bd71A5797d089AA4Edfad4 ControllerV1 0x1746484EA5e11C75e009252c102C8C33e0315fD4 Timelock 0x60D41d9708BBEfd29000d1486C6406Ef23526c01' (docs.angstrom.xyz/contracts/deployments)
cast storage 0x0000000aa232009084Bd71A5797d089AA4Edfad4 \ 0x0000000000000000000000000000000000000000000000000000000000000000 \ --block 26453551 --rpc-url "$ETH_RPC_URL" cast block 26453551 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x51e9967ffd6a84012d0dad44204d523b8ac43928e69de2801d2e72dbf8767129
Embed Live Control-Plane Badge
Show Angstrom'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/angstrom/)
<a href="https://pacta.wtf/protocols/angstrom/"><img src="https://pacta.wtf/badges/angstrom.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>
Static badge: https://pacta.wtf/badges/angstrom.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/angstrom.svg (5-minute cache).
Operating Angstrom? 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.