PACTAby Fractal Neurons
Request a dossier
Base Lending & Integrated Liquidity

Seamless Protocol (Base): control-plane safety record

1 indexed control-plane surface for Seamless Protocol (Base), pinned to a canonical Base block and compared with what the protocol documents. Contract: 0xA1b5…5A22

What differs

Changed / discrepant

  • Community Guardian Safe: docs state a 3/6 multi-sig; the Safe is 2-of-3: Guardian 0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22 (Base Safe, the address the smart-contracts page lists): getThreshold() = 2 of getOwners() = 3; guard slot empty; observed vs 'The Community Guardian Multi-Sig currently has ownership over both the Governance Guardian and Protocol Guardian functions.' documented
    Show the full onchain evidence

    Guardian 0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22 (Base Safe, the address the smart-contracts page lists): getThreshold() = 2 of getOwners() = 3; guard slot empty; getModulesPaginated() lists no module. It holds CANCELLER_ROLE on the governance timelock the same page lists as Timelock short (0x639d2dD24304aC2e6A691d8c1cFf4a2665925fee; hasRole = true), a Governance Guardian function. The docs state the Community Guardian Multi-Sig is a 3/6 multi-sig; on chain 2 signatures of 3 owners execute.

    Show the full documented text

    'The Community Guardian Multi-Sig currently has ownership over both the Governance Guardian and Protocol Guardian functions.' (raw.githubusercontent.com/seamless-protocol/gitbook/main/governance/seamless-guardians.md); '>0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22<' (raw.githubusercontent.com/seamless-protocol/gitbook/main/technical/smart-contracts.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: ModerateEmergency / freeze scope: StrongDocs-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
Moderate · Lowest controlling quorum: 2-of-3Evidence: controller fact: Safe getThreshold()
Emergency / freeze scope
Strong · Pause / freeze authority scoped behind a multi-signer controller (2-of-N Safe)Evidence: seamless-community-guardian-safe-2-of-3-s35: Guardian 0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22 (Base Safe, the address the smart-contracts page lists): getThreshold() = 2 of getOwners() = 3
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=base&address=0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "base", "address": "0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "base", "address": "0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22"})

Community Guardian Safe: docs state a 3/6 multi-sig; the Safe is 2-of-3

Status
Delta
Target
Seamless Community Guardian Safe (Base) 0xA1b5…5A22 · Basescan
Pinned block
Base #59,847,352 · Basescan · sprint 35
Block hash
0x58e5d7f0…81f3e8
Attestation
Base EAS attestation 0xce88…cdfd

Observed onchain. Guardian 0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22 (Base Safe, the address the smart-contracts page lists): getThreshold() = 2 of getOwners() = 3; guard slot empty; getModulesPaginated() lists no module. It holds CANCELLER_ROLE on the governance timelock the same page lists as Timelock short (0x639d2dD24304aC2e6A691d8c1cFf4a2665925fee; hasRole = true), a Governance Guardian function. The docs state the Community Guardian Multi-Sig is a 3/6 multi-sig; on chain 2 signatures of 3 owners execute.

Documented. 'The Community Guardian Multi-Sig currently has ownership over both the Governance Guardian and Protocol Guardian functions.' (raw.githubusercontent.com/seamless-protocol/gitbook/main/governance/seamless-guardians.md); '>0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22<' (raw.githubusercontent.com/seamless-protocol/gitbook/main/technical/smart-contracts.md)

Reproduce on any archive node
cast call 0xA1b5f2cc9B407177CD8a4ACF1699fa0b99955A22 \
  "getThreshold()" \
  --block 59847352 --rpc-url "$BASE_RPC_URL"
cast block 59847352 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0x58e5d7f07aaf27ccbf361f122a24120a821b455bb9dae30f4478a7da1381f3e8

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

Badge: https://pacta.wtf/badges/seamless-protocol-base.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/seamless-protocol-base.svg.

For maintainers and issuers

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

A maintainer and an independent verifier re-check Seamless Protocol (Base) 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 Seamless Protocol (Base)? 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)