<h1>
<a name="arc-uiux-upgrade-governance-framework-1" href="#arc-uiux-upgrade-governance-framework-1"></a>[ARC] - UI/UX upgrade governance framework</h1>
<p>The Aave protocol is a decentralized ecosystem of smart-contracts running on several EVM networks. This ecosystem is permisionless and anyone with the required tech knowledge can freely use 100% of the Aave protocol features.</p>
<p>That being said, for a more accessible user experience, the Aave companies created the <a href="https://app.aave.com/">Aave application <span>11</span></a> allowing the interaction with the Aave protocol without technical knowledge.</p>
<p>To reinforce the decentralization of the application, the Aave app is deployed on IFPS and considering Flux hosting to avoid centralization of hosting,</p>
<p>also, the Aave app, is <a href="https://github.com/aave/interface">fully open source <span>2</span></a> and allows any developer to contribute to the improvement of the application for the benefit of the end-users.</p>
<p>As recently, we have witnessed multiple demands from third-parties to be integrated in the aave App (wallets, on-ramps etc…) The presented framework intends to provide governance guidelines to standardize the process of integration into the Aave App.</p>
<hr />
<h3>
<a name="title-arc-integrate-entity-into-the-aave-app-2" href="#title-arc-integrate-entity-into-the-aave-app-2"></a>Title [ARC] - integrate [Entity] into the aave app</h3>
<h3>
<a name="proposal-3" href="#proposal-3"></a>[Proposal]</h3>
<p>Brief presentation of the entity and ecosystem 250 words max</p>
<h3>
<a name="proposed-integration-4" href="#proposed-integration-4"></a>[Proposed integration]</h3>
<p>Brief presentation of the requested integration</p>
<p>examples:</p>
<ul>
<li>a wallet requesting a direct support on user onboarding</li>
<li>an onramp requesting the integration of an onramp widget</li>
<li>a notification system requesting to be integrated into user’s dashboard</li>
<li>a portfolio tracker requesting link in users dashboard</li>
</ul>
<p>In this section, the entity should detail which specific section of the app should be modified to integrate the entity.</p>
<h3>
<a name="current-and-proposed-integration-of-aave-in-the-entity-ecosystem-5" href="#current-and-proposed-integration-of-aave-in-the-entity-ecosystem-5"></a>[Current and proposed integration of Aave in the Entity ecosystem]</h3>
<ul>
<li>Is the Aave app highlighted in the entity application?</li>
<li>How does the integration benefit the Entity Aave’s current and potential future users?</li>
</ul>
<h3>
<a name="technical-integration-6" href="#technical-integration-6"></a>[Technical integration]</h3>
<ul>
<li>Link to Aave interface PR requesting the integration</li>
</ul>
<hr />
<p>This framework is intended to provide standardization of UI/UX integration of the Aave App.</p>
<p>The proposed governance process for a UI integration is to have each entity do a governance thread open for at least 5 days.</p>
<p>Then open a snapshot vote with a starting voting period of 24h in the future with at least 3 days open vote period considered valid with a 100k AAVE YAE vote quorum.</p>
<p>the proposed options for the snapshot must be YAE/NAY/ABSTAIN.</p>
<p>The Aave interface GitHub maintainers will then review the integration PR and provided they don’t detect security issues, will merge the PR.</p>
<p>In the case of a security issue detected with the PR and not discussed before the snapshot vote, the GitHub maintainers will open technical communication channels with the entity in an effort to allow the integration to be merged but will keep a veto right regardless of the governance process in the case the integration is considered harmful to Aave users security.</p>

[ARC] UI/UX upgrade governance framework 
  [ARC] - UI/UX upgrade governance framework 
 The Aave protocol is a

[ARC] UI/UX upgrade governance framework

<h1>
<a name="community-guardian-renewal-1" href="#community-guardian-renewal-1"></a>Community Guardian renewal</h1>
<p>The Aave V3 markets with the exception of the Polygon market are currently operated by a community guardian 6/10 multisig composed of members of the DeFi community.</p>
<p>The community guardian is a temporary tool to allow V3 markets to be upgraded following governance votes on Snapshot while an on-chain cross-chain governance module is implemented.</p>
<p>With numerous upgrades and assets onboarding upcoming in the Aave ecosystem, a slight renewal of the multisig signer might prove itself beneficial for Aave. the objectives of this renewal are:</p>
<ul>
<li>Onboard BGD Labs for technical support on transaction building</li>
<li>Reduce delays between Snapshot votes and executions of governance decisions.</li>
</ul>
<p>To reach these goals the new proposed community guardian is as follows:</p>
<p><strong>Joining</strong></p>
<ul>
<li>Ernesto Boado (BGD Labs)</li>
<li>Matthew Graham (Governance House)</li>
<li>Marc Zeller (Aave Companies)</li>
<li>Fernando Martinelli (Balancer Labs)</li>
</ul>
<p><strong>Staying</strong></p>
<ul>
<li>Coderdan (Aavegotchi)</li>
<li>Corbin Page (ConsenSys Codefi, Aave Grants DAO)</li>
<li>Gavi Galloway (Standard Crypto)</li>
<li>Meltem Demirors (Coinshares)</li>
<li>Hilmar Maximilian Orth (Gelato)</li>
<li>0xmaki</li>
</ul>
<p><strong>Leaving</strong></p>
<ul>
<li>Isa Kivlighan (Aave community, previously head of marketing on Aave Genesis team)</li>
<li>Imran Khan (DeFi Alliance, Aave Grants DAO)</li>
<li>Arthur0x (DeFiance Capital)</li>
<li>Dennison Bertram (Tally)</li>
</ul>
<p>This renewal of the Community Guardian signers, if met with governance approval, will contribute to Aave upgrades with less inertia.</p>
<p>The community Guardian is still considered a temporary solution, and its responsibilities will be progressively reduced. First, the existing cross-chain governance solution will be applied to Arbitrum &amp; Optimism. In parallel, BGD Labs is working on a more generalized solution that will apply to all the networks, if approved by the community via AIP vote.</p>
<p>The consequence of the governance V3 implementation will limit the Guardian’s responsibilities to a failsafe emergency actor allowed to freeze Aave markets or cancel AIPs if they’re deemed insecure or malicious.</p>
<p>A snapshot vote will be published 5 days after the publication of this thread allowing the community to vote on this Guardian renewal.</p>

Community Guardian renewal 
  Community Guardian renewal 
 The Aave V3 markets with the exception of the

Community Guardian renewal

<p>The upgrade of the Aave governance model is ready to be submitted to AAVE holders in the form of an AIP.</p>
<p>Vote for this AIP will start today (12/11/2020), if you want to participate, you’re invited to use the aave app UI :</p>
<aside>
  <header>
      
      <a href="https://app-v1.aave.com/governance/3-QmZFA1bsaBaq1tumw1oZj34qqbEcofKYXbVdbDqPvzb2ba" target="_blank">Aave app</a>
  </header>
  <article>
    

<h3><a href="https://app-v1.aave.com/governance/3-QmZFA1bsaBaq1tumw1oZj34qqbEcofKYXbVdbDqPvzb2ba" target="_blank">Aave - Open Source Liquidity Protocol <span>36</span></a></h3>

<p>Aave is an Open Source Protocol to create Non-Custodial Liquidity Markets to earn interest on deposits and borrow assets with a variable or stable interest rate. The protocol is designed for easy integration into your products and services.</p>


  </article>
  <div>
    
    
  </div>
  <div></div>
</aside>

<p>Direct vote with the contracts is also available, please refers to the dedicated documentation :</p>
<aside>
  <header>
      
      <a href="https://docs.aave.com/developers/protocol-governance/governance" target="_blank">docs.aave.com</a>
  </header>
  <article>
    <div></div>

<h3><a href="https://docs.aave.com/developers/protocol-governance/governance" target="_blank">Voting &amp; Governance <span>40</span></a></h3>



  </article>
  <div>
    
    
  </div>
  <div></div>
</aside>

<h2>AIP content in short</h2>
<ul>
<li>Implementation of the Aave Governance v2 smart contract</li>
<li>Implementation of voting delegation and proposal power delegation</li>
<li>Implementation of voting strategies with the inclusion of AAVE and StkAAVE</li>
<li>Addition of voting and proposition power delegations on AAVE and SktAAVE</li>
<li>Implementation of Executor entities</li>
<li>Implementation of the Guardian</li>
</ul>
<p>For further understanding of the new mechanisms introduced in this proposal, please refer to the following diagram:</p>
<p></p><div><a href="https://europe1.discourse-cdn.com/business20/uploads/aave/original/1X/8ddc71fce4a7bf99376590e38cbd4f4f754ab19a.jpeg"><div><span>image</span><span>1600×1174 130 KB</span></div></a></div><p></p>
<h2>Relevant links</h2>
<p>For more details on this AIP please refers to the associated ARC post : <a href="https://governance.aave.com/t/arc-activation-of-aave-protocol-governance-v2/1717">ARC: Activation of Aave Protocol Governance V2 <span>17</span></a></p>
<p>Please also find the content of the AIP-4 on the Aave public Github repo :</p>
<aside>
  <header>
      <a href="https://github.com/aave/aip/blob/master/content/aips/AIP-4.md" target="_blank">github.com</a>
  </header>
  <article>
    <h4><a href="https://github.com/aave/aip/blob/master/content/aips/AIP-4.md" target="_blank">aave/aip/blob/master/content/aips/AIP-4.md <span>25</span></a></h4>
<pre><code>---
aip: 4
title: Activation of Aave Protocol Governance V2
status: Proposed
author: Marc Zeller (@marczeller)
discussions: https://governance.aave.com/t/arc-activation-of-aave-protocol-governance-v2/1717
created: 2020-12-11
<span>updated: 2020-12-11
---</span>

<span>## AIP rationale</span>

Aave V2 governance is inspired by delegation-based governance models already on the market, while introducing 3 key innovations and a new layer of resilience:

The introduction of a new concept in DeFi governance - the <span>**segregation between voting and proposition power**</span> to increase control and ownership of voting rights for AAVE holders.
AAVE holders will have the choice between delegating proposal creation power to specialized actors while holding their voting rights; or even delegating them to another entity.

<span>**Voting strategies**</span> - The AAVE token exists and is used in the Aave ecosystem in a variety of ways. Through different voting strategies, AAVE in different forms can be used to vote and create proposals. In the initial implementation both AAVE and stkAAVE holders will have voting and proposal creation rights. Voting strategies can be upgraded at any time through a governance proposal to include other forms of AAVE (i.e. aAAVE, staked AAVE/ETH AMM shares, etc.)

<span>**Multiple executor entities**</span> - Different components of the ecosystem might have different needs for consensus and security. For example, changing the AAVE token logic itself might have a large impact on the ecosystem and is something that requires higher consensus than adjusting a risk management parameter. The Aave governance V2 splits the control of different entities within the Aave ecosystem between different executors with different execution delays (timelocks) and different consensus parameters. At the beginning there will be two different executors:
</code></pre>

  This file has been truncated. <a href="https://github.com/aave/aip/blob/master/content/aips/AIP-4.md" target="_blank">show original</a>

  </article>
  <div>
    
    
  </div>
  <div></div>
</aside>

AIP-4: Activation of Aave Protocol Governance V2 The upgrade of the Aave governance model

AIP-4: Activation of Aave Protocol Governance V2

<p>Hello,</p>
<p>Aave V3 is designed to embrace the multiverse vision and works best on multiple networks.<br />
That being said, bandwidth is not infinite and not all networks are equally secure or worth.</p>
<p>as we’re experiencing more and more demands to host Aave V3,</p>
<p>I think the governance might want to consider standardization of the process.</p>
<p>Here’s a proposal for a framework that is open to community discussions.</p>
<hr />
<h3>
<a name="title-arc-deploy-aave-v3-on-network-1" href="#title-arc-deploy-aave-v3-on-network-1"></a>Title [ARC] - Deploy Aave V3 on [Network]</h3>
<h3>
<a name="proposal-2" href="#proposal-2"></a>[Proposal]</h3>
<p>Brief presentation of the network and ecosystem 250 words max</p>
<h3>
<a name="technical-specifications-3" href="#technical-specifications-3"></a>[Technical Specifications]</h3>
<p>Brief technical presentation of the network including</p>
<ul>
<li>the number of nodes, if the network is an L2 how does anchoring on L1 work?</li>
<li>consensus mechanism</li>
<li>Infrastructure presence : does Chainlink,Thegraph and Etherscan support the network?</li>
<li>Ecosystem presence: Does Curve and an AMM/Dex are present?</li>
<li>L2 or alt-L1</li>
<li>presence or not of a messaging system allowing smart-contract communication between Eth L1 and the network (Needed for cross-chain governance)</li>
<li>is the network EVM compatible?</li>
<li>what are the most common public RPCs?</li>
<li>does your network testnet has a Faucet? does your mainnet has one for the native asset?</li>
<li>relevant data</li>
</ul>
<h3>
<a name="proposed-list-of-initial-collaterals-4" href="#proposed-list-of-initial-collaterals-4"></a>[Proposed list of initial collaterals]</h3>
<p>a list of proposed starting collateral on Aave V3</p>
<ul>
<li>Does the network has chainlink Price Feeds or is it in contact with Chainlink to deploy feeds for these assets?</li>
<li>do these assets have 30 days 2M$ daily volume minimum?</li>
<li>liquidity of these assets on main DEXs</li>
<li>main DEXs of the network</li>
</ul>
<h3>
<a name="incentives-5" href="#incentives-5"></a>[Incentives]</h3>
<p>Short brief if the network wants to do a Liquidity Mining program and include Aave V3 in it.</p>
<h3>
<a name="audits-security-6" href="#audits-security-6"></a>[Audits &amp; Security]</h3>
<ul>
<li>List of relevant security audits of the network</li>
</ul>
<ul>
<li>Has the network experienced outages, downtime or exploits/hacks?</li>
</ul>
<p>If yes:</p>
<ul>
<li>How many outages/downtime has your chain experienced in the last year? Please list the 5 last occurrences with dates and explanations</li>
<li>How long was the longest downtime?</li>
<li>What were the main issues &amp; have they been resolved?</li>
</ul>
<hr />
<p>Governance process :</p>
<ol>
<li>create a compliant with this framework post in the governance forum</li>
<li>after a minimum of 5 DAYS, create a snapshot vote on Aave snapshot with a clear yes, no, and abstain option and reach a quorum of 150k AAVE votes in total</li>
</ol>
<p>I invite the community to provide feedback on this proposal and once consensus is reached, a snapshot vote will be created to ask for the adoption of this standardization.</p>

[ARC] Aave V3 network integrations process Hello, 
 Aave V3 is designed to embrace the multiverse

[ARC] Aave V3 network integrations process

<h1>
<a name="arc-change-admin-role-of-optimism-and-arbitrum-v3-markets-1" href="#arc-change-admin-role-of-optimism-and-arbitrum-v3-markets-1"></a>[ARC] Change Admin role of Optimism and Arbitrum V3 markets</h1>
<p>aip: TBA</p>
<p>title: [ARC] Change Admin role of Optimism and Arbitrum V3 markets</p>
<p>status: Proposal</p>
<p>author: Marc Zeller <a href="https://github.com/marczeller">@marczeller <span>1</span></a>, Miguel Martinez <a href="https://github.com/miguelmtzinf">@miguelmtzinf <span>1</span></a></p>
<p>created: 20/09/2022</p>
<p><strong>Title:</strong></p>
<p><strong>[ARC] Change Admin role of Optimism and Arbitrum V3 markets</strong></p>
<p><strong>Simple Summary:</strong></p>
<p>Aave V3 Arbitrum &amp; Optimism markets are currently governed by the Community Guardian, a 6/10 elected multisig of 10 Aave community members with the responsibility to enforce community decisions on snapshot on-chain.</p>
<p>This ARC intends to replace the community guardian in favor of Aave governance contracts for the administration of Arbitrum &amp; Optimism V3 markets.</p>
<p><strong>Motivation:</strong></p>
<p>As cross-chain governance bridges received recent audits and in favor of more decentralization of Aave, this AIP intends to fade the community guardian role in Arbitrum and Optimism V3 markets in favor of Aave governance contracts.</p>
<p>This means that if this AIP is validated by Aave governance, every AIP concerning the Arbitrum and OP markets will require an On-chain AIP vote to directly modify the Aave V3 markets on these networks for example onboard a new asset or change an asset risk parameters.</p>
<p>The community guardian multisig always has been presented as a temporary solution in the wait of a cross-chain messaging solution allowing the Aave governance contracts to enforce directly onchain with no trusted intermediary for the governance decisions.</p>
<p>Fading the guardian role is a step forward in Aave protocol decentralization.</p>
<p>if this AIP gathers governance approval, the community guardian will keep an “emergency failsafe” role with the ability to freeze markets or cancel AIPs votes to protect the Aave markets in case of crisis or malicious AIPs.</p>
<p>The cross-chain governance bridge contract that allows more decentralization of the Aave protocol has been audited by ChainSecurity and Certora, and a report of the audit of this contract can be found in the technical link section of this AIP.</p>
<p><strong>Technical specifications:</strong></p>
<p>The cross-chain governance bridges is a set of smart contracts that serve as an extension of the Ethereum Aave Governance, receiving the approved actions by the community in Ethereum, and executing them in the target chain.</p>
<p>The details of the actions are described in a message which is passed from the L1 Aave Governance Executor contract using the native messaging mechanism of the chain:</p>
<ul>
<li>For Arbitrum, via <a href="https://github.com/OffchainLabs/arbitrum/blob/84e64dee6ee82adbf8ec34fd4b86c207a61d9007/packages/arb-bridge-eth/contracts/bridge/Inbox.sol#L324">creation of a retrayable ticket</a> in the <a href="https://etherscan.io/address/0x4dbd4fc535ac27206064b68ffcf827b0a60bab3f#writeProxyContract">Arbitrum Inbox contract</a> on Ethereum.</li>
<li>For Optimism, via <a href="https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/contracts/L1/L1CrossDomainMessenger.sol#L49">sending a message</a> using the <a href="https://etherscan.io/address/0x25ace71c97B33Cc4729CF772ae268934F7ab5fA1#writeProxyContract">OVM L1 Cross Domain Messenger contract</a> on Ethereum.</li>
</ul>
<p>The recipient of the bridged actions are the governance bridge contracts. Once actions reach these contracts, they are registered in the execution queue so they can be executed after a delay period. Queued actions are susceptible to being canceled for a period of time (e.g. grace period) by the Guardian. This is an “emergency failsafe”, a mechanism to protect the market in the target chain in case there is malicious or illegitimate action. This is a last-resort instrument that can be used by the Community Guardian Multisig.</p>
<p>A detailed specification of the contracts and workflow is outlined in this <a href="https://github.com/aave/governance-crosschain-bridges">repository <span>1</span></a>.</p>
<p><strong>Technical Links</strong></p>
<p>Optimism cross-chain governance bridge contract:</p>
<p><a href="https://optimistic.etherscan.io/address/0x7d9103572be58ffe99dc390e8246f02dcae6f611#code">https://optimistic.etherscan.io/address/0x7d9103572be58ffe99dc390e8246f02dcae6f611#code <span>1</span></a></p>
<p>Arbitrum cross-chain governance bridge contract:</p>
<p><a href="https://arbiscan.io/address/0x7d9103572be58ffe99dc390e8246f02dcae6f611#code">https://arbiscan.io/address/0x7d9103572be58ffe99dc390e8246f02dcae6f611#code <span>2</span></a></p>
<p>Cross-chain governance bridge Audit report:</p>
<p><a href="https://github.com/aave/governance-crosschain-bridges/blob/master/audits/26-07-2022_ChainSecurity_AaveL2BridgeExecutors.pdf">https://github.com/aave/governance-crosschain-bridges/blob/master/audits/26-07-2022_ChainSecurity_AaveL2BridgeExecutors.pdf <span>2</span></a></p>
<p><strong>Next steps:</strong></p>
<p>If the community approves this ARC, a snapshot vote will be published after a minimum of 5 days delay. If YAE is the majority outcome of the snapshot vote, the Community Guardian will change the administration of specified Aave V3 markets.</p>

[ARC] UI/UX upgrade governance framework

Community Guardian renewal

AIP-4: Activation of Aave Protocol Governance V2

[ARC] Aave V3 network integrations process

[ARC] Change Admin role of Optimism and Arbitrum V3 markets

Got something to add?