f(x) Protocol v2: control-plane safety record
2 indexed control-plane surfaces for f(x) Protocol v2, each pinned to a canonical Ethereum block and compared with what the protocol documents. Contracts: 0x3235…CdA6, 0x3363…C708
What differs
Changed / discrepant
- ProtocolTreasury DEFAULT_ADMIN_ROLE Holders: DEFAULT_ADMIN_ROLE (0x00) on all 4 v2 ProtocolTreasury proxies … observed vs LongPoolManager (0x250893CA4Ba5d05626C785e8da758026928FCD24) and v2 governance docs scope EmergencySafe strictly to EMERGENCY_ROLE behind 3-day Timelock admin. documented
Show the full onchain evidence
DEFAULT_ADMIN_ROLE (0x00) on all 4 v2 ProtocolTreasury proxies (0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6, 0xb178197E88D58Da21bE22A408E850d1e6Dc09A38, 0x6D9e81c5b7C4b37d0Fe9E8CDA776e057f4040868, 0x87d5e4cAaF4358A4337C10859c7107c7AEF4f8Ce) held directly by OpsSafe (0x26B2ec4E02ebe2F54583af25b647b1D619e67BbF, 6-of-9 Safe) and EmergencySafe (0x28c921adAC4c1072658eB01a28DA06b5F651eF62, 3-of-4 Safe), while Timelock (0x68863fb8855b04509a835082478D6E3D0bE4E61a, getMinDelay = 259200s) holds false.
- Timelock delay: 0 s (no delay) observed vs 3 d documented
Protocol maintainer and fixed this gap? Get it re-verified on mainnet in 24h
Control-plane scorecard
Delta Docs and chain differ
- Upgradeability
- Not determined · Upgrade path not in the published records
- Timelock floor
- Weak · 0s minimum enforced delay across control surfacesEvidence: f-x-protocol-v2-router-owner-safe-s29: observed_delay_seconds = 0
- Signer quorum
- Strong · Lowest controlling quorum: 3-of-4Evidence: fx-protocol-v2-treasury-admin: … (0x28c921adAC4c1072658eB01a28DA06b5F651eF62, 3-of-4 Safe), while Timelock (0x68863fb8855b04509a835082478D6E3D0bE4E61a, …
- 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 -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "ethereum", "address": "0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "ethereum", "address": "0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6"})Provenance · research credit
Reported by @VB-Blue through the Pacta Wave 2 pool (PR #83, fixture bounties/wave-2/ethereum-fx-protocol.json), merged under the Apache-2.0 commercial grant and paid $1.00 USDC (tx 0xb804…51ef); credited on f-x-protocol-v2-router-owner-safe-s29. 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.
ProtocolTreasury DEFAULT_ADMIN_ROLE Holders
Observed onchain. DEFAULT_ADMIN_ROLE (0x00) on all 4 v2 ProtocolTreasury proxies (0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6, 0xb178197E88D58Da21bE22A408E850d1e6Dc09A38, 0x6D9e81c5b7C4b37d0Fe9E8CDA776e057f4040868, 0x87d5e4cAaF4358A4337C10859c7107c7AEF4f8Ce) held directly by OpsSafe (0x26B2ec4E02ebe2F54583af25b647b1D619e67BbF, 6-of-9 Safe) and EmergencySafe (0x28c921adAC4c1072658eB01a28DA06b5F651eF62, 3-of-4 Safe), while Timelock (0x68863fb8855b04509a835082478D6E3D0bE4E61a, getMinDelay = 259200s) holds false.
Documented. LongPoolManager (0x250893CA4Ba5d05626C785e8da758026928FCD24) and v2 governance docs scope EmergencySafe strictly to EMERGENCY_ROLE behind 3-day Timelock admin.
cast call 0x32356FE312Eba9B7D6A157ad28D1ca91b571CdA6 \ "hasRole(bytes32,address)" 0x0000000000000000000000000000000000000000000000000000000000000000 0x26B2ec4E02ebe2F54583af25b647b1D619e67BbF \ --block 26400152 --rpc-url "$ETH_RPC_URL" cast block 26400152 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa9a61622304ec55c5fec49abbcabec60069f66f28792cf841bdd7aef12ce63aa
V2 Router (Diamond) owner: docs put every transaction behind a 3-day timelock; owner() is the 6-of-9 Safe
Observed onchain. f(x) V2 Router 0x33636D49FbefBE798e15e7F356E8DBef543CC708 (Ethereum, an EIP-2535 Diamond): owner() = Safe 0x26B2ec4E02ebe2F54583af25b647b1D619e67BbF with getThreshold() = 6 of getOwners() = 9 owners (Safe v1.3.0), no Safe guard; facetAddress(diamondCut 0x1f931c1c) = 0x221ffB180AD01213FF882ab7DE9c75E23F9efA63. The timelock the docs name, 0x68863fb8855b04509a835082478D6E3D0bE4E61a, reads getMinDelay() = 259,200 s and is not the Router's owner.
Documented. 'Once queued, every transaction enter a mandatory 3-day public timelock before execution giving the community time to review, question, or flag concerns.' (fxprotocol.gitbook.io/fx-docs/more/resources/multisig)
cast call 0x33636D49FbefBE798e15e7F356E8DBef543CC708 \ "owner()" \ --block 26448221 --rpc-url "$ETH_RPC_URL" cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL" # expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8
Control-plane badge: Parameter Delta
This badge is amber because at least one Base-EAS-attested surface of f(x) Protocol v2 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/f-x-protocol-v2/)
<a href="https://pacta.wtf/protocols/f-x-protocol-v2/"><img src="https://pacta.wtf/badges/f-x-protocol-v2.svg" alt="Pacta Control Plane: Parameter Delta" height="20"></a>
Badge: https://pacta.wtf/badges/f-x-protocol-v2.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/f-x-protocol-v2.svg.
Fixed this gap? 24h mainnet re-verification ($99 intro)
A maintainer and an independent verifier re-check f(x) Protocol v2 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 f(x) Protocol v2? 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).