Tempo published an Aave governance proposal on 16 October seeking a V4 deployment on its payments network. The author reports that an earlier temperature check passed; further risk analysis and an ARFC Snapshot remain next steps.

The configuration still needs clarification

The plan describes one liquidity hub with Main and RWA Spokes. Its prose names pathUSD and OUSD as borrowing assets, while the tables show OUSD borrowing against cbBTC, OUSD or PRIME collateral. Initial parameters await risk-provider analysis. A community reply also asks for the incentive strategy.

NetNapz assessment: payment activity is not lending demand

Assessment: the commercial question is whether payment balances become durable lending liquidity. Money held for payroll or settlement can leave quickly. A lending pool needs enough readily available assets to meet withdrawals even when borrowers do not repay at the same time. A large payments network would therefore not, by itself, establish a deep or resilient credit market.

The asset-list discrepancy matters before users try to compare products. Collateral eligibility, the asset a borrower receives and the asset needed to repay are separate terms. Governance should reconcile the specification before readers treat either description as the final configuration.

For each proposed collateral asset, the useful evidence would include its precise contract identity, price source, liquidation arrangements and redemption restrictions. Similar ticker names do not establish identical claims or exit rights. These are review questions, not findings that any listed asset has failed.

What would change the investment case?

Assessment: a deployment announcement would still leave adoption and economics to prove. AAVE investors should distinguish a network expansion from actual borrowing, income accruing to the DAO and any subsequent token-value mechanism. This proposal establishes none of those outcomes.

The next meaningful milestones are a reconciled asset specification, published risk terms, completed governance and a verified deployment. Those would let users assess the intended product; subsequent utilisation and withdrawal performance would show whether it works commercially.

Sources and limits

Tempo's Aave ARFC and community reply, dated 16 October, checked 17 October 2026. Tempo developer documentation was also reviewed for network context. NetNapz could not independently read the linked Snapshot result and has not verified deployed lending contracts. This is proposal coverage, not confirmation of live lending.