Aave activated the first version of its pooled lending protocol on Ethereum on January 8, 2020. The successful mainnet transaction at 16:23:06 UTC created the V1 Lending Pool proxy at address 0x398eC7346DcD622eDc5ae82352F02bE94C62d119 in block 9,241,022.
The launch mattered because Aave was moving beyond the individually matched loans associated with ETHLend. Its new architecture gathered deposits in shared reserves, issued deposit claims called aTokens and let overcollateralized borrowers draw from available liquidity. It also put flash loans—uncollateralized liquidity that had to be returned inside one Ethereum transaction—into a live protocol.
A pool replaced bilateral matching
In the earlier peer-to-peer model, a lender and borrower needed compatible amounts and terms. Aave V1 instead treated each supported asset as a reserve. Depositors supplied assets to a common pool; borrowers accessed that liquidity after posting collateral that met the protocol’s parameters.
That design reduced the matching problem but did not eliminate risk. Borrowing power depended on token-specific loan-to-value limits and the market value of collateral. If a position’s health factor fell below the liquidation threshold, an external liquidator could repay part of the debt and receive collateral under the protocol’s rules. Price feeds, collateral liquidity, Ethereum execution and the correctness of the contracts therefore remained material dependencies.
Interest rates were algorithmic rather than negotiated loan by loan. Variable borrowing costs changed with reserve utilization: as borrowing consumed more of a reserve’s available liquidity, rates could rise. Aave also offered a “stable” borrowing mode, but the V1 documentation allowed that rate to be rebalanced under defined conditions. It was not equivalent to an irrevocably fixed conventional loan.
Depositors received aTokens corresponding to supplied assets. V1’s design kept an aToken tied one-for-one to its underlying asset while the holder’s token balance increased as interest accrued. That made the deposit position transferable and usable by other Ethereum applications, while also extending the chain of technical dependencies beyond the lending pool itself.
Flash loans compressed borrowing into one transaction
Flash loans were the launch’s most distinctive function. A custom contract could withdraw assets from an Aave reserve, perform other operations and return the liquidity plus the required fee before the transaction completed. If repayment failed, Ethereum reverted the transaction’s state changes.
The mechanism did not create an unsecured loan lasting hours or days. Its protection came from atomic execution: repayment and every preceding operation succeeded together, or the whole sequence was discarded. Contemporaneous discussion identified arbitrage, liquidation and refinancing as possible uses, but those were prospective applications on January 8, not evidence of meaningful launch-day demand.
What the chain establishes
The deployment record is unusually precise. Etherscan identifies the successful call from an Aave-labeled deployer to the V1 Lending Pool Provider, the proxy creation, block 9,241,022 and the 16:23:06 UTC timestamp. A separate event listing records a WBTC redeem interaction at 17:37:54 UTC in block 9,241,340, followed by additional same-day redeem events. Those records establish deployment and operation on January 8; they do not prove which interaction was the first deposit, first borrow or first flash loan.
Contemporaneous coverage described 16 assets available for deposits and borrowing at launch. That is an announced market list, not a measurement of liquidity in every reserve. No complete, reproducible January 8 dataset reviewed for this reconstruction establishes total value locked, deposit volume, outstanding loans, flash-loan volume or a token-price reaction.
The defensible event-day conclusion is therefore bounded: Aave V1 became operational on Ethereum as a pooled, non-custodial lending system, and flash loans became a production feature. Claims about later adoption, exploits, governance changes or market leadership belong to later dates and are not projected backward.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.

