KVORUM
aaveSource: Aave governance v3 · #481

Complete Offboarding Plan for Chaos Labs

executedMay 11, 2026, 06:06 PM UTCby660x66a2…73ff

01Summary

AISummary by Kvorumclaude-haiku-4-5

Follow-up payload to complete AgentHub offboarding for Chaos Labs by removing remaining Agent permissions on Ethereum mainnet and Plasma that were not removed after emergency Robots cancellation. No new permissions granted, no market configuration changed.

Type
protocol deprecation

Key changes

  • Remove remaining Agent permissions on Ethereum mainnet that were not removed after emergency Robots cancellation(high)
  • Cancel stream 100073 on Ethereum mainnet if not already canceled(high)
  • Remove Agent permissions on Plasma(high)

Notable concerns

  • This is a cleanup payload following emergency actions that preceded AIP-479 execution, indicating potential execution complexities with the original proposal
  • Payload scope is limited to permission removal with no new authorities or discretionary roles being granted
ContractsAaveV3EthereumAaveV3PlasmaAgentHub
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

300 words

Summary

This proposal submits a follow-up payload to complete the AgentHub offboarding actions associated with AIP-479.

The payload removes the remaining Agent permissions on Ethereum mainnet and removes the corresponding AgentHub permissions on Plasma. No new permissions are granted and no market configuration is changed.

Motivation

AIP-479 was intended to continue the Chaos offboarding process by canceling the relevant AgentHub automation and removing the permissions held by the related Agents.

After AIP-479 was prepared, emergency actions canceled the relevant Robots on Ethereum mainnet before the payload executed. Those actions changed the live contract state but did not remove the associated Agent permissions.

Because the Robots were already canceled, the pending AIP-479 payload may fail before completing the remaining permission cleanup. The DAO still needs the Ethereum Agent permissions removed to reach the intended offboarding state.

This proposal resolves that execution mismatch with a subsequent payload scoped to the remaining cleanup.

It also completes the corresponding Plasma Agent permission removal. Plasma was originally expected to remain active longer, but both LlamaRisk and Plasma have indicated support for removing these permissions early.

This AIP does not introduce a new automation scope, parameter authority, or discretionary role. It completes the offboarding state intended by AIP-479 under current live state.

Specification

This proposal executes a follow-up payload to complete the AgentHub offboarding actions intended by AIP-479.

The payload will:

  • On Ethereum mainnet, remove the remaining Agent permissions that were not removed after the related Robots were canceled through emergency action & cancel stream 100073 (if not already canceled before execution of this payload).
  • On Plasma, remove the Agent permissions.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Material discrepancy

The description commits to two concrete, chain-specific actions: (1) removing remaining Agent permissions on Ethereum mainnet, and (2) removing AgentHub Agent permissions on Plasma. The decoded calldata, however, contains only one action row, targeting chain 0x1 (Ethereum). There is no corresponding action for a Plasma chain ID anywhere in the provided decoded actions. Because Aave governance proposals that touch multiple networks typically include one action per network (often via a CrossChainController relay), the absence of any Plasma-targeted action is notable — either the payload does not actually execute the Plasma-side cleanup the description promises, or the decoding provided to this review is incomplete. Given the strict instruction to base analysis only on what's provided, this counts as a discrepancy between the described scope (two networks) and the decoded scope (one network only). Additionally, since the single Ethereum action decodes only to a generic execute()/fallback() call with no argument detail, the specific claims about permission removal and stream cancellation on Ethereum cannot be verified from calldata alone, though this opacity is normal for Aave's payload-executor architecture and is not itself flagged as a discrepancy. The overall assessment is material_discrepancy with medium confidence, since the missing Plasma action is significant enough that a delegate should be alerted, but it may also stem from incomplete data extraction rather than a genuine funds/control redirection.

Discrepancies

  • mediumextra in description

    The description explicitly and repeatedly states that this payload also removes AgentHub Agent permissions on Plasma ('It also completes the corresponding Plasma Agent permission removal', 'On Plasma, remove the Agent permissions'). However, the decoded on-chain actions contain only a single action, targeting chain 0x1 (Ethereum mainnet). No action targeting a Plasma chain ID is present in the calldata provided. If the governance proposal is expected to bundle a distinct action per network (as is typical for Aave cross-chain proposals), the Plasma-side execution appears to be missing from what was decoded, meaning the DAO may be voting on a payload that does not actually complete the Plasma cleanup the description promises.

    “It also completes the corresponding Plasma Agent permission removal.”

  • lowomitted in description

    The single decoded action is an opaque execute()/fallback() call with no visible internal calldata. This is standard for Aave payload-executor patterns, but it means the actual permission-revocation and stream-cancellation logic described in the proposal cannot be independently verified from the calldata alone — only cross-checked against the linked source code, which is outside the scope of the decoded actions provided.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0xdaf2…e941
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters27
VP participating445.6K
Outcome (current)For
Current support100%

06Voters

27 total
Filter:
VoterChoice% of totalRationale
570x57ab…2922For155.2K34.83%—6mo ago
8B0x8b37…2a22For75.8K17.01%—6mo ago
2C0x2cc1…4df1For72.2K16.20%—6mo ago
B90xb933…8dd1For55.2K12.39%—6mo ago
C00xc0d6…b802For34.5K7.74%—6mo ago
EC0xecc2…6ac9For23.7K5.32%—6mo ago
DF0xdf71…a51fFor11.6K2.61%—6mo ago
070x0703…961bFor10K2.24%—6mo ago
EZezr3al.eth0x8659…7d0eFor6.4K1.43%—6mo ago
3D0x3ddc…05b0For518.10.12%—6mo ago
9D0x9d3c…d623For2760.06%—6mo ago
300x301d…b420For201.10.05%—6mo ago
400x4053…4f15For50.30.01%—6mo ago
720x7204…6f00For15.50.00%—6mo ago
2F0x2f2f…f78aFor5.20.00%—6mo ago
050x0579…4048For10.00%—6mo ago
690x6923…26daFor0.20.00%—6mo ago
050x05f7…946cFor0.20.00%—6mo ago
3E0x3e51…0586For0.10.00%—6mo ago
100x10c4…6069For0.10.00%—6mo ago
4C0x4ca6…7f10For0.10.00%—6mo ago
000x00b9…9787For0.10.00%—6mo ago
280x288a…bd4cFor0.10.00%—6mo ago
530x53da…c14bFor00.00%—6mo ago
A90xa97c…ccc8For00.00%—6mo ago
D80xd8de…ae41For00.00%—6mo ago
CB0xcb15…a1a0For00.00%—6mo ago
Showing 27

07Forum

No forum thread is confidently linked to this proposal.