Spectra MetaVaults: control-plane safety record
1 indexed control-plane surface for Spectra MetaVaults, with its controller and timelock state pinned to a canonical Base block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51.
Control-plane scorecard
Observed Chain pinned; docs not assessed
- Upgradeability
- Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: spectra-metavaults-control-plane: is_eip1967_proxy = true
- Timelock floor
- Not determined · No enforced admin delay in the published records
- Signer quorum
- Not determined · No signer quorum in the published records
- Emergency / freeze scope
- Not determined · No pause / freeze authority in the published records
- Docs-vs-chain parity
- Uncompared · Uncompared: documentation not assessed (RPC-observed)
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=base&address=0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51"
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
params={"chain": "base", "address": "0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51"})
print(r.json()["verdict"])pacta_check_preflight({"chain": "base", "address": "0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51"})Provenance
RPC-pinned record: read over public JSON-RPC at the Base block shown below and independently re-read at the same block by a second Pacta seat. It is not EAS-attested: no sprint number, no summary document and no Base EAS UID. Status Observed (RPC-observed baseline): the onchain control plane is pinned at block height; whether it matches the protocol's documented parameters is not assessed here (the documentation is linked for reference). Machine-readable: /api/v1/rpc-pinned.json. The Base-EAS-attested Sprint records are in /api/v1/index.json.
Spectra Token · EIP-1967 Proxy & Controller Chain
Observed onchain. Spectra Token (0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51) verified on Base Mainnet at canonical block #58,956,515 (1,115 bytes runtime code). EIP-1967 proxy: implementation 0x690700C0255C745B97A0B0C13e6f08AEc011670E, admin 0xAA8578C937f8Ce1eDb10477817FfA424EdfAE6fc. The EIP-1967 admin slot holds contract contract 0xAA8578C937f8Ce1eDb10477817FfA424EdfAE6fc. That controller is in turn controlled by contract AccessManager 0x4973b53b300d64ab72147EFF8C9d962f6b1dA02e.
Documentation (linked, not compared). Spectra MetaVaults documentation is linked for reference (https://dev.spectra.finance/). This RPC-pinned record does not compare documentation parameters with the on-chain state.
cast storage 0x64FCC3A02eeEba05Ef701b7eed066c6ebD5d4E51 \ 0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103 \ --block 58956515 --rpc-url "$BASE_RPC_URL" cast block 58956515 --field hash --rpc-url "$BASE_RPC_URL" # expect 0x82af637fd7a689f4ea41c0ecd1a84a407ea93f2622b8e9c06184327d957129d0
Control-plane badge: RPC-Observed
The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until Spectra MetaVaults is compared with its documentation and attested on Base.
[](https://pacta.wtf/protocols/spectra-metavaults/)
<a href="https://pacta.wtf/protocols/spectra-metavaults/"><img src="https://pacta.wtf/badges/spectra-metavaults.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>
Badge: https://pacta.wtf/badges/spectra-metavaults.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/spectra-metavaults.svg.
Maintaining Spectra MetaVaults? 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).