DeFi & stablecoins
LlamaRisk recommends conditional approval of cbBTC on Aave Tempo
The risk provider proposes using Coinbase’s wrapped bitcoin only as collateral on Aave V4 Tempo. It recommends waiting for a public audit and a security bounty covering the relevant native components before activating the listing.

Collateral with a cap of 250 cbBTC
On November 20, 2026, LlamaRisk published a cbBTC assessment on the Aave forum for Aave V4’s main market on Tempo. It recommends accepting the token as collateral only, with a 78% collateral factor and an add cap of 250 cbBTC. It proposes a draw cap of zero. These are recommended parameters for a possible listing. The report does not announce a governance decision or market activation for the token.
Coinbase issues cbBTC, a token designed to be backed by bitcoin held in its custody service. According to the assessment, cbBTC on Tempo is minted through Chainlink’s CCIP bridge against cbBTC locked on Base. LlamaRisk counted 37.98 cbBTC in circulation on Tempo at its November 17 observation point. For pricing inside Aave, it recommends the standard Chainlink cbBTC/USD feed until Smart Value Recapture, or SVR, is confirmed on Tempo and verified by Aave.
Limited local market depth
Liquidating a loan backed by cbBTC would leave the liquidator with a token to sell. LlamaRisk found one Uniswap pool with usable depth on Tempo and attributes it to a single market maker. On November 17, under its cost and reference-price assumptions, a sale near break-even was roughly six cbBTC, down from roughly 25 a day earlier. Those figures are two observations and can change as liquidity enters or leaves the pool.
For larger amounts, the report considers bridging the token back to Base for sale. That route depends on bridge availability, limits in each direction, and market depth at the destination. It offers different conditions from a local liquidation in the same transaction. The assessment ties the proposed cap to those exit constraints and to the concentration of holders it observed on Tempo.
Two conditions before activation
LlamaRisk recommends auditing the deployed code of the native TIP-20 and TIP-403 components, with no unresolved high- or critical-severity findings. It also calls for a bug bounty covering both components and offering at least $50,000 for a critical finding. The provider says it found neither a public audit covering the live native code nor a bounty covering those components as of its assessment.
The report notes that LlamaRisk is funded in part by the Aave DAO. Its publication opens discussion on the terms of a listing. Evidence of a public audit, bounty coverage, and a governance decision would distinguish the recommendations from an actual launch.
