PACTAby Fractal Neurons
Request a dossier
L1 Canonical Bridge (token deposits) (Ethereum)

Sonic Gateway: control-plane safety record

1 indexed control-plane surface for Sonic Gateway, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xa1E2…ec20

What differs

Changed / discrepant

  • Fail-safe recovery: bridge declared dead after 200 days offline (docs: 14 days, immutable): Sonic Gateway TokenDeposit 0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20 (Ethereum): UUPS proxy, implementation 0xAdE2eF0101278fe11490F2EE2aaD7915a094ADe9. In its verified source, fetchDeadStatus() … observed vs 'In the highly unlikely event that the Gateway or the Sonic chain is down for 14 consecutive days, users are able to reclaim their bridged assets on Ethereum.' documented
    Show the full onchain evidence

    Sonic Gateway TokenDeposit 0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20 (Ethereum): UUPS proxy, implementation 0xAdE2eF0101278fe11490F2EE2aaD7915a094ADe9. In its verified source, fetchDeadStatus() marks the bridge dead (unlocking withdrawals and deposit cancels while dead) only once the StateOracle's lastUpdateTime is older than TIME_UNTIL_DEAD = 200 days; the runtime code read at this pin holds that constant (17,280,000 s) and no 14-day constant. exitAdministrator() = 0x7390251Bf35AA7eA7C196fc4750bd5d6c5918329 (the mechanism is off while it is zero; the owner sets it). _authorizeUpgrade is onlyOwner, and owner() = 0x9Fe65a5418850015a9D8ad3Ca50d6a0B9769FbE0, a 3-of-4 Safe, so the period can be changed by an upgrade. Not dead at this pin (deadState zero; StateOracle 0xB7e8CC3F5FeA12443136f0cc13D81F109B2dEd7f lastUpdateTime 1795109183).

    Show the full documented text

    'In the highly unlikely event that the Gateway or the Sonic chain is down for 14 consecutive days, users are able to reclaim their bridged assets on Ethereum.' (docs.soniclabs.com/llms-full.txt)

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

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: StrongEmergency / 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 · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: sonic-gateway-fail-safe-200-days-s31: Sonic Gateway TokenDeposit 0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20 (Ethereum): UUPS proxy, implementation 0xAdE2eF0101278fe11490F2EE2aaD7915a094ADe9. In its …
Timelock floor
Not determined · No enforced admin delay in the published records
Signer quorum
Strong · Lowest controlling quorum: 3-of-4Evidence: sonic-gateway-fail-safe-200-days-s31: … 0x9Fe65a5418850015a9D8ad3Ca50d6a0B9769FbE0, a 3-of-4 Safe, so the period can be changed …
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=0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20"})

Fail-safe recovery: bridge declared dead after 200 days offline (docs: 14 days, immutable)

Status
Delta
Target
Sonic Gateway TokenDeposit (Ethereum) 0xa1E2…ec20 · Etherscan
Pinned block
Ethereum #26,450,616 · Etherscan · sprint 31
Block hash
0xd2df7ccb…f37c35
Attestation
Base EAS attestation 0x63d2…de77

Observed onchain. Sonic Gateway TokenDeposit 0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20 (Ethereum): UUPS proxy, implementation 0xAdE2eF0101278fe11490F2EE2aaD7915a094ADe9. In its verified source, fetchDeadStatus() marks the bridge dead (unlocking withdrawals and deposit cancels while dead) only once the StateOracle's lastUpdateTime is older than TIME_UNTIL_DEAD = 200 days; the runtime code read at this pin holds that constant (17,280,000 s) and no 14-day constant. exitAdministrator() = 0x7390251Bf35AA7eA7C196fc4750bd5d6c5918329 (the mechanism is off while it is zero; the owner sets it). _authorizeUpgrade is onlyOwner, and owner() = 0x9Fe65a5418850015a9D8ad3Ca50d6a0B9769FbE0, a 3-of-4 Safe, so the period can be changed by an upgrade. Not dead at this pin (deadState zero; StateOracle 0xB7e8CC3F5FeA12443136f0cc13D81F109B2dEd7f lastUpdateTime 1795109183).

Documented. 'In the highly unlikely event that the Gateway or the Sonic chain is down for 14 consecutive days, users are able to reclaim their bridged assets on Ethereum.' (docs.soniclabs.com/llms-full.txt)

Reproduce on any archive node
cast call 0xa1E2481a9CD0Cb0447EeB1cbc26F1b3fff3bec20 \
  "exitAdministrator()" \
  --block 26450616 --rpc-url "$ETH_RPC_URL"
cast block 26450616 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xd2df7ccb74a6772b51a5597c8f144f5cfae362efeabf193ecfc7c80f8ff37c35

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

This badge is amber because at least one Base-EAS-attested surface of Sonic Gateway 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/sonic-gateway.svg)](https://pacta.wtf/protocols/sonic-gateway/)
HTML
<a href="https://pacta.wtf/protocols/sonic-gateway/"><img src="https://pacta.wtf/badges/sonic-gateway.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>

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

For maintainers and issuers

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

A maintainer and an independent verifier re-check Sonic Gateway 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 Sonic Gateway? 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)