PACTAby Fractal Neurons
Request a dossier
Lending Market (Base)

Aave V3 (Base): control-plane safety record

2 indexed control-plane surfaces for Aave V3 (Base), each pinned to a canonical Base block and compared with what the protocol documents. Contracts: 0x2DC219E716793fb4b21548C0f009Ba3Af753ab01, 0x56C1a4b54921DEA9A344967a8693C7E661D72968.

Control-plane scorecard

Upgradeability: Not determinedTimelock floor: ModerateSigner quorum: StrongEmergency / freeze scope: StrongDocs-vs-chain parity: Strong

Aligned Docs and chain match

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
Moderate · 1d minimum enforced delay across control surfacesEvidence: aave-v3-base-payloads-level1-1d-delay-s19: observed_delay_seconds = 86400
Signer quorum
Strong · Lowest controlling quorum: 4-of-7Evidence: controller fact: Safe getThreshold()
Emergency / freeze scope
Strong · Pause / freeze authority scoped behind a multi-signer controller (4-of-N Safe)Evidence: aave-v3-base-emergency-admin-protocol-guardian-4of7-s19: Protocol Guardian Safe (0x56C1a4b54921DEA9A344967a8693C7E661D72968, v1.3.0): getThreshold() = 4 of 7 owners, the 7 signers listed in the docs
Docs-vs-chain parity
Strong · Chain matches or is stronger than the documentation

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

EMERGENCY_ADMIN (pause / unpause) = Aave Protocol Guardian 4-of-7 Safe

Status
Aligned
Target
Aave Protocol Guardian Safe (Base) 0x56C1…2968 · Basescan ↗
Pinned block
Base #57,886,975 · Basescan ↗ · sprint 19
Block hash
0xf88ef5af…6ad277

Observed onchain. Protocol Guardian Safe (0x56C1a4b54921DEA9A344967a8693C7E661D72968, v1.3.0): getThreshold() = 4 of 7 owners, the 7 signers listed in the docs; ACLManager 0x43955b0899Ab7232E3a454cf84AedD22Ad46FD33 hasRole(EMERGENCY_ADMIN, Safe) = true, hasRole(POOL_ADMIN, Safe) = false.

Documented. aave.com/docs (governance): 'The Protocol Emergency Guardian is a 4 of 7 multi-signature wallet consisting of the following signers:' and 'The Protocol Emergency Guardian holds the EMERGENCY_ ADMIN'; ACL Manager docs: 'Holders of this role can pause and unpause the pool or an individual reserve.'

Reproduce on any archive node
cast call 0x56C1a4b54921DEA9A344967a8693C7E661D72968 \
  "getThreshold()" \
  --block 57886975 --rpc-url "$BASE_RPC_URL"
cast block 57886975 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0xf88ef5af0e0555ca6b7e28b325f5057163cb52d6ced0f509507613423c6ad277

Level-1 governance payloads execute on Base through ExecutorLvl1 after a 1-day delay

Status
Aligned
Target
Aave Governance V3 PayloadsController (Base) 0x2DC2…ab01 · Basescan ↗
Pinned block
Base #57,886,975 · Basescan ↗ · sprint 19
Block hash
0xf88ef5af…6ad277

Observed onchain. PayloadsController (0x2DC219E716793fb4b21548C0f009Ba3Af753ab01).getExecutorSettingsByAccessControl(1) = (ExecutorLvl1 0x9390B1735def18560c509E2d0bc090E9d6BA257a, 86400s); MIN_EXECUTION_DELAY() = 86400s, MAX_EXECUTION_DELAY() = 864000s; MESSAGE_ORIGINATOR() = Ethereum Governance V3 0x9AEE0B04504CeF83A65AC3f0e838D0593BCb2BC7 (ORIGIN_CHAIN_ID() = 1); access level 2 has no executor on Base. ExecutorLvl1 (owner() = the PayloadsController) is owner() and getACLAdmin() of PoolAddressesProvider 0xe20fCBdBfFC4Dd138cE8b2E6FBb6CB49777ad64D and holds DEFAULT_ADMIN_ROLE and POOL_ADMIN on ACLManager 0x43955b0899Ab7232E3a454cf84AedD22Ad46FD33.

Documented. aave.com/docs (governance): 'compared with the 3-day vote and 1-day timelock of a Level 1 proposal'

Reproduce on any archive node
cast call 0x2DC219E716793fb4b21548C0f009Ba3Af753ab01 \
  "getExecutorSettingsByAccessControl(uint8)" 0x1 \
  --block 57886975 --rpc-url "$BASE_RPC_URL"
cast block 57886975 --field hash --rpc-url "$BASE_RPC_URL"
# expect 0xf88ef5af0e0555ca6b7e28b325f5057163cb52d6ced0f509507613423c6ad277

Embed Live Control-Plane Badge

Pacta Control Plane: Aligned · Base EAS

Show Aave V3 (Base)'s Base-EAS-attested Aligned control-plane status in a README, docs page or forum post. The badge links back to this record.

Markdown
[![Pacta Control Plane](https://pacta.wtf/badges/aave-v3-base.svg)](https://pacta.wtf/protocols/aave-v3-base/)
HTML
<a href="https://pacta.wtf/protocols/aave-v3-base/"><img src="https://pacta.wtf/badges/aave-v3-base.svg" alt="Pacta Control Plane: Aligned · Base EAS" height="20"></a>

Static badge: https://pacta.wtf/badges/aave-v3-base.svg (rebuilt with the site). Live edge badge: https://pacta-x402.pacta.workers.dev/v1/badges/aave-v3-base.svg (5-minute cache).

Operating Aave V3 (Base)? Add Continuous Monitoring

Continuous Monitoring ($1,500 USDC / month) re-checks your control plane after governance proposals, signer rotations and timelock upgrades, and refreshes the dossier and attestation. It does not buy a status: the result can still be Delta whenever docs and chain diverge.

Read-only onchain analysis. Not investment advice. Exploit-sensitive vulnerabilities are never published here; they go through Immunefi or Cantina bounty programmes.Continuous Monitoring · $1,500 USDC / month →