Summary
This ARFC proposes deploying Aave Protocol V4 on Tempo Mainnet.
Motivation
Tempo is a Layer 1 blockchain built for payments. It was incubated by Stripe and Paradigm and is developed in partnership with fintechs and large enterprises including DoorDash, Deel, Shopify and MoneyGram. Tempo is designed for stablecoin use cases including cross-border payments, remittances, embedded finance, payroll and treasury management.
Tempo Mainnet launched on March 18, 2026 and uses chain ID 4217. The network has no native gas token. Transaction fees are paid in USD-denominated stablecoins, with pathUSD used as the default fee token when no other token is specified. Stablecoins on Tempo are issued under the TIP-20 token standard, and the protocol includes an enshrined stablecoin DEX that uses pathUSD as its quote token.
Since launch, the Tempo team has been building yield and credit products with enterprise partners. Deploying Aave V4 on Tempo would make Aave the lending infrastructure available to the enterprises and fintechs building on the network.
The deployment is intended to expand Aave’s liquidity footprint to include traditional enterprises and fintechs, to develop new markets by listing real-world assets available on Tempo, to support stablecoin liquidity growth, and to generate additional protocol revenue for the Aave DAO.
The TEMP CHECK for this deployment passed Snapshot. This ARFC sets out the proposed market scope.
Hub and Spoke Configuration
The proposed initial Tempo deployment will activate with one Liquidity Hub and two Spokes. The Liquidity Hub enables pathUSD and OUSD stablecoins to be borrowed against collateral assets listed in the Main Spoke and RWA Spoke.
| Hub | Assets |
|---|---|
| Tempo Core Hub | OUSD, cbBTC, PRIME |
| Hub | Spoke | Collateral | Borrowable |
|---|---|---|---|
| Tempo Core Hub | Main Spoke | cbBTC, OUSD | OUSD |
| Tempo Core Hub | RWA Spoke | PRIME | OUSD |
Other assets may become available before the Aave deployment, and this ARFC may be updated before deployment to include them, subject to risk assessment.
Risk Parameters
The initial token listing and parameters will be updated based on Aave DAO risk service provider analyses.
Links
Website: https://tempo.xyz/
Customer stories: Customer Stories
Developer docs: Tempo Developer Docs: APIs, SDKs & Guides
Explorer: https://explore.tempo.xyz/
Next Steps
-
Gather community feedback and complete risk analysis from LlamaRisk.
-
Escalate the proposal to the ARFC Snapshot stage.
Copyright
Copyright and related rights waived via CC0.