KVORUM
aaveSource: Aave governance v3 · #407

Orbit Program Renewal - Q3 and Q4 2025

executedNov 11, 2025, 03:53 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Renewal of the Orbit delegate compensation program for Q3 and Q4 2025 (July 1 - December 31, 2025), allocating 90,000 GHO to recognize and compensate eligible delegates who meet minimum voting power (20k) and voting ratio (85%) requirements across three delegate platforms.

Type
treasury allocation
Funding
$90000 GHO (stablecoin equivalent)

Key changes

  • Renewal of Orbit delegate compensation program for 6-month period (Q3-Q4 2025)(high)
  • Allocation of 90,000 GHO tokens for delegate compensation(high)
  • Change to semi-annual program structure (two 6-month periods per year instead of quarterly)(medium)
  • Compensation distributed to three eligible delegate platforms: EzR3al, stablelabs, and IgnasDefi(high)
  • Continuation of eligibility requirements: minimum 20k voting power and 85% vote ratio on Snapshots and AIPs(medium)

Notable concerns

  • Service Providers are explicitly excluded from Orbit Program eligibility
  • Program structure change from quarterly to semi-annual may impact governance frequency
  • Specific delegate performance tracking required to maintain 85% voting ratio threshold
Contracts0x24efbae8cc8f22252ba83cac08c3341c1198e449
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

Simple Summary

Proposing the renewal of the Orbit program for recognized delegates, compensating them with GHO, associated with their governance activity during Q3 and Q4 2025 ( From 2025-07-01, last date, until 2025-12-31). The reason is because extending period coverage will bring more reliance and predictability for delegates platform.

Motivation

Orbit recognizes the added value of the Delegates in the decentralization & diversity of the Aave DAO. This compensation allows them to focus on Aave and keep their contribution efforts to our governance. The ACI proposes the extension of Orbit for a both Q3 and Q4 2025, from 2025-07-01 to 2025-12-31.

As a reminder from previous Orbit round, a new cutoff had been set, starting at AIP 224, to apply again previous rules of a minimum of 20k voting power and 85% vote ratio on all Snapshots and AIP to be considered eligible to Orbit.

From now on, Orbit period coverage will be semi-annually or 2 times per year (Q1 and Q2 together, and Q3 and Q4 together), with the aim of reducing governance bloat.

Specification

Additional considerations:

As a reminder, Service Providers will not be considered eligible to Orbit Program.

Funds are distributed based on 180 days, as seen on budget and as specified on motivation section.

Disclosure

The ACI is independent and has not received any form of compensation from related parties for the drafting of this proposal.

Copyright

Copyright and related rights waived under Creative Commons Zero (CC0)

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal follows Aave's standard governance payload pattern: the on-chain action is a single delegatecall to execute() on a payload contract, with no decoded internal calls or transfer amounts visible in the provided calldata. This is typical and expected for Aave AIPs, where the actual GHO transfer logic (recipients, amounts, vesting/streaming details) lives inside the payload contract's bytecode and is not surfaced by this level of decoding. Because the decoded action gives no specific transfer amounts, recipient addresses, or token details to compare against the description's claims (90,000 GHO to three named delegate platforms over Q3/Q4 2025), a substantive value-by-value comparison is not possible from the data given. There is nothing in the visible calldata that contradicts the description, but there is also nothing that confirms the specific figures. Given the lack of granular calldata, confidence in this comparison is necessarily low, and no discrepancy can be responsibly flagged — flagging one would be speculative given the absence of decoded transfer details. This aligns with the guidance to avoid false alarms when the underlying data is insufficient to verify claims. Overall the description and the single high-level action do not conflict on their face, so we mark this consistent with low confidence rather than escalating an assessment we cannot substantiate.

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
0x24ef…e449
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.