Hi,
I am planning a public-good submission for the Code audits or Developer tooling category at Aave Grants DAO, but I want to confirm the program is currently active before committing the build effort. A few signals on public surfaces look quiet, so this is a sanity-check rather than an application:
- aavegrants.org’s most recent dated content is the May 10 2021 “Hello World!” post. The rolling-applications copy is present on the landing page, but the news / announcements feed has not been updated since 2021.
- The November 2023 ARFC continuation proposal Snapshot ended with Abstain as the main option ([ARFC] Updated Aave Grants Continuation Proposal), with AGD posting at the time that the program would continue from existing treasury. I have not been able to find a subsequent successful renewal or replacement announcement on a primary source.
- The April 2026 $25M “Aave Will Win” grant (proposal 469) went to Aave Labs, which I understand is a distinct vehicle from the AGD ecosystem program.
The questions:
1. Is AGD currently reviewing rolling applications and announcing new grantees in 2026 from existing treasury? When was the most recent grantee announcement?
2. Is the application path linked from Apply for a grant! the current intake, or is there a different intake surface now?
3. If AGD is effectively wound down, where do security-tooling contributions targeting Aave protocol contracts now route: Aave Labs, BGD Labs, the BGD continuous code-audits framework, or somewhere else?
Context on what I would be submitting. I run CaliperForge, an invariant-testing shop. The discipline is planted-twin invariant testing: write an invariant, plant a known bug as a twin contract, prove the invariant rejects the twin and accepts the clean version (zero false positives on the clean, at least one fail on the planted). The submission target would be an open-source planted-twin invariant atlas covering Aave-ecosystem contracts (v3 pool liquidation sequencing, GHO mint / burn accounting and peg dynamics, eMode collateral-factor logic), reusable by Aave integration teams and by audit firms working on Aave-ecosystem code.
Existence proof of the methodology, not of any Aave work: cf-invariants on Starknet, public, 12 invariant classes with paired clean=0 / planted>=1 CI green. Repo: GitHub - caliperforge/cf-invariants: Stateful invariant authoring with AI-suggested invariants on top of snforge. Apache-2.0. Twelve reference contracts live on Starknet Sepolia. caliperforge.com/ai-disclosure · GitHub. I have not yet harnessed an Aave contract; that is what the funding would build.
Happy to write up a one-page application against whichever category fits if the program is open. If it is not, I will route to whichever surface owns Aave security tooling now. Either answer is useful; I would rather not submit into a dormant intake.
Thanks,
Michael Moffett
CaliperForge