Certora Concord Equivalence Checker Funding
01Summary
Aave DAO proposes to contribute $50,000 USD in GHO to Certora for developing Concord, an open-source formal verification tool that proves smart contract upgrades preserve protocol behavior. This co-funded initiative with other protocols and Ethereum Foundation matching aims to reduce upgrade risk and audit overhead for Aave through bytecode-level equivalence checking.
- Type
- treasury allocation
- Funding
- $$50,000
Key changes
- One-time payment of $50,000 GHO to Certora (0x0F11640BF66e2D9352d9c41434A5C6E597c5e4c8) for Concord development(high)
- Aave becomes a founding sponsor of Certora Concord equivalence-checking framework alongside 3 other protocols(high)
- Access to formal verification tooling for proving compiler upgrades, optimizations, and refactors do not change protocol behavior(high)
- Ethereum Foundation will match $200,000 in ecosystem funding, doubling impact of $200,000 in protocol contributions(medium)
Generated by Kvorum
02Description
Simple Summary
We propose that the Aave DAO participate as a founding sponsor in the development of Certora Concord, an open-source equivalence-checking framework designed to formally verify that smart contract upgrades — including compiler upgrades, optimizations, and refactors — preserve protocol behavior.
Aave would contribute $50,000 USD as part of a co-funded ecosystem initiative, alongside other leading protocols, unlocking matching funding from the Ethereum Foundation.
This initiative introduces a new security primitive for Aave:
Formal, machine-checked guarantees that upgrades do not introduce unintended behavioral changes.
Motivation
Aave is a long-lived, continuously evolving protocol with:
- Frequent upgrades and governance proposals
- Increasing complexity (v4 and multi-chain deployments)
- Strong reliance on safe execution of changes
However, today:
- Even small changes (compiler upgrades, optimizations, refactors) can introduce subtle bugs
- These issues are difficult or impossible to detect via testing alone
- Post-audit changes often require expensive re-audits
This creates:
- Upgrade risk
- Operational overhead
- Slower innovation cycles
Proposed Solution: Certora Concord
Certora Concord is an equivalence-checking framework that:
- Compares two smart contracts at the bytecode level
- Proves whether they are behaviorally equivalent across all possible executions
- Produces counterexamples when differences exist
Unlike testing or fuzzing:
- Concord is exhaustive, not probabilistic
- Covers all inputs and execution paths
- Verifies externally observable behavior (state, calls, events)
In practice
- Compile the same contract with two compiler versions → prove equivalence
- Compare pre/post upgrade contracts → ensure no unintended behavior changes
This directly addresses core risks in Aave’s lifecycle.
Why This Matters for Aave
1. Safer Upgrades
Guarantee that:
- Compiler upgrades
- Gas optimizations
- Refactors
Do not change protocol behavior
2. Reduced Audit Overhead
- Avoid full re-audits for non-functional changes
- Focus audits only where behavior actually changes
3. Governance Confidence
- Provide stronger guarantees for AIPs
- Reduce the risk of introducing bugs through governance
4. Ecosystem Leadership
Aave becomes:
- A founding sponsor of a new verification primitive
- A leader in advancing formal security standards in DeFi
Scope of Work
Certora will:
- Develop Concord, integrated with the Certora Prover
- Provide:
- CLI tooling
- GUI interface for equivalence analysis
- Open-source the tool and documentation
- Maintain and extend Concord for at least 18 months
- Deliver:
- Real-world equivalence analyses
- Documentation and best practices
- Ecosystem-facing education and content
Funding Structure
This is a co-funded ecosystem initiative:
- 4 sponsors (including Aave): $50,000 each
- Total ecosystem funding: $200,000
- Ethereum Foundation match: $200,000
- Total project funding: $400,000
Aave’s contribution unlocks:
- Additional funding from the Ethereum Foundation
- Shared development costs across leading protocols
Timeline
- Initial production-ready version: 3 months
- Ongoing development & maintenance: 15+ months
Deliverables include:
- Tooling
- Documentation
- Case studies
- Continuous improvements
Benefits to Aave
Technical Benefits
- Early access to Concord tooling
- Ability to apply it directly to Aave upgrades
- Reduced upgrade risk and audit overhead
Strategic Benefits
- Recognition as a Concord Ecosystem Sponsor
- Visibility in:
- Technical publications
- Case studies
- Ecosystem initiatives
Financial Efficiency
- Leverages Ethereum Foundation matching → amplified impact per dollar
Specification
The proposal requests a one-time payment of $50,000 units of GHO paid to Certora for Concord development.
Certora Receiver: 0x0F11640BF66e2D9352d9c41434A5C6E597c5e4c8
References
- Implementation: AaveV3Ethereum
- Tests: AaveV3Ethereum
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal follows Aave's standard governance execution pattern: a single on-chain action that calls execute() on a payload contract, which internally performs the actual logic (in this case, presumably transferring $50,000 worth of GHO to the Certora receiver address). The decoded calldata provided only reveals this top-level execute() call and does not expose the internal transfer details, recipient address, or token amounts that the payload contract would execute via delegatecall. Because the underlying payload logic is not visible in the decoded actions, it is not possible to directly verify whether the $50,000 GHO payment, the recipient address (0x0F11640BF66e2D9352d9c41434A5C6E597c5e4c8), or any other specifics in the description match the actual on-chain execution. This is a common and expected limitation when reviewing Aave payload-based proposals, not necessarily an indication of a discrepancy. Given the lack of visibility into the payload's internal calls, confidence in this comparison is low, and per guidance, no discrepancies are flagged since we cannot substantiate a mismatch without deeper calldata (e.g., internal payload bytecode or a full trace). The description itself is internally consistent, detailed, and includes a direct link to the payload's implementation source code for further verification by delegates before voting.
Generated by Kvorum
04Actions
- Target
- 0x1e8c…004e
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 330x3320…3bb7 | For | 107.2K | 31.18% | — | 4mo ago |
| 2C0x2cc1…4df1 | For | 88.2K | 25.66% | — | 4mo ago |
| B90xb933…8dd1 | For | 53.9K | 15.68% | — | 4mo ago |
| EC0xecc2…6ac9 | For | 28.6K | 8.32% | — | 4mo ago |
| 360x3676…574d | For | 25K | 7.27% | — | 4mo ago |
| C00xc0d6…b802 | For | 20.2K | 5.87% | — | 4mo ago |
| 7A0x7ae1…e585 | For | 10K | 2.91% | — | 4mo ago |
| 070x0703…961b | For | 10K | 2.91% | — | 4mo ago |
| 4D0x4d26…7017 | For | 622.7 | 0.18% | — | 4mo ago |
| 3D0x3ddc…05b0 | For | 102.4 | 0.03% | — | 4mo ago |
| BC0xbcf0…46a5 | Against | 6 | 0.00% | — | 4mo ago |
| 2F0x2f2f…f78a | For | 5.2 | 0.00% | — | 4mo ago |
| BF0xbf57…0f42 | For | 4.6 | 0.00% | — | 4mo ago |
| 530x53da…c14b | For | 0 | 0.00% | — | 4mo ago |
| A90xa97c…ccc8 | For | 0 | 0.00% | — | 4mo ago |
07Forum
No forum thread is confidently linked to this proposal.