PACTAby Fractal Neurons
Request a dossier
Leveraged Credit & Curated Lending

Gearbox V3 / V3.1: control-plane safety record

1 indexed control-plane surface for Gearbox V3 / V3.1, pinned to a canonical Ethereum block and compared with what the protocol documents. Contract: 0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b.

What differs

Changed / discrepant

  • Timelock delay: 36 h observed vs 2 d documented

Matched

  • Safe threshold: 4-of-12

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: ModerateSigner 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 · Upgrade path not in the published records
Timelock floor
Moderate · 1d 12h minimum enforced delay across control surfacesEvidence: gearbox-v3-legacy-timelock-and-instance-safe: observed_delay_seconds = 129600
Signer quorum
Strong · Lowest controlling quorum: 4-of-12Evidence: gearbox-v3-legacy-timelock-and-instance-safe: … (0xbb803559B4D58b75E12dd74641AB955e8B0Df40E, 4-of-12), Treasury (0x7b065Fcb0760dF0CEA8CFd144e08554F3CeA73D1, …
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=0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b"})

LegacyTimelock Delay & InstanceManager Safe Quorum

Status
Delta
Target
Gearbox LegacyTimelock 0xa133…f23b · Etherscan
Pinned block
Ethereum #26,403,523 · Etherscan · sprint 11
Block hash
0xfc7beaa2…d4681a
Attestation
Base EAS attestation 0x754e…5e42

Observed onchain. LegacyTimelock (0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b) delay() = 129600s (36 hours, GIP-104), admin() = LegacyGovernor (0x29B97F37B3E0C704bCFD785F5b7bBa2A0B7df2c7); InstanceManager (0x77777777144339Bdc3aCceE992D8d4D31734CB2e) owner() = 4-of-21 Gnosis Safe (0x1E9ec044853611F4bCD4BBcFE7657508BD1c53D3); Tech (0xA7D5DDc1b8557914F158076b228AA91eF613f1D5, 6-of-12), Veto (0xbb803559B4D58b75E12dd74641AB955e8B0Df40E, 4-of-12), Treasury (0x7b065Fcb0760dF0CEA8CFd144e08554F3CeA73D1, 5-of-10), and Fee (0x3E965117A51186e41c2BB58b729A1e518A715e5F, 5-of-10) Guard Safes match documented thresholds.

Documented. docs.gearbox.finance states technical changes are 'behind a 2-day timelock' (172800s) and lists InstanceManager multisig as '4-of-12 (Subject to chain-specific configuration)'.

Reproduce on any archive node
cast call 0xa133C9A92Fb8dDB962Af1cbae58b2723A0bdf23b \
  "delay()" \
  --block 26403523 --rpc-url "$ETH_RPC_URL"
cast block 26403523 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xfc7beaa2338e8054577c0b101b641bc42afca2af39cb85d3fc13cbee32d4681a

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

Badge: https://pacta.wtf/badges/gearbox-v3-v3-1.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/gearbox-v3-v3-1.svg.

For issuers and maintainers

Maintaining Gearbox V3 / V3.1? 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)