Obol Network: control-plane safety record
4 indexed control-plane surfaces for Obol Network, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7, 0x4094C8D36e40795Ca25BFe9451f158D30614666A, 0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0, 0xcB1622185A0c62A80494bEde05Ba95ef29Fbf85c.
What differs
Changed / discrepant
- OBOL supply: documented cap of 500M, no cap on-chain; a 2-of-3 Safe holds MINTER_ROLE: ObolToken 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7 (Sourcify exact match): totalSupply() = 500000000000000103303500000 (500,000,000.0000001033035 OBOL); observed vs docs.obol.org (token distribution; documented
Show the full onchain evidence
ObolToken 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7 (Sourcify exact match): totalSupply() = 500000000000000103303500000 (500,000,000.0000001033035 OBOL); mint() has no supply cap; MINTER_ROLE and DEFAULT_ADMIN_ROLE held by Safe 0x42D201CC4d9C1e31c032397F54caCE2f48C1FA72 (2-of-3, v1.3.0), not by the timelock.
Matched
- Governance timelock: 5 days between a passed proposal and execution: matches the documentation
- Governor: 30,000 OBOL proposal threshold, 0.84% quorum: matches the documentation
- stOBOL unstaking: no withdrawal delay (WithdrawGate delay 0): matches the documentation
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Strong · 5d minimum enforced delay across control surfacesEvidence: controller fact: getMinDelay() = 432000s
- Signer quorum
- Weak · Lowest controlling quorum: 1-of-2Evidence: obol-network-stobol-withdraw-delay-s24: … 0x7E90E03654732ABedF89Faf87f05BcD03ACEeFdC (1-of-2, v1.4.1).
- 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=0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0"})Governance timelock: 5 days between a passed proposal and execution
Observed onchain. TimelockController 0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0 (Sourcify exact match): getMinDelay() = 432000s (5 days); ObolGovernor 0xcB1622185A0c62A80494bEde05Ba95ef29Fbf85c holds PROPOSER, EXECUTOR and CANCELLER; DEFAULT_ADMIN_ROLE held by the timelock itself and by 0x02b5D1Fd67246c0513223D320901474aA20Bf973, not by the Governor.
Documented. docs.obol.org (v1.8 Token House governance): 'After the voting period ends, if the proposal passes, there will be a 5-day timelock delay.'
cast call 0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0 \ "getMinDelay()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Governor: 30,000 OBOL proposal threshold, 0.84% quorum
Observed onchain. ObolGovernor 0xcB1622185A0c62A80494bEde05Ba95ef29Fbf85c (Sourcify exact match): proposalThreshold() = 30,000 OBOL; quorumNumerator() / quorumDenominator() = 84 / 10000 (0.84%); votingDelay() = 7200 blocks, votingPeriod() = 36000 blocks; timelock() = 0xCdBf527842Ab04Da548d33EB09d03DB831381Fb0.
Documented. docs.obol.org (v1.8 Token House governance): 'During Week 3, a wallet holding at least 30,000 OBOL in voting power must publish the proposal on the Obol Governance Platform.' / 'The current definition for the OBOL Token House is 0.84% of minted supply.' / 'After publication, there is a 24-hour voting delay, during which the proposal can be canceled if necessary.'
cast call 0xcB1622185A0c62A80494bEde05Ba95ef29Fbf85c \ "proposalThreshold()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
stOBOL unstaking: no withdrawal delay (WithdrawGate delay 0)
Observed onchain. WithdrawGate 0x4094C8D36e40795Ca25BFe9451f158D30614666A (Sourcify exact match): delay() = 0s (DELAY_MAX() = 2592000s); owner() = Safe 0x7E90E03654732ABedF89Faf87f05BcD03ACEeFdC (1-of-2, v1.4.1).
Documented. docs.obol.org (unstaking guide): 'You can unstake at any time, there are no lockups' / 'https://etherscan.io/address/0x6590cBBCCbE6B83eF3774Ef1904D86A7B02c2fCC#writeContract'
cast call 0x4094C8D36e40795Ca25BFe9451f158D30614666A \ "delay()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
OBOL supply: documented cap of 500M, no cap on-chain; a 2-of-3 Safe holds MINTER_ROLE
Observed onchain. ObolToken 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7 (Sourcify exact match): totalSupply() = 500000000000000103303500000 (500,000,000.0000001033035 OBOL); mint() has no supply cap; MINTER_ROLE and DEFAULT_ADMIN_ROLE held by Safe 0x42D201CC4d9C1e31c032397F54caCE2f48C1FA72 (2-of-3, v1.3.0), not by the timelock.
Documented. docs.obol.org (token distribution; OBOL token): 'The total supply is capped at 500 million tokens.' / 'The official token contract address of the OBOL Token is 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7'
cast call 0x0B010000b7624eb9B3DfBC279673C76E9D29D5F7 \ "totalSupply()" \ --block 26433001 --rpc-url "$ETH_RPC_URL" cast block 26433001 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa058ec92ccf0024822a76097f183d8e2d344d56e9539038c857e0cdaaa0ee5a7
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Obol Network differs from what the protocol documents. It turns to the emerald 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/obol-network/)
<a href="https://pacta.wtf/protocols/obol-network/"><img src="https://pacta.wtf/badges/obol-network.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/obol-network.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/obol-network.svg.
Maintaining Obol Network? 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).