Tempo

Aave’s governance forum has advanced a proposal to deploy Aave Protocol V4 on Tempo Mainnet, a Layer 1 blockchain incubated by Stripe and Paradigm that launched in March 2026. The deployment would make Aave’s lending infrastructure available to enterprises and fintechs building payment and treasury products on Tempo, where transaction fees are paid in USD-denominated stablecoins rather than a native gas token.

• Tempo Mainnet launched March 18, 2026 with chain ID 4217 and no native gas token
• Initial deployment includes one Liquidity Hub and two Spokes for pathUSD and OUSD stablecoins
• Proposal aims to expand Aave’s liquidity footprint to traditional enterprises and generate protocol revenue

• March 18 Tempo Mainnet launch date, five months before this deployment proposal
• 2 Spokes Initial market structure: Main Spoke and RWA Spoke for collateral assets
• 4217 Tempo’s unique chain identifier and transaction fee standard

The ARFC (Aave Request for Comments) proposal follows a successful Snapshot temperature check vote. Tempo is described as built for payments and incubated by Stripe and Paradigm, with development partners including DoorDash, Deel, Shopify and MoneyGram. The network uses pathUSD, a stablecoin, as its default fee token and operates an enshrined stablecoin DEX where pathUSD serves as the quote token.

Market structure and token scope remain preliminary

The proposal outlines an initial deployment with one Liquidity Hub and two Spokes. The Hub enables pathUSD and OUSD stablecoins to be borrowed against collateral assets listed in the Main Spoke and RWA Spoke, creating a structure designed around real-world asset lending and stablecoin liquidity.

The document states that “other assets may become available before the Aave deployment, and this ARFC may be updated before deployment to include them, subject to risk assessment.” Initial token listing and parameters will be updated based on analyses from Aave DAO’s risk service provider, LlamaRisk, which has not yet published its assessment.

The proposal does not specify which real-world assets will be available at launch or under what timeline.

Aave’s multichain expansion strategy

This marks Aave V4’s extension to a third Layer 1 network. The protocol has previously deployed on Ethereum mainnet and other chains, and governance has also advanced concurrent temperature checks for Aave V4 deployments on Avalanche and Arc, a blockchain focused on privacy and compliance.

Tempo’s enterprise-focused positioning differs from public blockchain ecosystems. The network has no native gas token and charges fees exclusively in stablecoins, aligning with use cases in cross-border payments, remittances, embedded finance, payroll and treasury management.

Aave’s deployment would serve as lending infrastructure for the fintech and enterprise partners already building yield and credit products on the network since March.

What changes for Aave holders and borrowers

Aave token holders gain exposure to a new revenue stream if the Tempo deployment generates protocol fees. Borrowers and lenders on Tempo will access Aave’s V4 interface for stablecoin lending and collateral management, integrating lending into the payment-first infrastructure that Tempo provides. The deployment does not require changes to AAVE governance or token mechanics.

The proposal does not disclose expected transaction volumes, projected fees, or timelines for risk review completion. It also leaves open whether additional stablecoin or collateral assets will be whitelisted before or shortly after launch, pending risk analysis.

The CCS read. Aave is consolidating its presence on enterprise blockchains where stablecoins and real-world assets drive adoption. Tempo’s focus on payments and traditional finance partnerships creates a tighter wedge for Aave’s lending than on public chains. The protocol’s fee model and absence of a native token make Aave’s revenue opportunity harder to estimate, but governance is betting that volume among Tempo’s fintech users will justify the engineering cost of a third V4 deployment.

The ARFC will escalate to a Snapshot vote after community feedback and LlamaRisk risk analysis are complete. No date has been set for that vote. Aave governance must also decide whether concurrent deployments on Avalanche and Arc will proceed on a similar timeline.