In July, Tempo asked the Aave community a question: would DeFi’s largest lender come to the payments blockchain incubated by Stripe and Paradigm? To make the case, it offered a sweetener.
It would pay depositors a yield close to the US benchmark interest rate (SOFR) for a full year, and it said the deployment would help grow Aave’s GHO stablecoin. The community voted yes.
Three months later, the formal proposal is out. I read it twice, and neither of those promises appears in it.
Aave’s Formal Proposal for Tempo Lands on October 16
The ARFC for deploying Aave V4 on Tempo was posted to Aave’s governance forum on October 16, 2026, under the account “Tempo.” Its summary is a single sentence proposing to deploy Aave Protocol V4 on Tempo Mainnet.
An ARFC (Aave Request for Final Comment) is the middle step of Aave’s three-stage process. It follows a temp check, which passed on Snapshot, and comes before a binding onchain vote. This document is meant to set out exactly what Aave would launch with.
By the time I checked, the thread had drawn about 200 views and one reply. For a proposal that would connect DeFi’s largest lending protocol to a chain backed by one of the world’s biggest payments companies, that’s very little attention.
What Tempo Brings to the Table
Tempo’s proposal describes itself as a Layer 1 blockchain built for payments. It was incubated by Stripe and Paradigm and is being developed with companies such as DoorDash, Deel, Shopify and MoneyGram, with a focus on cross-border payments, remittances, payroll and treasury management.
The technical setup is unusual for DeFi. Tempo Mainnet launched on March 18, 2026, with chain ID 4217. It has no native gas token. Fees are paid in dollar stablecoins, and pathUSD is the default when no other token is chosen. Stablecoins on Tempo follow the TIP-20 standard, and the chain has a built-in stablecoin exchange.
According to Tempo’s own FAQ, pathUSD is issued by Bridge, and the network is led by CEO Matt Huang, who is also a co-founder of Paradigm. The project raised $500 million at a $5 billion valuation before mainnet.
The ARFC gives four reasons for Aave to deploy there: reaching traditional enterprises and fintechs, listing real-world assets available on Tempo, growing stablecoin liquidity, and earning more revenue for the Aave DAO.
The Proposed Market Is Small and Narrow
V4 uses a “hub and spoke” design. A central pool of liquidity (the hub) serves separate markets with their own rules (the spokes). Tempo’s launch plan uses one hub and two spokes.
According to the proposal’s tables:
- Tempo Core Hub holds OUSD, cbBTC and PRIME.
- Main Spoke accepts cbBTC and OUSD as collateral, and OUSD is the only borrowable asset.
- RWA Spoke accepts PRIME as collateral, and again OUSD is the only borrowable asset.
That’s a small starting market: a Bitcoin wrapper, one real-world asset, and a single stablecoin to borrow. The ARFC doesn’t say who issues OUSD or PRIME or what backs them. It also says more assets may be added before launch, subject to risk review.
Where pathUSD and GHO Went
The ARFC’s own text says the hub will let pathUSD and OUSD be borrowed. Yet pathUSD doesn’t appear in any of the tables underneath. The asset that is Tempo’s default fee token, and the one Tempo promised to subsidize, isn’t actually listed in the market configuration.
That subsidy came from the original temp check in July. Tempo committed to pay incentives at around the SOFR rate on pathUSD deposited in Aave for the first year after launch. The same post listed growing GHO through business-to-business credit on Tempo as a goal of the deployment.
The ARFC doesn’t mention SOFR, any incentive, or GHO.
I’m not the only one who noticed. A delegate named Artilugio replied the same morning. He quoted the temp check’s own commitment that a successful vote would lead to an ARFC covering the “incentive strategy,” and asked whether it had been forgotten. As of today, there’s no response.
Risk Questions Raised in July Still Have No Answers
The ARFC also leaves out risk parameters. It says only that initial listings and parameters will be updated based on analysis from the DAO’s risk service providers. The next steps are a LlamaRisk review, followed by an ARFC Snapshot vote.
That leaves several questions from July unanswered. Delegate MconnectDAO had asked how losses would be shared among Tempo, the Aave DAO and users if something specific to Tempo failed, whether the chain itself, a bridge, or a real-world asset’s legal structure. He also asked for an overview of Tempo’s validator set, audits and security model, and whether the SOFR incentive was backed by any contractual commitment. Another delegate, Abel189, asked for measurable success targets, including whether liquidity would stay once incentives ended.
None of those points is addressed in the ARFC. Considering the proposal now lists a real-world asset spoke from day one, I think the loss-sharing question matters more now than it did in July.
Why This Matters Beyond One Chain
Zoom out and the strategy is clear. Aave’s governance forum also has an ARFC to deploy V4 on Arc, the stablecoin chain built by Circle, along with active V4 work on Avalanche. Aave appears to want to be the default lending layer on every payments-focused blockchain that corporate players are building.
Tempo might be the most valuable of these, given that Stripe is involved and it has a list of enterprise partners. That’s also why the details matter. A lender plugging into a chain designed for payroll and treasury management needs clear answers on collateral, incentives and responsibility for losses before the final vote, not after.
In my view, the idea is sound and the timing makes sense. But the proposal Aave holders will be asked to approve is thinner than the one they originally voted for. Whether pathUSD, the SOFR incentive and GHO return before the Snapshot vote is the thing to watch.
Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services.
Follow us on Twitter @themerklehash to stay updated with the latest Crypto, NFT, AI, Cybersecurity, and Metaverse news!
Be the first to comment