Base Bridge: control-plane safety record
1 indexed control-plane surface for Base Bridge, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x0475…059E
What differs
Changed / discrepant
- L1 ProxyAdmin owner: docs name 0x5a0A…3d2A; owner() is another 2-of-2 Safe: Base L1 ProxyAdmin 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E (Ethereum): owner() = Safe 0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c with getThreshold() = 2 of getOwners() = 2 owners … observed vs 'Authorized to update the L1 Proxy Admin.' documented
Show the full onchain evidence
Base L1 ProxyAdmin 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E (Ethereum): owner() = Safe 0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c with getThreshold() = 2 of getOwners() = 2 owners: 0x9855054731540A48b28990B63DcF4f33d8AE46A1 (3-of-6 Safe), 0x20AcF55A3DCfe07fC4cecaCFa1628F788EC8A4Dd (8-of-11 Safe). The address the configuration page names as L1 ProxyAdmin Owner, 0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A, is a 2-of-2 Safe, not one of those owners.
Show the full documented text
'Authorized to update the L1 Proxy Admin.' (docs.base.org/specifications/reference/configuration, row L1 ProxyAdmin Owner: 0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A)
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Weak · Upgradeable with no enforced delay: upgraded by a Safe directly (a Safe has no delay of its own)Evidence: base-bridge-l1-proxyadmin-owner-s29: Base L1 ProxyAdmin 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E (Ethereum): owner() = Safe 0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c with getThreshold() = 2 of …
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: base-bridge-l1-proxyadmin-owner-s29: Base L1 ProxyAdmin 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E (Ethereum): owner() = Safe 0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c with getThreshold() = 2 of …
- Signer quorum
- Moderate · Lowest controlling quorum: 2-of-2Evidence: base-bridge-l1-proxyadmin-owner-s29: … 0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A, is a 2-of-2 Safe, not one of those owners.
- 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=0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E"})Provenance · research credit
Reported by @kinshu7777 through the Pacta Wave 2 pool (PR #90, fixture bounties/wave-2/ethereum-base-bridge.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0x71a7…89c0); credited on base-bridge-l1-proxyadmin-owner-s29. Pacta then re-read every value below on two independent RPCs at its own Sprint pin and compared it with the documentation; the classifications and the Base EAS attestation are Pacta's. See the leaderboard.
L1 ProxyAdmin owner: docs name 0x5a0A…3d2A; owner() is another 2-of-2 Safe
Observed onchain. Base L1 ProxyAdmin 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E (Ethereum): owner() = Safe 0x7bB41C3008B3f03FE483B28b8DB90e19Cf07595c with getThreshold() = 2 of getOwners() = 2 owners: 0x9855054731540A48b28990B63DcF4f33d8AE46A1 (3-of-6 Safe), 0x20AcF55A3DCfe07fC4cecaCFa1628F788EC8A4Dd (8-of-11 Safe). The address the configuration page names as L1 ProxyAdmin Owner, 0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A, is a 2-of-2 Safe, not one of those owners.
Documented. 'Authorized to update the L1 Proxy Admin.' (docs.base.org/specifications/reference/configuration, row L1 ProxyAdmin Owner: 0x5a0Aae59D09fccBdDb6C6CcEB07B7279367C3d2A)
cast call 0x0475cBCAebd9CE8AfA5025828d5b98DFb67E059E \ "owner()" \ --block 26448221 --rpc-url "$ETH_RPC_URL" cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Base Bridge 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/base-bridge/)
<a href="https://pacta.wtf/protocols/base-bridge/"><img src="https://pacta.wtf/badges/base-bridge.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/base-bridge.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/base-bridge.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Base Bridge 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 Base Bridge? 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).