Hop Protocol: control-plane safety record
1 indexed control-plane surface for Hop Protocol, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xb890…727f
What differs
Changed / discrepant
- L1 ETH Bridge governance: 24h Timelock whose admin is a 2-of-3 key Safe: Hop L1_ETH_Bridge 0xb8901acB165ed027E32754E0FFe830802919727f (Ethereum, not a proxy; verified source; the SDK's Ethereum ETH l1Bridge): addBonder(), removeBonder(), setGovernance() … observed vs 'In summary, the Hop DAO controls every aspect of the protocol.' documented
Show the full onchain evidence
Hop L1_ETH_Bridge 0xb8901acB165ed027E32754E0FFe830802919727f (Ethereum, not a proxy; verified source; the SDK's Ethereum ETH l1Bridge): addBonder(), removeBonder(), setGovernance(), setChallengePeriod(), setChainIdDepositsPaused() and rescueTransferRoot() are onlyGovernance, and governance() = 0x22e3F828b3f47dAcFACd875D20bd5cc0879C96e7, a Compound-style Timelock (verified) with delay() = 86,400 s, pendingAdmin() empty and admin() = Safe 0x1ec078551A5ac8F0f51fAc57Ffc48Ea7d9A86E9d: getThreshold() = 2 of getOwners() = 3; guard slot empty; getModulesPaginated() lists no module; all 3 owners are accounts with no code. Neither the DAO Governor 0xed8Bdb5895B8B7f9Fdb3C087628FD8410E853D48 nor the DAO Timelock 0xeeA8422a08258e73c139Fc32a25e10410c14bd7a (both on the governance links page) is in this path: 2 keys queue and execute any onlyGovernance call after 24 hours.
Show the full documented text
'In summary, the Hop DAO controls every aspect of the protocol.' (docs.hop.exchange/governance/into-to-hop-dao); '0xeeA8422a08258e73c139Fc32a25e10410c14bd7a' (docs.hop.exchange/governance/important-links); 'l1Bridge: '0xb8901acB165ed027E32754E0FFe830802919727f'' (raw.githubusercontent.com/hop-protocol/hop/develop/packages/sdk/src/addresses/mainnet.ts)
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Strong · Immutable or ownership renouncedEvidence: hop-l1-eth-bridge-governance-2-of-3-safe-s34: … 0xb8901acB165ed027E32754E0FFe830802919727f (Ethereum, not a proxy; verified source; the SDK's Ethereum …
- Timelock floor
- Moderate · 1d minimum enforced delay across control surfacesEvidence: hop-l1-eth-bridge-governance-2-of-3-safe-s34: observed_delay_seconds = 86400
- Signer quorum
- Strong · DAO Governor (token vote)Evidence: hop-l1-eth-bridge-governance-2-of-3-safe-s34: … accounts with no code. Neither the DAO Governor 0xed8Bdb5895B8B7f9Fdb3C087628FD8410E853D48 …
- 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=0xb8901acB165ed027E32754E0FFe830802919727f"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0xb8901acB165ed027E32754E0FFe830802919727f"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0xb8901acB165ed027E32754E0FFe830802919727f"})L1 ETH Bridge governance: 24h Timelock whose admin is a 2-of-3 key Safe
Observed onchain. Hop L1_ETH_Bridge 0xb8901acB165ed027E32754E0FFe830802919727f (Ethereum, not a proxy; verified source; the SDK's Ethereum ETH l1Bridge): addBonder(), removeBonder(), setGovernance(), setChallengePeriod(), setChainIdDepositsPaused() and rescueTransferRoot() are onlyGovernance, and governance() = 0x22e3F828b3f47dAcFACd875D20bd5cc0879C96e7, a Compound-style Timelock (verified) with delay() = 86,400 s, pendingAdmin() empty and admin() = Safe 0x1ec078551A5ac8F0f51fAc57Ffc48Ea7d9A86E9d: getThreshold() = 2 of getOwners() = 3; guard slot empty; getModulesPaginated() lists no module; all 3 owners are accounts with no code. Neither the DAO Governor 0xed8Bdb5895B8B7f9Fdb3C087628FD8410E853D48 nor the DAO Timelock 0xeeA8422a08258e73c139Fc32a25e10410c14bd7a (both on the governance links page) is in this path: 2 keys queue and execute any onlyGovernance call after 24 hours.
Documented. 'In summary, the Hop DAO controls every aspect of the protocol.' (docs.hop.exchange/governance/into-to-hop-dao); '0xeeA8422a08258e73c139Fc32a25e10410c14bd7a' (docs.hop.exchange/governance/important-links); 'l1Bridge: '0xb8901acB165ed027E32754E0FFe830802919727f'' (raw.githubusercontent.com/hop-protocol/hop/develop/packages/sdk/src/addresses/mainnet.ts)
cast call 0xb8901acB165ed027E32754E0FFe830802919727f \ "governance()" \ --block 26453551 --rpc-url "$ETH_RPC_URL" cast block 26453551 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x51e9967ffd6a84012d0dad44204d523b8ac43928e69de2801d2e72dbf8767129
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Hop Protocol 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/hop-protocol/)
<a href="https://pacta.wtf/protocols/hop-protocol/"><img src="https://pacta.wtf/badges/hop-protocol.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/hop-protocol.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/hop-protocol.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Hop Protocol 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 Hop Protocol? 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).