4626 Proposal - Cycle 7 Ajna Governance
Request
Receiving Address: (`0x9A22889a2Bb9712E3401de26985d66Aa776791cF`)
AJNA Amount: (`5,000,000`)
Applicant and Team Information
Applicant Name & Contact: @Prototech_Labs
About the team: A team of ex-MakerDAO engineers closely familiar with the Ajna codebase. We have provided a number of security reviews and conducted comprehensive invariant testing for the Ajna team already.
Project Information
1. What is it?
A bespoke ERC-4626 Ajna vault, fully compliant with the ERC-4626 standard, designed to enable seamless frontend integration with Ajna pools.
This vault abstracts away Ajna’s complexity by providing a standard ERC-4626 interface to manage lender funds and allocate them to appropriate Ajna buckets. It automatically rebalances user deposits into the highest-yielding buckets, so DeFi frontends can offer a simple, plug-and-play lending experience without requiring custom Ajna integrations. In short, it lowers the barrier for frontends and users by introducing a familiar, widely adopted standard.
2. What problem is being solved, and how?
Ajna’s complexity has been an obstacle to user adoption. By introducing an ERC-4626-compliant vault, this solution removes the need for bespoke frontend development and makes Ajna accessible through a standard interface.
The design uses a permissioned keeper to manage liquidity between a buffer contract and earning buckets, guided by an oracle for accurate market pricing. Running the vault requires operating a keeper service and sourcing reliable oracle feeds. Unlike earlier approaches such as the ARK, which lacked ERC-4626 standardization, this implementation aligns with current DeFi standards and ensures easier adoption across frontends and aggregators.
3. What are the deliverable(s)?
-
ERC-4626 Development & Supporting Documentation
-
Interface Guide for Frontend Integrations
-
Keeper Development & Operations Guide