PACTAby Fractal Neurons
Request a dossier
Modular Lending & DEX Vaults

Fluid / Instadapp: control-plane safety record

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

What differs

Changed / discrepant

  • VaultFactory.isVaultAuth Migration Scope: isVaultAuth(vault, 0x4F6F977aCDD1177DCD81aB83074855EcB9C2D49e) returns true on Vault 76 (0x7FE0B032cB5982Af72498F96be3DD6566F7B7de8), Vault 110 (0xee327311D8640156E87eC33ea55FcbF2309e0ce6), Vault 111 … observed vs fluid-permissions-and-mutability.md describes narrow fee/reward/magnifier team multisig scope outside migration grants. documented
    Show the full onchain evidence

    isVaultAuth(vault, 0x4F6F977aCDD1177DCD81aB83074855EcB9C2D49e) returns true on Vault 76 (0x7FE0B032cB5982Af72498F96be3DD6566F7B7de8), Vault 110 (0xee327311D8640156E87eC33ea55FcbF2309e0ce6), Vault 111 (0x984636a30ed2B4A61FB7150CED644096349275d3), and Vault 144 (0x0e19B64F3A79FeeE12Df1b6f239929c6ab6C7ED0) per IGP-98 / IGP-126 migration configuration.

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: Not determinedSigner quorum: Not determinedEmergency / 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
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
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=0x324c5Dc1fC42c7a4D43d92df1eBA58a54d13Bf2d"
Python (requests)
import requests
r = requests.get("https://pacta-x402.pacta.workers.dev/v1/check/preflight",
                 params={"chain": "ethereum", "address": "0x324c5Dc1fC42c7a4D43d92df1eBA58a54d13Bf2d"})
print(r.json()["verdict"])
MCP tool call · https://pacta-x402.pacta.workers.dev/mcp
pacta_check_preflight({"chain": "ethereum", "address": "0x324c5Dc1fC42c7a4D43d92df1eBA58a54d13Bf2d"})

VaultFactory.isVaultAuth Migration Scope

Status
Delta
Target
VaultFactory 0x324c…Bf2d · Etherscan
Pinned block
Ethereum #26,401,405 · Etherscan · sprint 5
Block hash
0x26e155e1…be1510
Attestation
Base EAS attestation 0x8042…28e5

Observed onchain. isVaultAuth(vault, 0x4F6F977aCDD1177DCD81aB83074855EcB9C2D49e) returns true on Vault 76 (0x7FE0B032cB5982Af72498F96be3DD6566F7B7de8), Vault 110 (0xee327311D8640156E87eC33ea55FcbF2309e0ce6), Vault 111 (0x984636a30ed2B4A61FB7150CED644096349275d3), and Vault 144 (0x0e19B64F3A79FeeE12Df1b6f239929c6ab6C7ED0) per IGP-98 / IGP-126 migration configuration.

Documented. fluid-permissions-and-mutability.md describes narrow fee/reward/magnifier team multisig scope outside migration grants.

Reproduce on any archive node
cast call 0x324c5Dc1fC42c7a4D43d92df1eBA58a54d13Bf2d \
  "isVaultAuth(address,address)" 0x7FE0B032cB5982Af72498F96be3DD6566F7B7de8 0x4F6F977aCDD1177DCD81aB83074855EcB9C2D49e \
  --block 26401405 --rpc-url "$ETH_RPC_URL"
cast block 26401405 --field hash --rpc-url "$ETH_RPC_URL"
# expect 0x26e155e1569d436406a52ecee31c94d8d8ef2ca4c45d82211a84c8c802be1510

Control-plane badge: Parameter Delta

Pacta Control Plane: Parameter Delta

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

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

For issuers and maintainers

Maintaining Fluid / Instadapp? 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)