PACTAby Fractal Neurons
Request a dossier
Deposit program that bootstrapped an L2's yield-bearing ETH and stablecoin balances before mainnet (Ethereum)

Blast pre-launch Farm: control-plane safety record

1 indexed control-plane surface for Blast pre-launch Farm, with its controller and timelock state pinned to a canonical Ethereum block over archive JSON-RPC (not EAS-attested; documentation parameters are linked, not compared). Contract: 0x5F6A…A47d

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: StrongEmergency / freeze scope: Not determinedDocs-vs-chain parity: Uncompared

Observed Chain pinned; docs not assessed

Aligned means the docs are accurate, not that the protocol is low-risk. The rosette rates the controls themselves.
Upgradeability
Not determined · Upgradeable; the delay gating the upgrade path is not in the published recordsEvidence: blast-pre-launch-farm-control-plane: is_eip1967_proxy = true
Timelock floor
Not determined · No enforced admin delay in the published records
Signer quorum
Strong · Lowest controlling quorum: 5-of-5Evidence: blast-pre-launch-farm-control-plane: … slot zero. Direct owner() returns Safe 5-of-5 0x67CA7Ca75b69711cfd48B44eC3F64E469BaF608C.
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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=ethereum&address=0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d"})

Provenance

RPC-pinned record: read over public JSON-RPC at the Ethereum 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.

LaunchBridge · EIP-1967 Proxy & Controller Chain

Status
Observed
Target
LaunchBridge 0x5F6A…A47d · Etherscan
Pinned block
Ethereum #26,448,221 · Etherscan · RPC-pinned, not EAS-attested
Block hash
0xa7818c0e…7607c8
Controller
5-of-5 Safe 0x67CA…608C

Observed onchain. LaunchBridge (0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d) verified on Ethereum Mainnet at canonical block #26,448,221 (792 bytes runtime code). EIP-1967 proxy: implementation 0x0bD88b59D580549285f0A207Db5F06bf24a8e561, admin slot zero. Direct owner() returns Safe 5-of-5 0x67CA7Ca75b69711cfd48B44eC3F64E469BaF608C.

Documentation (linked, not compared). Blast pre-launch Farm documentation is linked for reference (https://blast.io/). This RPC-pinned record does not compare documentation parameters with the on-chain state.

Reproduce on any archive node
cast call 0x5F6AE08B8AeB7078cf2F96AFb089D7c9f51DA47d \
  "owner()" \
  --block 26448221 --rpc-url "$ETH_RPC_URL"
cast block 26448221 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0xa7818c0e1b8807aac0c999c2dc9aeeea40b91b4f19b1b76a62ad02d8d17607c8

Control-plane badge: RPC-Observed

Pacta Control Plane: RPC-Observed

The slate badge states only what Pacta pinned on-chain; it makes no documentation claim until Blast pre-launch Farm is compared with its documentation and attested on Base.

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/blast-pre-launch-farm.svg)](https://pacta.wtf/protocols/blast-pre-launch-farm/)
HTML
<a href="https://pacta.wtf/protocols/blast-pre-launch-farm/"><img src="https://pacta.wtf/badges/blast-pre-launch-farm.svg" alt="Pacta Control Plane: RPC-Observed" height="20"></a>

Badge: https://pacta.wtf/badges/blast-pre-launch-farm.svg · live: https://pacta-x402.pacta.workers.dev/v1/badges/blast-pre-launch-farm.svg.

For maintainers and issuers

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

A maintainer and an independent verifier re-check Blast pre-launch Farm 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 Blast pre-launch Farm? 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)