Circle Gateway: control-plane safety record
1 indexed control-plane surface for Circle Gateway, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0x7777…00eE
What differs
Changed / discrepant
- GatewayWallet: EOA owner (UUPS upgrade, withdrawal delay) and EOA pauser over withdrawals: Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy, implementation … observed vs 'Users have full control of their deposited assets. documented
Show the full onchain evidence
Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy, implementation 0xF7a6D9D7Df917c072ac8987A820c58aA27A0e798 (GatewayWallet, verified source). owner() = 0x2A6A86466F181721ec8ff946967b56f1AA4758c5 and pauser() = 0x9812d5F0a0832d9A0a78a1ba728fACd87bC35b19, both accounts with no code (externally owned) at this pin; denylister() = 0x7359fD9aA258992eb4B6d9572c6f6c74Cf719a94, also without code. In the verified source _authorizeUpgrade, updateWithdrawalDelay and updatePauser are onlyOwner, pause() is onlyPauser, and both initiateWithdrawal() and withdraw() are whenNotPaused; no timelock sits in either path. withdrawalDelay() = 50,400 blocks; paused() = false. This record does not allege any misuse of these powers.
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: no timelock in front of upgradesEvidence: circle-gateway-wallet-eoa-owner-and-pauser-s32: Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy …
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: circle-gateway-wallet-eoa-owner-and-pauser-s32: Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy …
- Signer quorum
- Weak · Lowest controlling quorum: a single keyEvidence: circle-gateway-wallet-eoa-owner-and-pauser-s32: … 0x9812d5F0a0832d9A0a78a1ba728fACd87bC35b19, both accounts with no code (externally owned) at this pin; denylister() = 0x7359fD9aA258992eb4B6d9572c6f6c74Cf719a94, …
- Emergency / freeze scope
- Weak · Pause / freeze authority held by a single keyEvidence: circle-gateway-wallet-eoa-owner-and-pauser-s32: Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy …
- 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=0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE"})Provenance · research credit
Reported by @VB-Blue through the Pacta Wave 2 pool (PR #107, fixture bounties/wave-2/ethereum-circle-gateway.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xf2f7…969a); credited on circle-gateway-wallet-eoa-owner-and-pauser-s32. 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.
GatewayWallet: EOA owner (UUPS upgrade, withdrawal delay) and EOA pauser over withdrawals
Observed onchain. Circle GatewayWallet 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE (Ethereum; the address the Gateway contract-addresses page lists): UUPS EIP-1967 proxy, implementation 0xF7a6D9D7Df917c072ac8987A820c58aA27A0e798 (GatewayWallet, verified source). owner() = 0x2A6A86466F181721ec8ff946967b56f1AA4758c5 and pauser() = 0x9812d5F0a0832d9A0a78a1ba728fACd87bC35b19, both accounts with no code (externally owned) at this pin; denylister() = 0x7359fD9aA258992eb4B6d9572c6f6c74Cf719a94, also without code. In the verified source _authorizeUpgrade, updateWithdrawalDelay and updatePauser are onlyOwner, pause() is onlyPauser, and both initiateWithdrawal() and withdraw() are whenNotPaused; no timelock sits in either path. withdrawalDelay() = 50,400 blocks; paused() = false. This record does not allege any misuse of these powers.
Documented. 'Users have full control of their deposited assets. Funds can only move with their signature, and withdrawals are trustless.' (www.circle.com/gateway)
cast call 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE \ "owner()" \ --block 26451608 --rpc-url "$ETH_RPC_URL" cast block 26451608 --field hash --rpc-url "$ETH_RPC_URL" # expect 0x0266af5bcad519d93b3be78e41b76a62985e22fbe4feef043ac3225f6f217a17
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of Circle 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.
Embed this badge (it updates when the status changes):
[](https://pacta.wtf/protocols/circle-gateway/)
<a href="https://pacta.wtf/protocols/circle-gateway/"><img src="https://pacta.wtf/badges/circle-gateway.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/circle-gateway.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/circle-gateway.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check Circle 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 Circle 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).