Appoint Securitize as a Whitelister to Aave Arc
01Summary
Aave Governance is voting to add Securitize, a regulated FINRA member Broker-Dealer and SEC-registered Transfer Agent, as a whitelister on Aave Arc. Securitize will conduct KYC/KYB/AML/CFT compliance checks and manage wallet access permissions for the permissioned institutional liquidity pool, helping institutions safely access Aave while meeting compliance requirements.
- Type
- governance change
Key changes
- Add Securitize (0x36b8A1D23BDc76092aD88A1c4Ef59fafD4931b03) as a PermissionAdmin on the Aave Arc PermissionManager contract via addPermissionAdmins() call(high)
- Grant Securitize authority to conduct KYC/KYB/AML/CFT checks on users and manage wallet whitelisting permissions (add/remove access) for Aave Arc(high)
- Enable Securitize to exercise multi-sig veto power on Aave Arc governance proposals that present excessive compliance risk, similar to guardian role on Aave V2(medium)
Notable concerns
- Centralized gatekeeping authority granted to a single private company over institutional access to Aave Arc
- Multi-sig veto power over Arc governance proposals concentrates compliance decision-making with Securitize
Generated by Kvorum
02Description
Simple Summary
Securitize asks the Aave Governance community to approve the appointment, adoption, and authorization of Securitize as a “whitelister” on the Aave Arc market.
Abstract
Securitize is the leading digital asset securities company. As a FINRA member Broker-Dealer and the first SEC-registered Transfer Agent operating with digital asset securities, Securitize is one of the most regulated firms in the entire digital assets industry.
Securitize has an excellent track record for providing comprehensive compliance services to a vast array of digital assets companies. Our proprietary investor passport, Securitize iD, is globally recognized and built upon Securitize’s battle-tested KYC/KYB/AML/CFT compliance program, allowing Securitize iD to be trusted by over 450K registered investors and over 200 issuers to date.
We have performed a detailed analysis and documented it here for the consideration of the Aave Governance community. We believe that Securitize satisfies all criteria necessary to be appointed as a whitelister for Aave Arc.
Motivation
The institutional appetite for DeFi is growing, but that hunger remains mostly unsatisfied due to compliance obstacles. In response, pragmatic DeFi communities like Aave launched permissioned versions of their services, like Aave Arc, and are wisely seeking regulated third parties, like Securitize, to facilitate user credential and access management.
As a whitelister, Securitize will function as one of the trusted gatekeepers for Aave Arc, ensuring that only wallets with verified credentials can access the permissioned liquidity pool. Therefore, institutions can safely leverage the transactional benefits of Aave — e.g., supply, borrow, and liquidate digital assets — while still abiding by their compliance requirements. Securitize believes that this is a monumental first step toward the eventual mass inclusion of institutions in the decentralized economy.
Specification
“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 addPermissions() and removePermissions() contract methods, respectively.
Rationale
The Aave Governance community voted on the Snapshot proposal with “YES” 389K AAVE (99.98%) and “No” 87 AAVE (0.02%)
Implementation
The implementation is described here
Proposal
The proposal executes a single call to the PermissionManager contract to add Securitize as PermissionAdmin in Aave ARC market:
IPermissionManager(0xF4a1F5fEA79C3609514A417425971FadC10eCfBE).addPermissionAdmins([0x36b8A1D23BDc76092aD88A1c4Ef59fafD4931b03]);
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The description states a single action: adding Securitize (0x36b8...b03) as a PermissionAdmin via addPermissionAdmins() on the PermissionManager contract (0xF4a1...cFbE). The decoded calldata shows exactly one action: a call to the Arc timelock's queue() function that schedules an execution targeting the same PermissionManager address, calling the same function signature addPermissionAdmins(address[]), with encoded calldata that decodes to the array containing the same Securitize address. The extra wrapping via the timelock's queue() mechanism is standard governance/timelock plumbing for Aave Arc (as referenced in the Implementation link to the arc-timelock repo) and not a substantive deviation from what the description promises — it is the mechanical means by which the described action is executed, not a different action. Value is 0 and delegatecall flag is false, consistent with a simple, non-value-transferring permission update. No mismatched addresses, function names, or parameters were found. Given the straightforward one-to-one match between the described action and the decoded action (accounting for the expected timelock queue wrapper), this proposal is consistent with its description.
Generated by Kvorum
04Actions
- Target
- 0xace1…1218
- Value
- 0 wei
- Function
- queue(address[],uint256[],string[],bytes[],bool[])
- Arguments
{ "0": [ "0xF4a1F5fEA79C3609514A417425971FadC10eCfBE" ], "1": [ "0" ], "2": [ "addPermissionAdmins(address[])" ], "3": [ "0x0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000100000000000000000000000036b8a1d23bdc76092ad88a1c4ef59fafd4931b03" ], "4": [ false ] }- Calldata
05Tally
Summed from votes
06Voters
No votes recorded yet.
07Forum
- ARC: Appoint Securitize as a Whitelister to Aave Arc ↗discourse · high confidence
Arguments for
- Securitize is one of the most regulated digital asset securities firms (FINRA member Broker-Dealer, SEC-registered Transfer Agent) and fully satisfies the Aave Arc white paper's criteria for a whitelister.— mike.rogers
- Securitize iD already provides battle-tested KYC/KYB/AML/CFT compliance to nearly 400K users and 200+ issuers, with proven integrations like Exodus and Centrifuge.— mike.rogers
- Securitize's on-chain attestation model (Securitize iD for DeFi) is designed to be interoperable, privacy-preserving, and gas-efficient, aligning with DeFi ethos while enabling institutional compliance.— mike.rogers
- Adding Securitize as an additional whitelister increases the pool of whitelisters for Aave Arc, which is beneficial given Arc is still early-stage.— eboado
- Appointing Securitize supports Aave's broader institutional DeFi vision by helping risk-conscious institutions gain comfort with compliance before engaging with permissionless DeFi.— mike.rogers
Arguments against
None surfaced.
Unresolved concerns
- Why would a user choose Securitize's KYC'd wallet route over simply connecting to the permissionless Aave protocol directly, given the rate differences on Arc?— fig
- Whitelisting KYC'd wallets for Aave Arc may contradict the decentralization ethos and increase regulatory burden on users.— fig
- Risk that onboarding through Securitize's whitelisted Arc could cannibalize growth of the core permissionless Aave protocol rather than being additive.— fig
- Need for Securitize to coordinate with existing whitelister Fireblocks to align on integrating different whitelisting approaches within the common Arc layer was flagged but not shown as resolved in the thread.— eboado
Notable participants
- mike.rogersProposer from Securitize who authored the detailed proposal and responded to community questions.
- eboadoAave Core Dev who gave supportive feedback and raised the need for coordination with Fireblocks, the existing whitelister.
- figCommunity member who raised critical questions about the value proposition and decentralization implications of the proposal.
- lucianoduqueReported the final Snapshot vote results showing near-unanimous community approval.
Generated by Kvorum
08Similar proposals
- aaveexecutedAdd SEBA Bank as a whitelister on Aave Arc84%
- aaveexecutedAdd Fireblocks as a whitelister on Aave Arc82%
- aaveexecutedAdopt The SEAL Safe Harbor Agreement65%
- aaveexecutedAdd dHEDGE Protocol to flashBorrowers64%
- aaveexecutedAuthorize the Guardian to hold the emergency keys for V264%
- aaveexecutedDeFi Saver Aave V3 FlashBorrowers Whitelist Part II63%
- aaveexecutedAave V3.5 Plasma Activation63%
- aaveexecutedAave V3.3 Soneium Activation63%
- aavedefeatedActivation of A-C Prime Foundation62%
- aaveexecutedAave V3.3 Sonic Activation62%