Abracadabra Spell: control-plane safety record
1 indexed control-plane surface for Abracadabra Spell, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x5f0D…EDd2
What differs
Changed / discrepant
- Abracadabra Spell multisig: docs state 5-of-10, the Safe is 5-of-11: Abracadabra Spell Safe 0x5f0DeE98360d8200b20812e174d139A1a633EDd2 (Ethereum): getThreshold() = 5 of getOwners() = 11 owners (Safe v1.3.0); observed vs 'The 5/10 multisign is composed of:' (docs.abracadabra.money/llms-full.txt) documented
Show the full onchain evidence
Abracadabra Spell Safe 0x5f0DeE98360d8200b20812e174d139A1a633EDd2 (Ethereum): getThreshold() = 5 of getOwners() = 11 owners (Safe v1.3.0); it controls MagicInternetMoneyV1 0x99D8a9C45b2ecA8864373A26D1459e3Dff1e17F3.
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- 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: 5-of-11Evidence: controller fact: Safe getThreshold()
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Weak · Documentation differs from the chain (parameter delta)
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=0x5f0DeE98360d8200b20812e174d139A1a633EDd2"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x5f0DeE98360d8200b20812e174d139A1a633EDd2"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x5f0DeE98360d8200b20812e174d139A1a633EDd2"})Abracadabra Spell multisig: docs state 5-of-10, the Safe is 5-of-11
Observed onchain. Abracadabra Spell Safe 0x5f0DeE98360d8200b20812e174d139A1a633EDd2 (Ethereum): getThreshold() = 5 of getOwners() = 11 owners (Safe v1.3.0); it controls MagicInternetMoneyV1 0x99D8a9C45b2ecA8864373A26D1459e3Dff1e17F3.
Documented. 'The 5/10 multisign is composed of:' (docs.abracadabra.money/llms-full.txt)
cast call 0x5f0DeE98360d8200b20812e174d139A1a633EDd2 \ "getThreshold()" \ --block 26449594 --rpc-url "$ETH_RPC_URL" cast block 26449594 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xbe263d5b378dcb7c3c4e18bd8e388f0cb2dab1adacd83de2be58c9408b377287
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Abracadabra Spell differs from what the protocol documents. It turns to the neutral Aligned · Base EAS shield only when the on-chain state or the documentation changes and the two match at a new finalized block, whoever requests the re-check.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/abracadabra-spell/)
<a href="https://pacta.wtf/protocols/abracadabra-spell/"><img src="https://pacta.wtf/badges/abracadabra-spell.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/abracadabra-spell.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/abracadabra-spell.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Abracadabra Spell on mainnet within 24h and attest the result on Base. The fee pays for the 24-hour mainnet re-verification work, never the grade: your attestation reads Aligned when on-chain controls match the published documentation, and Delta when they do not.
Maintaining Abracadabra Spell? Verify and reconcile the record
Two paths, both public. A free doc-update notice asks the maintainers to correct the documentation or the onchain parameter; anyone can send it. A Full Control-Plane Dossier ($2,500–$5,000 USDC, 24h SLA) re-reads the multisig and timelock control planes on archive RPCs and prepares an upstream docs reconciliation PR. Either way the classification changes only when the onchain state or the documentation aligns at a new finalized block.
Need procurement paperwork? Request a commercial invoice (PDF).