KVORUM
aaveSource: Aave governor v2 · #407

TokenLogic & karpatkey Service Provider Partnership

executedDec 19, 2023, 12:56 AM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Aave DAO onboards TokenLogic and karpatkey for 180 days to provide treasury management, strategic asset liquidity (particularly GHO), and Safety Module services. Combined budget is 400k GHO (220k to 0x58e6c7ab55aa9012eacca16d1ed4c15795669e1c and 180k to 0x3e4A9f478C0c13A15137Fc81e9d8269F127b4B40). Services include developing asset management architecture, managing liquidity incentives to support GHO re-pegging, and optimizing Safety Module performance.

Type
treasury allocation
Funding
$400000 GHO equivalent

Key changes

  • Create 180-day GHO streams totaling 400k GHO to TokenLogic and karpatkey (220k and 180k respectively) for financial services(high)
  • Develop non-custodial treasury management architecture with role-based access controls enabling asset diversification and yield optimization(high)
  • Lead Aave Liquidity Committee to manage liquidity incentives and support GHO price recovery through concentrated liquidity strategies on Maverick, Uniswap v3, and other platforms(high)
  • Model Safety Module performance, introduce additional asset categories for diversification, and reduce dependence on AAVE as insurance fund backstop(high)
  • Cancel TokenLogic's existing Orbit program GHO stream (StreamID 100017)(medium)
  • Include TokenLogic and karpatkey in Gas Rebate program for voting and deployment costs(low)

Notable concerns

  • Financial statements omitted from proposal due to budget constraints
  • Proposal relies on coordination with BGD Labs for technical implementation of Safety Module asset categories
  • Success of GHO re-pegging strategy dependent on market conditions and effectiveness of liquidity incentives
  • Significant discretion given to service providers for treasury operations and liquidity management decisions
Contracts0x9aee0b04504cef83a65ac3f0e838d0593bcb2bc70x58e6c7ab55aa9012eacca16d1ed4c15795669e1c0x3e4A9f478C0c13A15137Fc81e9d8269F127b4B40
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

1,272 words

Simple Summary

This AIP onboards TokenLogic & karpatkey to provide financial services to the Aave DAO for an initial period of 180 days, with a combined budget of 400k GHO.

Motivation

Overview

TokenLogic & karpatkey are responsible for delivering the following services to the Aave DAO:

  • Treasury Management;
  • Strategic Assets' Liquidity; and
  • Safety Module.

This funding will be used to support the TokenLogic and karpatkey teams to deliver the scope as outlined in the TEMP CHECK.

What to Expect

This proposal outlines a collaborative framework between TokenLogic and karpatkey to manage the Aave DAO’s treasury. Both parties will work in unison to ensure any future proposals within the agreed scope are jointly developed and endorsed.

Treasury Management

Develop the Architecture for Managing Aave's Assets

We aim to define a robust architecture for asset management. This architecture will enable non-custodial asset management, incorporating role-based access controls preapproved by the community that will enable treasury diversification and yield optimization. This system will ensure the Aave DAO retains full control over fund retrieval and permission management, facilitated through Aave’s “shortExecutor”. Overtime this will lead to fund management delegation and reduced governance overhead.

As the architecture for treasury management is being developed, the TokenLogic and karpatkey partnership will diligently progress with the necessary treasury operations, aligning them with the needs of the DAO and the stipulations of this proposal. All activities will be conducted in accordance with the established AIP model to avoid any disruptions.

Financial Security

A key objective is to secure sufficient funds to ensure a one-year runway, aligning with the DAO’s known budget and anticipated expenses.

This approach guarantees financial stability and an operational continuity for Aave DAO. Key components of this objective will include:

  • Bridging Aave funds between networks;
  • Migrating funds from Aave v2 to Aave v3; and
  • Swap asset to align expenses and holdings.

Do note, financial statements have been omitted in order to present a cost conscious, high-impact solution within the current budget. If the Aave DAO wishes to explore having financial statements as part of a broader proposal, we can later expand the funding to include the additional scope.

Strategic Assets' Liquidity

TokenLogic and karpatkey will lead the Aave Liquidity Committee (ALC) and oversee he management of liquidity incentives and Aave-owned liquidity in alignment with Aave’s strategic asset goals. One of the main focus areas will be supporting GHO’s token price recovery. Key initiatives include:

  • Foster concentrated liquidity profiles that support GHO’s price movement towards re-pegging, while maintaining its utility across a full range AMMs.
    • Utilize Maverick’s design to automate liquidity concentration as prices evolve, while reducing the friction caused by liquidity fragmentation in concentrated boosted pools.
    • Optimize incentives on Uniswap v3 for concentrated liquidity, tailored across three categories: fees, GHO, and other USD token liquidity. Prioritize USD liquidity, particularly when GHO is off-peg.
    • Continuously review and adjust incentives on platforms that yield the best results.
    • Initial focus is on skewed liquidity distribution to support regaining the peg. However, it is paramount to ensure existing liquidity providers find sufficient utility on their GHO funds (through sustainable strategies that make use of Aave’s AURA holding) to mitigate selling pressure.
  • Post-Repeg Strategy for GHO, explore sustainable approaches that preserve the token’s value and expand its functional role within the ecosystem:
    • Implement optimized liquidity strategies through Maverick and Merkl to achieve balanced liquidity and deeper market depth.
    • Enhance GHO’s extrinsic demand by incentivizing stableswap pools, such as Balancer’s GHO pools, leveraging Aave’s capacity for a significant TVL increase.
    • Work with Gyroscope to deploy liquidity pools that align with Balancer’s architecture, using their advanced bonding curve model for concentrated liquidity AMMs. This strategic integration will use Aave-owned AURA to enhance GHO’s price stability.
    • Deploy and incentivize markets beyond USD-pegged assets, including ETH, ETH LSTs, EUR, and Real World Assets (RWAs). This diversification will open up new investment avenues and attract liquidity providers with varying risk appetites.
    • Collaborate closely with Aave and specialized risk service providers to support the deployment and configuration of the GHO Stability Module (GSM). This coordination will focus on fine-tuning critical parameters, taking into account prevailing market conditions. Our objective is to integrate the GSM with managed capacity, potentially even before GHO achieves full re-pegging, as a strategic mechanism to foster price stability.
  • To optimize the utilization of surplus votes resulting from incentivized liquidity, we propose to leverage excess voting power effectively, transforming it into tangible rewards through participation in voting markets such as Curve, Convex, Balancer, and Aura.

For operational simplicity and alignment with the DAO’s strategic objectives, evolving the GHO Liquidity Committee into the Aave Liquidity Committee is a logical step.

Saftety Module

As part of the scope, karpatkey and TokenLogic will focus on modeling the SM performance during shortfall events and present proposals to diversify asset categories. This proposal will feature how the DAO can utilize the vlAURA position, realize synergies between GHO Liquidity and overall attempt to reduce the DAOs insurance fund spend.

The below outlines at a high level what we intend to deliver:

  • Introduce additional asset categories to promote diversification and reduce the dependence on AAVE as a backstop for the protocol.
    • Initial parameter configuration will incorporate feedback from Chaos Labs & Gauntlet.
    • We will explore the feasibility of including GHO LP assets and harness rewards from other protocols.
    • Technical lift associated with creating new categories will be performed by BGD Labs, with a security audit, if required.
  • 90-day emission forecast will be provided ahead of each emission cycle for community feedback. TokenLogic and karpatkey will prepare the payload to extend the SM emissions for @bgdlabs for review.
    • Iterative emission cycles enable the DAO to target specific asset categories and improve the correlations between bad debt potential whilst maintaining a base level of insurance. The proposal will feature the ability to reward some categories with non AAVE rewards, like GHO, to support adoption and velocity.
  • Capital efficiency, optimize emission schedules to balance attracting and retaining new deposits for each respective category. For example the APR on stkAAVE is expected to continue being reduced given the recent GHO Mint Discount utility being added and the introduction of new categories.
  • Analytics, a dashboard will be created/maintained that tracks the effective coverage of the insurance fund under various market conditions. The deposit value, composition of assets, APR over time and impact on the DAOs runway will all be readily available for the community to view. This is expected to create transparency and provide insight into the performance of the SM as an effective insurance fund for the DAO.

Specification

The AIP will call the createStream() method of the IAaveEcosystemReserveController interface to create two 180-day streams for 220k and 180k of GHO.

The following address will be the recipient of the 220k GHO stream: Address: 0x58e6c7ab55aa9012eacca16d1ed4c15795669e1c

The following address will be the recipient of the 180k GHO stream: Address: 0x3e4A9f478C0c13A15137Fc81e9d8269F127b4B40

TokenLogic and karpatkey are to be included in the Gas Rebate program that reimburses on-chain voting, calling revenue contracts, deployment and testings costs.

TokenLogic and karpatkey will jointly lead the GLC for the duration of the service provider contract.

Upon execution of this AIP, TokenLogic's Orbit program GHO stream (StreamID 100017) will be cancelled.

Disclaimer

TokenLogic and karpatkey receive no compensation beyond Aave protocol for the creation of this proposal. TokenLogic and karpatkey are both delegates within the Aave ecosystem.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal description makes several specific, concrete claims: creation of two GHO streams (220k and 180k) with named recipient addresses, inclusion of TokenLogic/karpatkey in the gas rebate program, joint GLC leadership, and cancellation of an existing Orbit stream (ID 100017). However, the only decoded on-chain action available is a single call to forwardPayloadForExecution, which forwards execution to a separate payload contract (0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5) referenced by payload ID 1. This is the standard Aave governance pattern where the AIP's on-chain action merely triggers a pre-deployed payload contract that contains the actual logic (stream creation, cancellation, role assignments, etc.). Because the payload contract's internal calls are not decoded/exposed in the provided calldata, it is not possible to directly verify whether the specific dollar amounts, recipient addresses, stream cancellation, or committee assignments described in the prose are faithfully implemented on-chain. There is no evidence of a mismatch — the single forwarding action is fully consistent with what a proposal of this type would do — but the lack of decoded detail in the target payload means confidence in a full line-by-line verification is low. No contradictions were found between the visible calldata and the description; the assessment defaults to consistent given the absence of any conflicting evidence, but this should be treated with appropriate caution given the limited visibility into the forwarded payload's actual instructions.

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0forwardPayloadForExecution((uint256,uint8,address,uint40))chain 0x1
Target
0x9aee…2bc7
Value
0 wei
Function
forwardPayloadForExecution((uint256,uint8,address,uint40))
Arguments
{
  "0": [
    "1",
    "1",
    "0xdAbad81aF85554E9ae636395611C58F7eC1aAEc5",
    "39"
  ]
}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.