Terms specific to this repository and proposal development workflow.
- Payload
- Config Engine
- Generator
- Feature Module
- Snapshot Diff
- Fork Testing
- Default Test Suite
- PayloadsController
- AIP (Aave Improvement Proposal)
- ARFC (Aave Request for Comments)
- Direct-to-AIP
- Proposition Power
- Voting Network
- Catapulta
- Base Payload Classes
- Config File Mode
Smart contract that executes protocol changes on a specific chain. Inherits from base classes like AaveV3PayloadEthereum. Deployed on the target chain.
Standardized interface (IAaveV3ConfigEngine) for protocol parameter updates. Provides functions like newListings(), capsUpdates(), rateStrategiesUpdates(). External dependency from aave-v3-origin.
CLI tool (npm run generate) that creates proposal files interactively. Generates .sol, .t.sol, .s.sol, and .md files based on user prompts.
Generator component that handles specific update type (e.g., caps, rates, asset listing).
Automated before/after comparison of protocol state. Generated by defaultTest() and saved to diffs/ directory as markdown.
Running tests against a copy of live blockchain state at a specific block. Uses Foundry's vm.createSelectFork().
The defaultTest() function that runs comprehensive validation: captures state, executes proposal, generates diff, validates parameters.
Governance contract that registers and executes approved payloads. Deployed on each target chain.
Formal on-chain proposal submitted to governance. Executable smart contract that modifies protocol parameters when approved.
Pre-proposal discussion on governance forum to gather community feedback before creating AIP.
Streamlined path skipping ARFC/Snapshot. Used for: time-sensitive updates, routine maintenance, extensions of approved proposals.
Blockchain where voting occurs. Default: Avalanche (for gas savings).
- README.md - Repository overview and architecture
- Generator Guide - Using the generator CLI
- TESTING_GUIDE.md - Testing workflows and infrastructure