PACTAby Fractal Neurons
Request a dossier
Canonical bridge into a based contestable ZK rollup (Ethereum)

Taiko Bridge: control-plane safety record

1 indexed control-plane surface for Taiko Bridge, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x2Aff…7ECd

What differs

Changed / discrepant

  • Emergency Multisig: minApprovals 4 of 5 signers (docs: 6); standard 3 (docs: 5): Taiko DAO 0x9CDf589C941ee81D75F34d3755671d614f7cf261 (owner of controller.taiko.eth in the taiko-mono deployment log): hasPermission() grants EXECUTE_PERMISSION on the DAO to the … observed vs 'The proposal must receive 6 approvals within 14 days from Security Council members to be executable.' documented
    Show the full onchain evidence

    Taiko DAO 0x9CDf589C941ee81D75F34d3755671d614f7cf261 (owner of controller.taiko.eth in the taiko-mono deployment log): hasPermission() grants EXECUTE_PERMISSION on the DAO to the OptimisticTokenVoting plugin 0x989E348275b659d36f8751ea1c10D146211650BE (and not to either council plugin), and PROPOSER_PERMISSION on that plugin to the Emergency Multisig 0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd and the Multisig 0xD7dA1C25E915438720692bC55eb3a7170cA90321; all three return dao() = the DAO (EIP-1967 proxies, implementations 0x437E450452E8Bc142bd5317199296EcB187c514b, 0x8510d389236d7213eE9B9C38CAaBc0aD24853C25, 0x5B0Da2FB08754a5dDf32e28887D2F5437485f085, verified). EmergencyMultisig multisigSettings() = (onlyListed true, minApprovals 4, signerList 0x0F95E6968EC1B28c794CF1aD99609431de5179c2, proposalExpirationPeriod 1,209,600 s); the SignerList addresslistLength() = 5. Its execute() needs approvals >= minApprovals and calls createProposal(..., duration 0) on the destination plugin, which executes the actions on the DAO immediately when the duration is 0 (governanceSettings() minDuration = 0): 4 of the 5 listed signers make an emergency proposal executable. Multisig (standard) multisigSettings() = (onlyListed true, minApprovals 3, destinationProposalDuration 864,000 s, same signerList, proposalExpirationPeriod 1,209,600 s): 3 approvals move a standard proposal to the public veto stage (timelockPeriod 604,800 s, as documented).

    Show the full documented text

    'The proposal must receive 6 approvals within 14 days from Security Council members to be executable.' (dao-docs.taiko.xyz/guides/making-an-emergency-proposal); 'The proposal must receive 5 approvals within 14 days from Security Council members to move to the public stage' (dao-docs.taiko.xyz/guides/making-a-standard-proposal); '- Owner (Taiko DAO): `0x9CDf589C941ee81D75F34d3755671d614f7cf261`' (raw.githubusercontent.com/taikoxyz/taiko-mono/main/packages/protocol/deployments/mainnet-contract-logs-L1.md)

Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: Not determinedEmergency / freeze scope: Not determinedDocs-vs-chain parity: Weak

Delta Docs and chain differ

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
Upgradeability
Not determined · Upgrade path not in the published records
Timelock floor
Not determined · No enforced admin delay in the published records
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
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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd"})

Emergency Multisig: minApprovals 4 of 5 signers (docs: 6); standard 3 (docs: 5)

Status
Delta
Target
Taiko DAO Emergency Multisig plugin 0x2Aff…7ECd · Etherscan
Pinned block
Ethereum #26,453,551 · Etherscan · sprint 34
Block hash
0x51e9967f…767129
Attestation
Base EAS attestation 0xc281…d992

Observed onchain. Taiko DAO 0x9CDf589C941ee81D75F34d3755671d614f7cf261 (owner of controller.taiko.eth in the taiko-mono deployment log): hasPermission() grants EXECUTE_PERMISSION on the DAO to the OptimisticTokenVoting plugin 0x989E348275b659d36f8751ea1c10D146211650BE (and not to either council plugin), and PROPOSER_PERMISSION on that plugin to the Emergency Multisig 0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd and the Multisig 0xD7dA1C25E915438720692bC55eb3a7170cA90321; all three return dao() = the DAO (EIP-1967 proxies, implementations 0x437E450452E8Bc142bd5317199296EcB187c514b, 0x8510d389236d7213eE9B9C38CAaBc0aD24853C25, 0x5B0Da2FB08754a5dDf32e28887D2F5437485f085, verified). EmergencyMultisig multisigSettings() = (onlyListed true, minApprovals 4, signerList 0x0F95E6968EC1B28c794CF1aD99609431de5179c2, proposalExpirationPeriod 1,209,600 s); the SignerList addresslistLength() = 5. Its execute() needs approvals >= minApprovals and calls createProposal(..., duration 0) on the destination plugin, which executes the actions on the DAO immediately when the duration is 0 (governanceSettings() minDuration = 0): 4 of the 5 listed signers make an emergency proposal executable. Multisig (standard) multisigSettings() = (onlyListed true, minApprovals 3, destinationProposalDuration 864,000 s, same signerList, proposalExpirationPeriod 1,209,600 s): 3 approvals move a standard proposal to the public veto stage (timelockPeriod 604,800 s, as documented).

Documented. 'The proposal must receive 6 approvals within 14 days from Security Council members to be executable.' (dao-docs.taiko.xyz/guides/making-an-emergency-proposal); 'The proposal must receive 5 approvals within 14 days from Security Council members to move to the public stage' (dao-docs.taiko.xyz/guides/making-a-standard-proposal); '- Owner (Taiko DAO): `0x9CDf589C941ee81D75F34d3755671d614f7cf261`' (raw.githubusercontent.com/taikoxyz/taiko-mono/main/packages/protocol/deployments/mainnet-contract-logs-L1.md)

Reproduce on any archive node
cast call 0x2AffADEb2ef5e1F2a7F58964ee191F1e88317ECd \
  "multisigSettings()" \
  --block 26453551 --rpc-url "$ETH_RPC_URL"
cast block 26453551 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x51e9967ffd6a84012d0dad44204d523b8ac43928e69de2801d2e72dbf8767129

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Taiko 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.

Submit updated docs

Embed this badge (it updates when the status changes):

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/taiko-bridge.svg)](https://pacta.wtf/protocols/taiko-bridge/)
HTML
<a href="https://pacta.wtf/protocols/taiko-bridge/"><img src="https://pacta.wtf/badges/taiko-bridge.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

Badge: https://pacta.wtf/badges/taiko-bridge.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/taiko-bridge.svg.

For maintainers and issuers

Fixed this gap? 24h mainnet re-verification ($99 intro)

A maintainer and an independent verifier re-check Taiko 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 Taiko 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).

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Request a dossier (24h SLA)