PACTAby Fractal Neurons
Request a dossier
Liquid locker automating veAERO voting and reward harvesting (Base)

iAero Protocol: control-plane safety record

1 indexed control-plane surface for iAero Protocol, 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: 0x7ee8964160126081cebC443a42482E95e393e6A8.

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: Not determinedEmergency / 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 · Upgrade path not in the published records
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
curl -s "https://pacta-x402.pacta.workers.dev/v1/check/preflight?chain=base&address=0x7ee8964160126081cebC443a42482E95e393e6A8"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "base", "address": "0x7ee8964160126081cebC443a42482E95e393e6A8"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "base", "address": "0x7ee8964160126081cebC443a42482E95e393e6A8"})

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.

Liquid (LIQToken) · Non-Proxy Bytecode & Controller

Status
Observed
Target
Liquid (LIQToken) 0x7ee8…e6A8 · Basescan
Pinned block
Base #58,956,515 · Basescan · RPC-pinned, not EAS-attested
Block hash
0x82af637f…7129d0
Controller
No single-key owner or admin getter (immutable or role-scoped modules)

Observed onchain. Liquid (LIQToken) (0x7ee8964160126081cebC443a42482E95e393e6A8) verified on Base Mainnet at canonical block #58,956,515 (5,549 bytes runtime code). EIP-1967 implementation and admin storage slots are both zero (non-EIP-1967 contract). No owner(), admin(), authority(), curator() or AccessControl admin was readable on the contract.

Documentation (linked, not compared). iAero Protocol documentation is linked for reference (https://app.iaero.finance/docs). This RPC-pinned record does not compare documentation parameters with the on-chain state.

Reproduce on any archive node
cast call 0x7ee8964160126081cebC443a42482E95e393e6A8 \
  "owner()" \
  --block 58956515 --rpc-url "$BASE_RPC_URL"
cast block 58956515 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0x82af637fd7a689f4ea41c0ecd1a84a407ea93f2622b8e9c06184327d957129d0

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 iAero Protocol is compared with its documentation and attested on Base.

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

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

For issuers and maintainers

Maintaining iAero Protocol? 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)