CoinYQ Dossier

From finding a lender to deciding how shared capital bears losses

ETHLend began by trying to pair one lender with one borrower. Aave escaped that bottleneck by pooling capital, then kept rebuilding the machinery through V1, V2, V3 and V4. The token also changed: LEND became AAVE and moved governance onchain. Yet the protocol’s real control surface is wider than a ballot—executors hold permissions, Guardians can halt operations within their emergency mandates, and today’s backstop is split between legacy AAVE staking and reserve-specific Umbrella pools.

The order book that could not become a market

In November 2017, Stani Kulechov’s ETHLend sold LEND to fund a peer-to-peer lending system. Aave Labs later described the sale as raising $16.2 million; because that number is a project retrospective, it should be read as the company’s account rather than an audited fundraising finding.

The early design asked lenders and borrowers to find matching terms. During the 2018–2019 bear market, the team took the Finnish word Aave—ghost—and replaced bilateral orders with shared liquidity. January 2020’s V1 made the decisive move: suppliers received aTokens, borrowers drew from pools, and flash loans used transaction atomicity instead of conventional collateral.

That lineage matters because “Aave” does not identify one immortal contract. V2 arrived in December 2020; V3 began on six networks in March 2022 and later reached Ethereum; V4 opened on Ethereum in March 2026. Older deployments could be frozen or remain available separately, as V1’s 2022 freeze shows.

A hundred LEND enter; one AAVE leaves

Aavenomics compressed 1.3 billion LEND into a 16 million AAVE design. The conversion rate was 100 LEND for 1 AAVE: 13 million were reserved for migrating holders and 3 million were created for a governance-controlled Ecosystem Reserve.

AIP-1 began the migration in 2020 and paid initial Safety Module incentives, explicitly without slashing. AIP-7 activated legacy slashing in January 2021. The token therefore acquired two distinct jobs—governance power and optional exposure as protocol backstop—rather than ownership of the lending pools.

The migration did not remain open forever. On 9 May 2026, proposal 480 disabled the migrator and returned about 302,000 unclaimed AAVE to the Ecosystem Reserve. The rescue implementation now makes migrateFromLEND revert. A historical 100:1 promise is no longer a current redemption route.

Treasury control is also not treasury ownership. Governance can allocate Ecosystem Reserve and Collector assets through proposals, but an AAVE balance does not provide a pro-rata withdrawal, dividend or legal claim on those assets.

A vote crosses networks, then meets the keys

Governance V3 finished its operational migration on 25 December 2023. Its core lives on Ethereum, while voting machines and payload controllers can sit on other networks. Storage proofs carry snapshotted Ethereum voting power; a.DI carries messages; executors finally call contracts after the appropriate delay.

This design separates an open trigger from privileged execution. Anyone may register a payload and, after approval and timelock, call executePayload. But only a queued governance message reaches an Executor that actually holds protocol permissions. Owners can update portals, strategies or executors through governance-controlled roles, and several contracts remain upgradeable.

Two emergency groups sit beside the token vote. The 5-of-9 Governance Guardian can cancel proposals or unexecuted payloads. The 4-of-7 Protocol Guardian holds EMERGENCY_ADMIN powers for pausing pools and freezing reserves. The current permission inventory also records cross-chain adapters, automation and bounded service-provider roles.

AAVE, stkAAVE and aAAVE may supply or delegate voting power, but concentration, thresholds and participation determine outcomes. “Token-governed” is accurate only when paired with this machinery; “every action is decided directly by all holders” is not.

Umbrella changes who stands beneath the shortfall

The original Safety Module made stkAAVE and related assets a broad last-resort pool. It remains visible: current help lists legacy AAVE and ABPT, with up to 20% slashing after an onchain governance vote, and legacy GHO with slashing currently set to 0%. Those settings can change.

Umbrella, active since 5 June 2025, narrows the match between risk and capital. Aave aTokens or GHO can be staked for a particular reserve and network. Automated slashing lowers the stake token’s asset backing; contract documentation then describes a separate, permissioned coverage step through the Collector. It is more precise than calling the pool an automatic insurance payout.

V4’s Hub-and-Spoke launch adds another layer of configurable risk: shared hubs hold liquidity while spokes define borrowing and liquidation rules. Aave Labs’ launch is evidence that the contracts and interface went live, while its market-share and faultless-resilience claims remain promotional assertions unless independently measured.

Pooling capital let Aave leave behind the search for an individual lender. Each generation then had to specify who could change the conditions, what could be stopped, and which funds would meet a shortfall. Following the roles of users, voters, delegates, developers, service providers, executors and Guardians is how a reader can assess each new claim of safety or decentralization.

How the project changed

  1. 2017-11
    ETHLend funds a peer-to-peer lender

    Aave Labs retrospectively says Stani Kulechov’s ETHLend ICO raised $16.2 million; the bilateral matching model later proved difficult to scale.

  2. 2018–2019
    The ghost leaves order books for pooled liquidity

    During the bear market the project took the Aave name and rebuilt lending around shared pools rather than individual lender-borrower matches.

  3. 2020-01
    Aave V1 opens pooled lending

    V1 launches with aTokens and flash loans, turning the ETHLend experiment into a reusable liquidity market.

  4. 2020-10
    LEND begins converting to AAVE

    AIP-1 implements the 100:1 migration and starts Safety Module incentives without activating slashing.

  5. 2020-12
    V2 becomes a separate deployment

    V2 adds collateral swaps, debt tokenization and other changes; older markets do not vanish merely because a new version exists.

  6. 2022-03
    V3 starts on six networks

    The first V3 deployments add isolation mode, caps and efficiency controls; Ethereum V3 follows on 27 January 2023.

  7. 2023-12-25
    Governance V3 completes its handover

    The final migration proposal transfers operational permissions and voting-asset compatibility to the multi-network governance system.

  8. 2025-06-05
    Umbrella becomes active

    Reserve-matched aToken and GHO staking begins alongside, rather than instantly erasing, the legacy AAVE Safety Module.

  9. 2026-03-30
    V4 launches on Ethereum

    Three Liquidity Hubs open with Hub-and-Spoke markets while V3 deployments remain relevant.

  10. 2026-05-09
    The LEND exit finally closes

    Proposal 480 disables the old migrator and returns about 302,000 unclaimed AAVE to the Ecosystem Reserve.

Evidence and primary sources

Last evidence review: 2026-09-04

What is Aave?

Aave is a family of non-custodial lending deployments rather than one contract that has simply been replaced in place. Users supply assets to smart-contract markets, receive claim tokens, and may borrow within governance-set collateral and risk limits. V3 remains deployed across networks; V4 launched on Ethereum on 30 March 2026 with shared Liquidity Hubs feeding specialized Spokes.

AAVE is the Ethereum governance token descended from ETHLend’s LEND. Eligible AAVE, stkAAVE and aAAVE balances or delegations create proposal and voting power. That power works through a contract system with timelocks, executors, cross-chain messaging, elected Guardians and bounded service-provider roles; a wallet balance is not direct custody of markets or a share of Aave Labs.

What problem does Aave solve?

ETHLend matched individual lenders and borrowers, an approach Aave Labs says was difficult to scale. The rebuild pooled liquidity so one supplier did not need to find one borrower, but pooled lending introduced a different problem: collateral factors, oracle inputs, liquidation rules, asset caps and upgrades must be changed without handing every emergency to one operator.

Aave’s successive versions are answers to that coordination problem. V2 changed debt and collateral operations, V3 separated risk with caps and isolation, and V4 shares hub liquidity among differently configured spokes. Each gain in capital coordination also increases the importance of governance code and named emergency permissions.

How does Aave work?

Suppliers deposit into a market and receive aToken or version-specific claim accounting; borrowers draw from pooled liquidity against collateral. Interest and liquidation depend on utilization, oracle prices and parameters. V4 changes the topology: Liquidity Hubs hold shared capital while Spokes define collateral, borrowing and liquidation rules.

Governance V3 keeps its core on Ethereum. Eligible voting power is snapshotted, voting may occur on a selected voting network, and results return through Aave Delivery Infrastructure. After quorum and vote-differential tests, payloads wait in level-specific timelocks and execute through permission-holding contracts. Guardians can cancel or pause within defined scopes.

Safety also has two eras. Legacy stkAAVE remains listed with governance-triggered slashing of up to 20%. Umbrella, live since 5 June 2025, primarily stakes reserve-matched aTokens or GHO; a slash reduces the stake token’s asset backing, then permissioned coverage functions move funds through the Collector to address deficits.

Key facts

  • ETHLend began in 2017 as peer-to-peer lending; Aave V1 launched pooled markets in January 2020.
  • LEND converted at 100:1 into a 16,000,000 AAVE design: 13,000,000 for migration and 3,000,000 for the Ecosystem Reserve.
  • Proposal 480 closed the LEND migrator on 9 May 2026 and redirected about 302,000 unclaimed AAVE to the Ecosystem Reserve.
  • Aave V2 launched in December 2020; V3 first deployed on six networks in March 2022 and reached Ethereum on 27 January 2023.
  • Aave V4 launched on Ethereum on 30 March 2026 with three Liquidity Hubs and specialized Spokes.
  • Governance V3 completed migration on 25 December 2023; its core, voting machines, a.DI, payload controllers and executors divide voting from execution.
  • Current voting power can come from AAVE, stkAAVE or aAAVE held or delegated on Ethereum, subject to proposal thresholds and quorum rules.
  • Current emergency structure separates a 5-of-9 Governance Guardian from a 4-of-7 Protocol Emergency Guardian.
  • Umbrella is live, but the current stake page still lists legacy AAVE, ABPT and GHO modules; legacy stkAAVE slashing is stated as up to 20%.
  • AAVE voting does not by itself grant equity, dividends, redemption, intellectual-property ownership or a pro-rata claim on DAO treasury assets.

Official links

Categories

Related coins

Frequently asked questions

Did Aave begin as a liquidity-pool protocol?

No. ETHLend started with direct peer-to-peer matching. During 2018–2019 the project adopted the Aave name and rebuilt around pooled liquidity; V1 launched that model in January 2020.

Can LEND still be converted into AAVE?

No. The 100:1 migrator was disabled by executed proposal 480 on 9 May 2026. Its implementation now rejects migration and reports the process ended.

Does one AAVE equal one vote?

Voting power is proportional to eligible AAVE, stkAAVE or aAAVE held or delegated on Ethereum, but proposal creation, quorum and vote-differential thresholds still apply. Offchain forum and Snapshot stages are not the final onchain execution.

Can any user execute a governance payload?

Anyone may trigger executePayload after a successful proposal has been delivered, queued and passed its timelock. The call itself then runs through a permission-holding Executor; permissionless triggering is not permissionless arbitrary code execution.

Who can stop Aave in an emergency?

Current documentation lists a 4-of-7 Protocol Guardian with EMERGENCY_ADMIN pause/freeze powers and a separate 5-of-9 Governance Guardian able to veto proposals or unexecuted payloads. These are elected multisig dependencies with bounded roles.

Is staking AAVE the current Umbrella system?

Not exactly. Umbrella mainly uses reserve-matched aTokens and GHO. AAVE remains in the legacy Safety Module, which is still listed and can be slashed up to 20% after an onchain governance vote.

Does Umbrella make stakers whole or insure every loss?

No guarantee is documented. A configured stake token can be slashed for its matching reserve and network; coverage depends on offsets, available stake, governance-set configuration and follow-up coverage operations.

Do AAVE holders own Aave Labs or the DAO treasury?

Reviewed records establish token-weighted governance power, not corporate shares, dividends, redemption rights, intellectual property or a proportional right to withdraw treasury assets.

External trackers

Choose a tracking site for Aave: