ARFC: Establish Aave Rewards Multisig and Initial Incentives Operations Mandate

Summary

This ARFC proposes the creation of a new 3-of-4 rewards operations multisig at rewards.aave.eth to receive, hold, and administer incentive funding provided by third parties for Aave growth campaigns.

No Aave treasury funds are requested or authorized by this proposal. The multisig would function as a pass-through operations wallet for partner-funded incentive programs. Third parties may fund the wallet for approved campaigns, and the multisig would manage the operational configuration and distribution of those rewards.

The multisig would be operated by representatives from Aave Labs, TokenLogic, and LlamaRisk. Signer identities will not be publicly disclosed for personal safety and protocol opsec.

This proposal does not replace any existing multisig. It does not modify any active incentive program. It does not grant authority to request, receive, or deploy Aave treasury funds. It does not grant authority to change protocol risk parameters, list tokens, modify protocol contracts, or deploy funds outside the approved incentives mandate.

Motivation

Aave growth campaigns increasingly require timely coordination with external partners across new market launches, integrations, liquidity campaigns, and ecosystem programs.

Many of these campaigns are funded by third parties rather than the Aave DAO. A dedicated rewards operations multisig gives contributors a known endpoint for incentive funding while giving the DAO a clearer view into how externally funded campaigns are administered.

The purpose of this proposal is to establish that operational structure before upcoming campaign windows begin. The multisig would not control DAO capital. It would only receive incentive funding from third parties and manage those rewards according to the mandate approved by governance.

Expedited Timeline

Aave Labs proposes to move this ARFC to an immediate Snapshot vote.

The standard ARFC process generally includes a longer discussion window before Snapshot. Aave Labs is requesting an expedited timeline because certain incentive operations require a dedicated rewards administration structure before upcoming campaign start dates.

This expedited process is limited to the mandate described in this ARFC. The Snapshot vote will still give the DAO the ability to approve or reject the proposed structure before it is used as the recognized rewards operations wallet for the approved mandate.

Specification

A new rewards operations multisig will be created with the following configuration. Signer identities will not be disclosed.

Address: 0x66Ac7223048037826e12cef9a848199e31AEFabE

ENS: rewards.aave.eth

Threshold: 3-of-4

Signer Address
Signer 1 0x4b752551fC6345A7de82F76fd7a5015CA16d1a74
Signer 2 0xb291232F480F41c75802C4a60F1D2AC03404Afef
Signer 3 0xb647055A9915bF9c8021a684E175A353525b9890
Signer 4 0x45d11217458aEE68A4D976A8f17e2E24Fc5898A1

Interim Incentive Campaigns

There may be campaigns that begin before the Snapshot vote for this ARFC is completed. The relevant Aave service providers have aligned on the campaigns, and there is no practical reason to delay launch while the DAO considers the proposed rewards operations structure.

If this ARFC does not pass, the campaigns may be cancelled or wound down. Until then, they will proceed as limited interim campaigns supporting the same scope described in this proposal.

Initial Mandate

The rewards operations multisig may receive incentive funding from third-party contributors for Aave growth campaigns.

The multisig may hold and administer those third-party-funded rewards for campaigns connected to Aave markets, integrations, partner programs, or other growth initiatives approved under this mandate.

The multisig may configure and manage rewards distributions where operational action is required to activate, adjust, or complete a campaign.

The multisig may coordinate with service providers, contributors, and ecosystem partners to execute incentive campaigns within the approved scope.

The multisig must provide public reporting on funded campaigns, including the source of incentive funding, the market or program supported, the amount received, the amount distributed, and any remaining balances.

The multisig may not use funds for purposes unrelated to incentive administration.

Reporting

Aave Labs, TokenLogic, and LlamaRisk will provide periodic updates to the DAO covering active campaigns, completed campaigns, budget deployed, remaining budget, and observed performance where available.

Reports will be posted to the governance forum and will include enough information for the DAO to understand how the mandate is being used.

Next Steps

If the DAO supports this ARFC, it will proceed to Snapshot.

If Snapshot passes, rewards.aave.eth will be created and may be used to administer incentive campaigns within the approved mandate.

Disclaimer

Aave Labs is presenting this proposal as a service provider to the Aave DAO under the budget approved by the Aave Will Win framework.

Copyright

Copyright and related rights waived under CC0.

6 Likes

This ARFC to establish a new Aave rewards multisig and incentives operations mandate has been raised to Snapshot. Voting will begin in 24 hours. You may vote here.

2 Likes

I support the creation of a dedicated rewards operations multisig to improve coordination and execution of externally funded Aave ecosystem campaigns.

The proposal is pragmatic and helps separate operational incentive management from direct DAO treasury spending, which is a positive step as Aave continues expanding across multiple ecosystems and integrations.

At the same time, because the multisig will play an important operational role, transparent and regular reporting will be critical. The reporting commitments outlined in the proposal are therefore very important for maintaining DAO oversight and community trust.

I also understand the rationale behind not publicly disclosing signer identities for safety and operational security reasons, though this naturally increases the importance of strong transparency around campaign execution, fund flows, remaining balances, and measurable outcomes.

Overall, I view this as a reasonable operational framework provided that reporting standards remain consistent and publicly accessible over time.

Hello,

ACI has an exclusive mandate over incentives for the Aave DAO until July 1st.

This Snapshot is non-compliant with the ARFC and TEMP check proposal framework. Therefore, the vote is considered null.

If @AaveLabs wants to take over incentives and other ACI mandates, they’re free to propose a compliant ARFC to release the @ACI from all duty and pending obligations and officially take over from our scope.

Until then we will continue our mandate until July 1st unbothered.

Aave is still a DAO, The DAO is sovereignn, rules can be changed, scope and mandates can be changed, but in a compliant way; otherwise, it’s not a DAO.

I don’t claim to know everything that’s going on here, but I did see the very public withdrawal by ACI and now ACI rewards are nowhere to be found. What are you continuing “unbothered” if ACI isn’t running growth rewards? This feels petty to an outside observer, though like I said I don’t claim to understand all of the battle going on between y’all or exactly what you may or may not still be doing until July 1.

2 Likes

ACI still handles all current incentives campaigns and users are able to claim their rewards as expected.

We have no plan to stop this service. MASIv is now a protocol-agnostic service.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.