Continuous Security Proposal Aave <> Certora
01Summary
Aave is renewing its security services contract with Certora for 1 year at $1.5M ($1M in GHO + $500k in AAVE tokens, equivalent to 5,200 AAVE). Services include continuous formal verification of smart contracts, governance proposal reviews within 3.5 days, and 24/7 incident investigation support. The proposal extends proven security work from the past 18 months where 28 significant bugs were prevented across 169 smart contracts.
- Type
- treasury allocation
- Funding
- $1500000
Key changes
- Allocation of $1.5M annual budget for Certora security services: $1M in GHO vested linearly and $500k in AAVE tokens (5,200 AAVE) vested linearly(high)
- Addition of governance proposal review service - dedicated team will review each on-chain governance proposal within 3.5 days to verify it matches its description and has no unwanted codebase effects(high)
- Continuation of continuous formal verification using Certora Prover integrated into CI with open-source CVL specifications(high)
- 24/7 incident investigation support team for bug bounty triage and emergency response(high)
- Price reduction from $2.7M to $1.5M reflecting bear market conditions and reduced project review capacity(medium)
Generated by Kvorum
02Description
Simple Summary
We offer to extend the existing formal verification and manual review services and provide additional security services:
- Governance proposal reviews - Review every governance proposal in the on-chain stage as suggested by BGDLabs.
- We will assist Aave and BGD in reviewing Immunify bug bounties per request.
This proposal asks for a 1-year duration with a budget of $1.5m, starting from the 14th of September 2023.
Motivation
During the 18 months of services, we have reviewed 169 smart contacts consisting of over 51,289 Solidity lines. We have prevented 28 significant bugs. Full breakdown of our work can be found in this spreadsheet.
Continuous Formal Verification (Auditing and Formal Verification integrated into CI)
Following the success of the collaboration in the last 18 months, we offer to continue this service in the same format - new code is formally verified and manually reviewed. Our open-source CVL specification rules are checked using the Certora Prover and become publicly available when the code is released. The formal tests are also integrated into Aave’s CI system to continuously check changes introduced into the code. Reports are delivered upon demand at the end of each project. We have recently released a free version of the Certora Prover and the community can use this to validate the outputs.
The Aave and BGD teams will play a key role in rule writing going forward. These teams are highly technical and have insights into high-level properties of the protocol. Our team will review these rules and ensure the Certora Prover can formally prove these rules or find a bug. Our team will add more rules and manually review the code.
Governance Proposal Review
Following BGD’s suggestion to add a third party to the governance proposals verification process, we will allocate a dedicated team to review each proposal on the on-chain stage within 3.5 days.
Each proposal’s payload will be reviewed by the dedicated team, and we will verify that it does what it’s supposed to do according to its description/AIP. We will also check that there are no unwanted effects on the codebase, which is supposed to stay unchanged.
Our job will be done after a review by BGD at an earlier stage. BGD will also assist with onboarding to guarantee the highest quality of service.
Incident Investigation Support Services
Triaging and validating all the incoming bug reports for a massive protocol, such as Aave, can be highly time-consuming and distracting for the developing entities. Many of the reported issues turn out to be benign. However, at the time of the report, the severity and feasibility of bugs are still unknown. Therefore, it is crucial to investigate them with full seriousness and urgency. We offer to establish an incident investigation support team available 24/7 to support emergency cases. In every incident, we will write a rule that confirms or rejects the existence of a bug and later use it to test the validity of the fix. After every incident, we will update the specifications and incorporate the new tests in the CI.
In past commitments, we have played a crucial role in two critical incident responses. In one case, we concluded that there was no bug in the system. In another case, we identified a missing rule, wrote it, and used it to catch a tricky bug in the suggested fix before the code was deployed.
Specification
The annual price for the project is $1.5M: $1M is paid in GHO vested linearly over one year, and $500,000 is paid in Aave tokens vested linearly over one year, This amounts to 5200 AAVE according to the 30-DAY TWAP price of the asset. A 30-day termination is possible after a vote. We reduced the price of $2.7M from last year to reflect the bear market and inlined with the reduced project review capacity.
The Aave and the BGD team will also assist by writing their CVL rules.
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal description details a detailed, human-readable set of commitments (continuous formal verification, governance proposal review, incident investigation support) and specific payment terms ($1M GHO + $500k/5200 AAVE, vested linearly over 1 year, 30-day termination clause). However, the decoded on-chain actions only show the generic Aave governance execution pattern: a forwardPayloadForExecution call to route a payload for execution, and an execute()/fallback call on a separate payload contract address. Neither decoded action reveals the actual internal logic of the payload (e.g., token transfer amounts, stream creation, vesting schedules, or recipient addresses for the GHO/AAVE compensation). This is typical for Aave V3 governance payloads, where the actual effectful logic (transfers, stream creation) is encapsulated inside the payload contract's own code, which is referenced via a GitHub link but not decoded here as calldata. Because the decoded calldata is essentially a generic forwarding/execution call and does not expose the specific financial parameters described in the prose, I cannot verify or contradict claims like the $1.5M budget, the GHO/AAVE split, or the vesting terms directly against calldata values. There is no evidence of misalignment (no mismatched targets, no obviously wrong values), but there is also insufficient visibility into the actual fund movements to confirm exact alignment. Given this opacity, confidence is low and no specific discrepancy can be responsibly flagged since doing so would require speculation about the payload's internal contents beyond what's provided.
Generated by Kvorum
04Actions
- Target
- 0x9aee…2bc7
- Value
- 0 wei
- Function
- forwardPayloadForExecution((uint256,uint8,address,uint40))
- Arguments
{ "0": [ "1", "1", "0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5", "40" ] }- Calldata
- Target
- 0xea05…1dce
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 570x57ab…2922 | For | 144.3K | 27.09% | — | 3y ago |
| 320x329c…3ed4 | For | 103.1K | 19.34% | — | 3y ago |
| 130x13bd…8548 | For | 60K | 11.26% | — | 3y ago |
| 230x2331…7e73 | For | 60K | 11.26% | — | 3y ago |
| 2C0x2cc1…4df1 | For | 43.7K | 8.20% | — | 3y ago |
| B90xb933…8dd1 | For | 42.6K | 7.99% | — | 3y ago |
| EZezr3al.eth0x8659…7d0e | For | 38.1K | 7.15% | — | 3y ago |
| E40xe459…e666 | For | 20K | 3.75% | — | 3y ago |
| 0F0x0f11…e4c8 | For | 15.9K | 2.98% | — | 3y ago |
| 180x1855…98ba | For | 3.6K | 0.67% | — | 3y ago |
| 680x683a…6c02 | For | 1.6K | 0.30% | — | 3y ago |
| EA0xea17…6676 | For | 38.6 | 0.01% | — | 3y ago |
| 570x5762…a752 | For | 1 | 0.00% | — | 3y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedAave <> Certora Continuous Security Services89%
- aaveexecutedSecurity Services for Aave Current Infrastructure <> Certora88%
- aaveexecutedSecurity Services for Aave v4 <> Certora86%
- aaveexecutedContinuous Formal Verification86%
- aaveexecutedCertora Continuous Formal Verification85%
- aaveexecutedSigma Prime - Security Assessment Services for Aave72%