This Temp Check seeks community feedback on deploying Aave v4 on Tempo Mainnet.
Tempo is a new purpose-built Layer 1 blockchain for payments, developed in partnership with leading fintechs and Fortune 500s like DoorDash, Deel, Shopify, Moneygram and more. Incubated by Stripe and Paradigm, Tempo is designed for stablecoin use cases including cross-border payments, remittances, embedded finance, payroll, and treasury management that bring real business value to companies adopting blockchain technology.
Launching Aave v4 on Tempo would position Aave as a key infrastructure partner for Tempo and the enterprises building on Tempo.
Motivation
Tempo launched on mainnet in March 2026. Since then, the Tempo team has been building yield and credit products with enterprise partners. With regulatory clarity emerging around stablecoins and crypto, traditional companies are increasingly positioned to build onchain using DeFi infrastructure. Tempo is excited to partner with the Aave ecosystem on bringing these use cases to life.
Deploying Aave v4 on Tempo will:
Expand Aave’s liquidity footprint to include traditional enterprises and fintechs
Develop new markets by listing bespoke real-world assets exclusive to Tempo
Grow GHO by powering B2B credit use cases on Tempo
Drive new revenue opportunities that will accrue value back to the Aave DAO and $AAVE token holders
For the first year after Aave v4 launches on Tempo, the Tempo team will incentivize pathUSD deposited on Aave at around SOFR rate. This will establish a sustainable baseline incentive APY for the pathUSD supply market. pathUSD is a native stablecoin on Tempo issued by Bridge.
Specification
If governance supports this Temp Check, the next phase will be an ARFC for deploying Aave v4 on Tempo. The ARFC would include the proposed initial supported tokens, oracle configuration, risk framework, deployment contracts, incentive strategy, and parameter recommendations from relevant Aave DAO service providers.
Gather community feedback on this Temp Check during a five day forum discussion period and escalate to Snapshot
Following a successful Snapshot, publish an ARFC covering the initial supported tokens, oracle configuration, risk framework, deployment contracts, incentive strategy, and parameter recommendations from relevant Aave DAO service providers
After the ARFC discussion and a successful ARFC Snapshot, submit an AIP for an onchain vote to deploy Aave v4 on Tempo
@Tempo Thanks for the proposal, can you provide a lot more details on subjects such as your Incentives Package Commitments or perhaps your Post Growth Roadmap with v4?
Thanks for bringing this Temp Check to the Aave community and for sharing high‑level context around Tempo and your enterprise partners.
Before forming an opinion on deploying Aave v4 on a new L1, I’d like to understand the risk and incentive profile in more detail:
Chain security and decentralization
Could you share a concise overview of Tempo’s security model (consensus design, validator set, audits, incident history) and any independent assessments that Aave governance can review?
Stablecoin and RWA risk
For pathUSD and the bespoke real‑world assets you plan to list, what does the legal/regulatory and collateral framework look like (reserves, enforcement, jurisdictions), and how are worst‑case loss scenarios handled for Aave users?
Incentives package commitments
The post mentions ~SOFR‑level incentives for one year. Is there any on‑chain or contractual commitment that guarantees these incentives, and what happens to TVL/liquidity assumptions once this period ends?
Loss‑sharing and responsibility
In the event of a Tempo‑specific failure (L1, bridge, RWA/legal), how do you envision cost and responsibility being shared between Tempo, Aave DAO, and end users? Is any backstop or insurance layer being considered as part of the deployment?
Clarifying these points would make it much easier for risk‑focused delegates to evaluate whether deploying Aave v4 on Tempo is strictly necessary at this stage or more of an optional growth bet, and what safeguards should accompany it.
Tempo presents an interesting opportunity to expand Aave into enterprise-oriented financial use cases, which could diversify both liquidity sources and protocol adoption beyond the traditional DeFi ecosystem.
One aspect I would like to see clarified over time is how success will be measured after deployment. Beyond TVL, it would be valuable to define a small set of objective KPIs, such as enterprise participation, GHO adoption, utilization of the proposed markets, and the retention of liquidity once the initial incentive program concludes.
Having predefined success metrics would help governance evaluate whether the deployment is achieving its intended objectives and would provide a consistent framework for assessing future Aave V4 deployments on new networks.
