KVORUM
aaveSource: Aave governor v2 · #71

Approval of BGD contribution to Aave

executedMay 6, 2022, 05:59 PM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorumclaude-haiku-4-5

Aave governance approves a mandate to engage BGD Labs for technical development work. The proposal updates Aave v2 Ethereum ecosystem reserves with streaming capabilities, releases 1.2M USDC, 1M USDT, 1M DAI and 8,400 AAVE upfront (40% of budget), and creates 15-month payment streams for 4.8M USDC and 12,600 AAVE.

Type
treasury allocation
Funding
$Approximately 7.2 million USD (3.2M upfront in stablecoins plus streaming component)

Key changes

  • Updates Aave v2 Ethereum ecosystem reserve and AAVE ecosystem reserve with common implementation contract featuring streaming capabilities(high)
  • Establishes AaveEcosystemReserveController as sole entity controlled by Aave governance with authority to transfer, approve funds, create and cancel streams(high)
  • Releases 40% of BGD Labs budget upfront: 1,200,000 USDC, 1,000,000 USDT, 1,000,000 DAI, and 8,400 AAVE(high)
  • Creates 15-month duration payment streams for 4,800,000 USDC and 12,600 AAVE to BGD Labs(high)

Notable concerns

  • Proposal implementation underwent extensive security procedures including formal verification by Certora, Slither analysis, community security review, and full test coverage
Contracts0x1e12071bd95341aa92fcba1513c714f9f49282a40x3d569673daa0575c936c7c67c4e6aeda69cc630c0x1aa435ed226014407fa6b889e9d06c02b1a12af3
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

402 words

Summary

This proposal acts as a mandate from the Aave community to engage with BGD Labs for the technical work defined on the Aave governance forum here and already pre-approved by the Aave community via Snapshot here.

As a result of this proposal, the proposed budget will be approved to a BGD-controlled address: 40% of the total transferred upfront, and the rest only defined as a claimable stream during the following 15 months. In order to enable this mandate, this proposal also includes what can be considered as the first development on the list of tasks proposed: the update of the ecosystem's reserve of Aave v2 Ethereum to enable stream of funds, to be used now by BGD, but also by anybody else in the future.

Motivation

A full rationale of the proposal can be found on the Aave governance forum post here, but the main motivation is the onboarding of another technical provider to the decentralized Aave ecosystem.

Specification

A full specification of the contracts update enabling this mandate can be found on the BGD Labs github here, together will all the security procedures applied, and the implementation of the governance payload. In summary, the proposal:

  • Updates the Aave v2 Ethereum ecosystem reserve and the AAVE ecosystem reserve with a common implementation contract, with streaming capabilities.
  • Sets as fundsAdmin of those ecosystem reserves a new AaveEcosystemReserveController contract, controlled directly by the Aave governance and the only entity able to transfer and approve funds, create streams, and cancel streams.
  • Releases the 40% of the budget defined upfront: 1'200'000 USDC, 1'000'000 USDT, 1'000'000 DAI and 8'400 AAVE.
  • Creates 15-months duration streams: 4'800'000 USDC and 12'600 AAVE.

Security

As mandatory with any change on a running Aave smart contract, extensive security procedures have been applied to the proposal payload and the changes included. A full security report can be found here, but as summary:

  • Full test coverage via units tests in the Forge environment.
  • Security review from Aave community members.
  • Minimal changes from the Sablier's v1 logic used as base for the streaming capabilities. The original codebase is audited and battle tested (running in production with meaningful funds for a long time).
  • Set of properties (formal verification) by Certora.
  • Slither analysis of the codebase.

Implementation

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

1 total
#0fallback()chain 0x1
Target
0x1e12…82a4
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters32
VP participating522.9K
Outcome (current)For
Current support100%

06Voters

32 total

No votes recorded yet.

07Forum

AIForum synthesis by Kvorumclaude-haiku-4-5
sentiment · favorablethread · constructive

Arguments for

  • BGD founding members possess deep technical expertise and have been core to Aave's inception and evolution, making them the best-positioned team to handle critical development tasks.— Jordan, dhadrien, stani, Alex_BertoG, JohannEid
  • The proposal addresses a critical gap in dedicated technical contributors with sufficient knowledge and commitment to manage complex core development and ecosystem tasks that currently lack strong leadership.— eboado, pakim249, samyak, JLue
  • The compensation structure of $8 million in stablecoins and 21,000 AAVE over 15 months is reasonable and affordable given the protocol treasury's size, growth rate, and the scope of critical tasks being covered.— Jordan, eboado, fig, JLue
  • The team demonstrates strong values alignment with Aave including security-first mindset, compromise, expertise, responsible freedom, and commitment to open-source code benefiting the DAO.— Jordan, Shelly, inkyamze, samyak
  • BGD's comprehensive task list covers essential ecosystem maintenance, V3 migration support, governance improvements, and security coordination that would otherwise require dozens of developers at greater cost.— pakim249, fcmartinelli, Shelly, raho
  • This proposal exemplifies true decentralization by keeping founding team members engaged as community service providers rather than losing their expertise to other protocols or external ventures.— stani, dhadrien, FoxSteven, 0xMaki
  • Existing external security and risk partners including Certora, Gauntlet, and Chainlink have endorsed the team's professionalism and capability to execute the proposed work.— Shelly, inkyamze, JohannEid

Arguments against

None surfaced.

Unresolved concerns

  • Whether the 15-month engagement duration is appropriate or if more frequent evaluation checkpoints would be needed to hold the team accountable.— pakim249, fig
  • Detailed breakdown of how the $8 million budget will be allocated across salaries, infrastructure, deployment costs, and attracting additional talent remains unspecified.— EzR3aL
  • Risk that regulatory authorities could view BGD as THE developers and maintainers of Aave, potentially creating regulatory exposure for both the team and the protocol.— G-Blockchain
  • Whether the team should expand its scope to include growth, partnerships, and community components beyond purely technical development.— Asango
  • Uncertainty about how collaboration opportunities will be structured for other community members and external teams wanting to contribute alongside BGD.— siddhant

Notable participants

  • eboadoBGD co-founder and proposal lead; provides detailed responses on compensation, engagement model, regulatory concerns, and budget allocation throughout the thread.
  • EmilioBGD co-founder; referenced throughout as a trusted core developer and strong technical leader known for Aave expertise and security focus.
  • AndykoBGD co-founder; previously Head of Backend/Frontend at Aave Genesis Team; key technical contributor to the proposal.
  • JordanFormer Aave COO providing strong endorsement based on 4 years of working alongside the BGD founders and validating the reasonableness of costs relative to Gauntlet benchmarks.
  • staniAave founder providing full support and validation of team capability; emphasizes alignment with decentralization values and commitment to community support.
  • pakim249Active community member raising constructive concerns about evaluation metrics and accountability mechanisms over the 15-month period.
  • ShellyCertora representative endorsing BGD's professionalism, security orientation, and planning to collaborate closely on security and code correctness.
  • inkyamzeGauntlet representative confirming collegial interactions and endorsing the team's embodiment of stated mission values including security-first approach.
  • JohannEidChainlink head of integration attesting to 2 years of working with BGD members and their unparalleled contribution to Aave with zero security issues.
  • figCommunity member asking clarifying questions about team expansion, 15-month duration rationale, and expressing concern about 7% treasury stablecoin allocation.
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Open the thread ↗