Add Fireblocks as a whitelister on Aave Arc
Fireblocks asks the Aave Governance community to approve the appointment, adoption, and authorization of Fireblocks LLC, a Fireblocks company, as a “whitelister” on the Aave Arc market.
Aave Arc is a “permissioned” version of the software underlying V2 of the Aave protocol that employs an additional smart contract layer to only allow “whitelisted” or “permissioned” users to engage with the protocol.
Only regulated entities that (a) employ KYC/KYB principles in accordance with FATF guidelines to identify and accept their clients; (b) have robust AML/CFT compliance programs; and (c) are currently in good standing with an active license/registration in the entity’s operating jurisdiction will be accepted as “whitelisters” on Aave Arc.
We believe that Fireblocks LLC, a Fireblocks company, satisfies all the qualification requirements to be a whitelister. We have performed a detailed analysis and documented it here for the consideration of the Aave Governance community.
DeFi is considered by institutional users to be one of the more complex markets to navigate across security, compliance, and risk perspectives. We are eager to be at the forefront of this transformational opportunity with Aave Arc by extending access to even our most compliance-conscious customers, who have been searching to engage with DeFi in a way that comports with their own internal requirements.
Approval of Fireblocks LLC can potentially also facilitate the integration of other “whitelisters” and institutions into instances of the Aave protocol. This may have multiple benefits, including the creation of sustainable governance practices for Aave Arc whitelisters and whitelister customers, as well as the enablement of benefits to the ecosystem, such as the onboarding of regulated fiat on/off ramps and protocol deployments connected to debit cards, high yield savings accounts and other innovative fintech products.
“Whitelisting” is the gatekeeping function performed by whitelisters on users of Aave Arc. The term refers specifically to the process of:
- Conducting KYC/KYB checks on the user;
- Onboarding the user with appropriate disclosures, terms, and conditions;
- Granting specific permissions (e.g., borrow, supply, liquidate) to the Ethereum wallet address(es) provided by the user.
In addition, Aave Arc whitelisters perform a similar role on Arc as guardians do on Aave V2. Specifically, whitelisters can use a multi-sig veto on governance proposals that add excessive compliance risk on the Aave Arc protocol. For example, existing whitelisters can veto the addition of a privacy coin if such a coin is impermissible in the relevant jurisdiction, or veto the addition of a whitelister that has a poor reputation for compliance.
The whitelisting is managed via a PermissionManager contract, in which whitelisters are designated as Permission Admins. Permission Admins are permitted to add or remove wallets grants to the Aave Arc market by calling
removePermissions() contract methods, respectively.
The Aave community voted on the Snapshot proposal with Yes 149.2k AAVE (98.33%) and No 2.54k AAVE (1.67%).
Test cases for an implementation are mandatory for AIPs but can be included with the implementation.
Executes the proposal deployed at:
The proposal executes the following:
- Adds Fireblocks as Permission Admin by calling addPermissionAdmins` on the PermissionManager contract.
- Unpause the pool by calling setPoolPause on the LendingPoolConfigurator contract.
- Transfers the EmergencyAdmin role of the system to the ArcTimelock's Veto DAO.
- Transfers ownership of the system to the ARC Market Multisig temporarily until handed over to Aave Governance.
Aave Arc Timelock
Aave Arc Timelock gives a guardian address the opportunity to cancel an approved governance action prior to its execution. The timelock implementation can be found here.
Copyright and related rights waived via CC0.
Your voting info