# Coinbase Wrapped BTC (cbBTC) on Aave Tempo Assessments

**URL:** <https://governance.aave.com/t/coinbase-wrapped-btc-cbbtc-on-aave-tempo-assessments/26468>\
**Category:** Assessments\
**Created:** [November 20, 2026, 8:59pm UTC](https://governance.aave.com/t/coinbase-wrapped-btc-cbbtc-on-aave-tempo-assessments/26468 "2026-11-20T20:59:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LlamaRisk](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/llamarisk/32/12865_2.png) [@LlamaRisk](https://governance.aave.com/u/LlamaRisk)\
**Post date:** [November 20, 2026, 8:59pm UTC](https://governance.aave.com/t/coinbase-wrapped-btc-cbbtc-on-aave-tempo-assessments/26468/1 "2026-11-20T20:59:30Z")

</div>

This thread is the home for all risk and technical assessments of Coinbase Wrapped BTC (cbBTC) on Aave Tempo.

It collects, in one place:

- The pre-listing asset risk assessment, under the Aave Risk Framework.
- The pre-listing technical asset assessment, under the Technical Asset Listing Framework.
- All post-listing monitoring reports, periodic refresh assessments, and any re-evaluations triggered by material changes.

New assessments and updates will be posted as replies below as they are produced, so the full history stays in a single thread.

---

<div class="post-metadata">

**Author:** ![LlamaRisk](https://dub1.discourse-cdn.com/flex013/user_avatar/governance.aave.com/llamarisk/32/12865_2.png) [@LlamaRisk](https://governance.aave.com/u/LlamaRisk)\
**Post date:** [November 20, 2026, 9:09pm UTC](https://governance.aave.com/t/coinbase-wrapped-btc-cbbtc-on-aave-tempo-assessments/26468/2 "2026-11-20T21:09:47Z")

</div>

## Summary

LlamaRisk supports onboarding cbBTC to the Main Spoke of the Aave V4 Tempo Core Hub as collateral only, with a collateral factor of 78%, a maximum liquidation bonus of 7.77%, a liquidation fee of 10%, collateral risk of 0%, an add cap of 250 cbBTC and a draw cap of 0. We recommend pricing it with the Chainlink cbBTC/USD feed through the standard proxy until Chainlink confirms that Smart Value Recapture (SVR) is live on Tempo and Aave verifies the integration. On Tempo, cbBTC is bridged from Base through Chainlink’s Cross-Chain Interoperability Protocol (CCIP), and supply was 37.98 cbBTC on November 17, 2026.

Tempo has one usable Uniswap pool, which we assess is funded by a single market maker, so liquidations larger than its depth (about 6 cbBTC before break-even on November 17) must bridge cbBTC to Base and sell there. Admin roles on the Tempo token sit with Chainlink governance contracts, while on Base every assigned token role, including the proxy admin, is a Coinbase-controlled externally owned account (EOA) with no timelock.

cbBTC on Tempo runs on Tempo’s TIP-20 and TIP-403 precompiles, which have no public audit and no bug bounty (§3.3, §3.4). We recommend activating the listing once an audit of the live precompile code shows no unresolved High or Critical findings and a bug bounty covering both precompiles pays at least $50,000 for a critical finding.

## 1. Asset Fundamental Characteristics

### 1.1 Asset

[cbBTC](https://basescan.org/token/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf) is a non-yield-bearing wrapped BTC token issued by Coinbase. It is designed to maintain a 1:1 backing by native Bitcoin held in Coinbase’s institutional custody, and [LlamaRisk previously assessed it for Aave](https://governance.aave.com/t/arfc-onboard-cbbtc-to-aave-v3-on-base-and-mainnet/18988/11). Under the [Aave Asset Classification Framework](https://governance.aave.com/t/arfc-endorse-the-asset-classification-framework-aaca/23114), cbBTC is a Wrapped Asset. Coinbase manages its issuance and reserves centrally.

Unless stated otherwise, figures are as of [Tempo block 49,506,757](https://explore.tempo.xyz/block/49506757) and [Base block 58,750,951](https://basescan.org/block/58750951) (November 17, 2026, 1:36 PM ET), when the Chainlink cbBTC/USD feed on Tempo read $63,989.38. On Tempo, cbBTC is a [TIP-20 token](https://explore.tempo.xyz/address/0x20C000000000000000000000c412Ec89D0c08be5). TIP-20 is Tempo’s native token standard, implemented as a precompile. cbBTC on Tempo uses 6 decimals, compared with 8 on Base.

### 1.2 Architecture

cbBTC on Base is an upgradeable [FiatTokenProxy](https://basescan.org/address/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf), with [FiatTokenV2\_1](https://basescan.org/address/0x7458bfDC30034EB860B265E6068121D18Fa5Aa72) as its current implementation, the same architecture as USDC. Supply on Base was 49,720 cbBTC ($3.18B) on November 17, 2026.

On Tempo, a CCIP BurnMintTokenPool, the [Tempo pool](https://explore.tempo.xyz/address/0x3b54b8c2bcbb673a42c98db9f6ec95128d46c71e), mints and burns the token against cbBTC locked in the CCIP pool on Base. A [deployer address](https://explore.tempo.xyz/address/0x062f05cd6c835677b05a8658a351969476861316) created the token on May 6, 2026 (block 18,568,293) through the [TIP-20 factory](https://explore.tempo.xyz/address/0x20Fc000000000000000000000000000000000000). It granted the admin role to the Chainlink CCIP [timelock](https://explore.tempo.xyz/address/0xd31dB306E5D79F0018Ac92e08492284201493EA1) and the minting role to the Tempo pool, then gave up its own admin role.

 ![Exhibit 1](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/3X/4/d/4d7e26178f560115de88d416827bb1eaf963da63.png)

#### 1.2.1 Minting

On Base, cbBTC minting starts off-chain through verified Coinbase customer accounts and is controlled by Coinbase’s internal processes:

1. A customer withdraws BTC from Coinbase to a supported chain in wrapped form ([Coinbase help](https://help.coinbase.com/en/exchange/crypto-transfers/wrapped-assets)).
2. The `masterMinter` sets a minter’s allowance with `configureMinter()`, and that minter calls `mint()` on the FiatTokenV2\_1 implementation to issue cbBTC to the customer’s address.
3. Supply updates onchain, and the tokens reach the customer.

Coinbase does not mint cbBTC on Tempo. The Tempo pool, the only holder of the minting role, mints only what the Base pool locks once CCIP delivers the message, up to the 79.2 cbBTC inbound limit (§1.2.4).

#### 1.2.2 Redemption

An eligible Coinbase customer deposits cbBTC with Coinbase, which unwraps it and credits BTC to the account ([Coinbase help](https://help.coinbase.com/en/exchange/crypto-transfers/wrapped-assets)). Withdrawing that BTC to a Bitcoin address is a separate step. There is no onchain redemption queue, so timing and restrictions follow Coinbase’s operational and compliance requirements.

A holder on Tempo must first bridge to Base, where the Base pool releases cbBTC equal to the amount burned on Tempo, and then redeem with Coinbase.

#### 1.2.3 Fees

The cbBTC contracts charge no transfer fee. Bridging between Tempo and Base costs a CCIP fee of 0.26–0.27 pathUSD per message, as quoted by the Tempo router at the November 17 block. Tempo network fees can be paid in stablecoins such as [pathUSD](https://explore.tempo.xyz/address/0x20c0000000000000000000000000000000000000). For a liquidator, the larger costs are the swap discount, OUSD funding and converting exit proceeds back to OUSD (§2.1).

#### 1.2.4 Bridge

cbBTC bridges from Base through Chainlink CCIP and a [LockReleaseTokenPool](https://basescan.org/address/0x93cF6F19fdd01c8C240651357193E25abf41523a). On November 17, 2026, the pool held 160.30 cbBTC ($10.3M), 0.32% of Base supply. Every remote chain bridges through Base and draws on the same escrow.

At the November 17 blocks, the allowlist was disabled, so any address can start a cross-chain transfer, and no `rateLimitAdmin` was set, so changing a rate limit requires the timelock process in §3.1.2 or the bypasser. Each lane has a rate limit with a capacity and a refill rate. Five lanes were active on November 17:

| **Remote chain** | **Capacity, Base → chain** | **24h refill, Base → chain** | **Capacity, chain → Base** | **24h refill, chain → Base** |
| --- | --- | --- | --- | --- |
| Monad | 100 cbBTC | 99.4 cbBTC | 110 cbBTC | 109.3 cbBTC |
| Robinhood | 100 cbBTC | 100.0 cbBTC | 110 cbBTC | 110.0 cbBTC |
| Tempo | 72 cbBTC | 72.0 cbBTC | 79.2 cbBTC | 79.2 cbBTC |
| Katana | 25 cbBTC | 24.2 cbBTC | 27.5 cbBTC | 26.6 cbBTC |
| Aptos | 25 cbBTC | 25.0 cbBTC | 25 cbBTC | 25.0 cbBTC |

Source: [Base LockReleaseTokenPool](https://basescan.org/address/0x93cF6F19fdd01c8C240651357193E25abf41523a), November 17, 2026.

The Tempo pool connects only to Base, with matching limits, and all four Tempo–Base buckets were full on November 16 and 17. Tempo’s outbound bucket, which governs exits to Base, holds 72 cbBTC and refills at about 3 cbBTC per hour, so an exit larger than local depth moves at that pace after the first 72 cbBTC. Tempo’s inbound bucket, which governs mints on Tempo, holds 79.2 cbBTC, which caps a forged CCIP message at 79.2 cbBTC minted at once and about 158 cbBTC in 24 hours. Past transfers from Tempo reached Base in under two minutes ([Tempo pool logs](https://explore.tempo.xyz/address/0x3b54b8c2bcbb673a42c98db9f6ec95128d46c71e)).

### 1.3 Backing and Reserve Analysis

#### 1.3.1 Proof of Reserves

A Chainlink [Proof of Reserves (PoR) feed](https://basescan.org/address/0x0F8E057D1D7b282EF968D26E9cB432617dF52519#code) on Base reports the BTC backing cbBTC. Chainlink node operators read the balances directly from the Bitcoin chain, but Coinbase supplies the list of addresses through Chainlink’s [Wallet Address Manager](https://docs.chain.link/data-feeds/smartdata), so the feed covers only the addresses Coinbase includes. Coinbase also publishes address-level balances on its [proof-of-reserves page](https://www.coinbase.com/cbbtc/proof-of-reserves).

The feed read 105,791.27 BTC at the November 17 Base block, from its November 16 update at 7:27 PM ET. The latest matched comparison with native supply is from October: the feed reported 95,935.97 BTC on October 25, 0.12% below the next day’s 96,047.89 cbBTC of native supply on Base, Ethereum, Arbitrum and Solana. The feed updates once a day and lags new minting; the previous matched reading, from October 24, showed 100.10% coverage.

Tempo has no reserve feed, but its supply can be checked against the bridge. Through November 17, 2026, the Tempo pool minted 326.44 cbBTC and burned 288.45 cbBTC, matching the 37.98 cbBTC ($2.43M) outstanding. No cbBTC has been minted on Tempo outside the bridge.

### 1.4 Tokenomics

cbBTC does not enforce a hard supply cap at the contract level. The masterMinter role controls supply by setting allowances for individual minters. The TIP-20 supply cap on Tempo is set to the maximum value, so Tempo supply moves only with the bridge under the current roles.

 ![Exhibit 2](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/3X/1/7/1739cdf0ce581c4e5081dd9f9d4dcd88c1e7d589.png)

Source: [Tempo cbBTC transfer logs](https://explore.tempo.xyz/address/0x20C000000000000000000000c412Ec89D0c08be5), LlamaRisk calculations.

Tempo supply peaked at 264.31 cbBTC on August 17, 2026, when 99.99% of it sat in Morpho Blue, supplied from three wallets. By October 4, 2026, it had fallen to 4.05 cbBTC (§2.4). On October 21, 2026, 36.87 cbBTC was minted to an [EOA](https://explore.tempo.xyz/address/0x87227292ccc804cc17729fe5cd4304f7dae0cb14), which moved 30.63 cbBTC into Uniswap v4 [OUSD](https://explore.tempo.xyz/address/0x20c0000000000000000000006a37da5c996874be)/cbBTC liquidity. OUSD is a US dollar stablecoin issued by Bridge, a Stripe subsidiary, and is the borrowable asset on the Main Spoke.

#### 1.4.1 Token Holder Concentration

Largest identified holders on Base on November 17, 2026. All five are contracts; none is an EOA or a multisig:

- [Morpho](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf?a=0xBBBBBbbBBb9cC5e90e3b3Af64bdAF62C37EEFFCb) (contract, Morpho Blue singleton): 82.48%
- [Aave V3](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf?a=0xBdb9300b7CDE636d9cD4AFF00f6F009fFBBc8EE6) (contract, aBascbBTC aToken): 6.45%
- [MagicSpend](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf?a=0x982663b77D98170266eb969811eaD30eB95961E6) (contract, Coinbase paymaster): 0.99%
- [CCIP LockReleaseTokenPool](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf?a=0x93cF6F19fdd01c8C240651357193E25abf41523a) (contract): 0.32%
- [dHEDGE V2 Pool](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf?a=0x3764F07752384450576C6d8b027d06Ffa29E5Ae9) (contract, aBTC vault): 0.26%

Source: Basescan, November 17, 2026.

On Tempo, three addresses held 99% of supply on November 17, 2026. One [EOA](https://explore.tempo.xyz/address/0x87227292ccc804cc17729fe5cd4304f7dae0cb14) held 29.01 cbBTC (76.4%), the Uniswap v4 [PoolManager](https://explore.tempo.xyz/address/0x33620f62c5b9b2086dd6b62f4a297a9f30347029) 7.83 cbBTC (20.6%) across all its pools and [Morpho Blue](https://explore.tempo.xyz/address/0x10EE9AAC980A180dd4DcFc96C746d60B0EA88f97) 0.77 cbBTC (2.0%). That EOA also funded a [liquidity contract](https://explore.tempo.xyz/address/0x74706bc34ed24c4d59e02679cd835d108d741836) and made its first liquidity changes, so we attribute both, together with a second [operator EOA](https://explore.tempo.xyz/address/0x99c0fe3aad7d3dd950cdda57381db873c4324e59), to one unidentified market maker that controls nearly all cbBTC on Tempo outside Morpho.

## 2. Market Risk

### 2.1 Liquidity

A liquidator repays OUSD and receives cbBTC, then sells it on Tempo in the same transaction or bridges it to Base and sells there. On Tempo, cbBTC trades only on Uniswap v4, because the Stablecoin DEX, Tempo’s built-in order book, lists only stablecoins. Of four Uniswap v4 pools with cbBTC in October, only the OUSD/cbBTC 0.30% pool, created on October 15, 2026, had usable depth. Quotes through the [Uniswap v4 Quoter](https://explore.tempo.xyz/address/0x20e6487c371a2086f841ef453f85378223df4f4e), against the cbBTC/USD and OUSD/USD feeds, fee included:

| **Date and Tempo block** | **Sell size (cbBTC)** | **OUSD received** | **Discount to the feed** |
| --- | --- | --- | --- |
| Nov. 16, 49,361,537 | 1 | 64,676 | 0.22% |
| Nov. 16, 49,361,537 | 5 | 320,784 | 1.02% |
| Nov. 16, 49,361,537 | 20 | 1,241,813 | 4.21% |
| Nov. 16, 49,361,537 | 25 | 1,526,321 | 5.81% |
| Nov. 16, 49,361,537 | 30 | 1,690,322 | 13.08% |
| Nov. 17, 49,506,757 | 1 | 63,131 | 1.34% |
| Nov. 17, 49,506,757 | 5 | 305,251 | 4.59% |
| Nov. 17, 49,506,757 | 10 | 425,686 | 33.47% |

Source: [Uniswap v4 Quoter](https://explore.tempo.xyz/address/0x20e6487c371a2086f841ef453f85378223df4f4e) on Tempo, November 16 and 17, 2026.

Near a health factor of 1, a liquidator breaks even selling at a 5.92% discount to the feed, after the 10% fee on the bonus. On November 16 a liquidator could sell 25.28 cbBTC before reaching it. On November 17 that fell to 6.14 cbBTC, and the pool’s maximum output fell from 1.69M to 0.43M OUSD. Since late October the market maker has moved cbBTC out of the pool: the PoolManager’s balance fell from 30.59 to 7.83 cbBTC and the funding EOA’s rose from 6.25 to 29.01.

 ![Exhibit 3](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/3X/1/e/1e0e703f9aed586a480a7a5a78cae1f45d3a1898.png)

Source: [Uniswap v4 Quoter](https://explore.tempo.xyz/address/0x20e6487c371a2086f841ef453f85378223df4f4e) on Tempo, Chainlink feeds, LlamaRisk calculations.

On Base, [KyberSwap](https://kyberswap.com/swap/base) quoted 4,564,636 USDC for 72 cbBTC at 1:38 PM ET on November 17, a 0.92% discount to the feed. When the lane has room, the bridge takes one to two minutes per transfer, during which the liquidator has already funded the OUSD repayment and carries BTC price risk.

The liquidator then has to turn that USDC back into OUSD on Tempo. At the November 17 block, the [Stablecoin DEX](https://explore.tempo.xyz/address/0xDEc0000000000000000000000000000000000000) could convert at most 480,222 USDC.e or 586,245 pathUSD into OUSD in a single quote. Relay quoted 480,000 Base USDC into OUSD at a 0.066% loss but rejected the 4.56M USDC proceeds of a 72 cbBTC sale. Public onchain routes therefore top out near $0.5M per conversion. Coinbase Exchange converts USDC to OUSD and allows OUSD withdrawals to Tempo of up to 4M OUSD each, so a liquidator with an institutional account could recycle the proceeds of a full 72 cbBTC bridge transfer in two withdrawals.

#### 2.1.1 Liquidity Venue Concentration

On Base, the 20 largest cbBTC pools on [GeckoTerminal](https://www.geckoterminal.com/base/tokens/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf) held $76.43M of total value locked (TVL) on November 17, 2026, $56.58M of it in the top eight:

| **Pair** | **DEX** | **TVL** |
| --- | --- | --- |
| cbBTC/WETH 0.05% | Uniswap V3 | $16.10M |
| cbBTC/WETH 0.3% | Uniswap V3 | $7.78M |
| cbBTC/WETH 0.05% | Aerodrome Slipstream | $7.65M |
| cbBTC/USDC 0.05% | Uniswap V3 | $6.35M |
| cbBTC/USDC 0.149% | Aerodrome Slipstream | $6.01M |
| cbBTC/WETH 0.136% | Aerodrome Slipstream | $4.67M |
| cbBTC/WETH 0.01% | PancakeSwap V3 | $4.09M |
| cbBTC/USDC 0.178% | Aerodrome Slipstream | $3.92M |

Source: [GeckoTerminal](https://www.geckoterminal.com/base/tokens/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf), November 17, 2026.

#### 2.1.2 DEX LP Concentration

On Tempo, 99.9% of the OUSD/cbBTC pool’s liquidity changes in October, and all of them between November 16 and 17, came from the market maker’s [operator EOA](https://explore.tempo.xyz/address/0x99c0fe3aad7d3dd950cdda57381db873c4324e59) through its [liquidity contract](https://explore.tempo.xyz/address/0x74706bc34ed24c4d59e02679cd835d108d741836), consistent with a single automated market maker. The operator has already withdrawn most of its cbBTC and can remove the rest at any time. If it withdraws, liquidators depend on the bridge alone.

### 2.2 Volatility

Largest BTC falls from an hourly close to the lowest price within the following window, Coinbase Exchange BTC-USD, January 1, 2020 to November 17, 2026:

| **Window** | **Worst fall, 2 years** | **Worst fall, 3 years** | **99.9th percentile, since 2020** |
| --- | --- | --- | --- |
| 1 hour | 7.02% | 7.47% | 6.11% |
| 4 hours | 9.06% | 11.32% | 10.90% |
| 8 hours | 12.09% | 16.43% | 15.76% |
| 1 day | 17.48% | 19.64% | 25.52% |

Source: Coinbase Exchange BTC-USD hourly prices, LlamaRisk calculations.

The largest falls of the past three years came on March 5 and August 4, 2024, and in the October 10, 2025 crash. The worst four-hour fall since 2020 was 33.51%, on March 12, 2020.

Between October 26 and November 17, the Tempo feed fell 20.2%, from $80,204 to $63,989, without exceeding any of the worst falls in the table. cbBTC itself tracked BTC closely: from July 15 to October 25, 2026, 99% of the Tempo feed’s rounds were within 0.40% of Chainlink BTC/USD on Base (§2.5).

### 2.3 Exchanges

cbBTC trades almost entirely on decentralized exchanges. Across 248 active listings, venues reported $456.84M of 24-hour volume on November 19, 2026, and Base carried $404.85M of it (88.6%), mostly against WETH and USDC on Aerodrome, Uniswap V3 and PancakeSwap. Solana ($24.74M) and Ethereum ($20.14M) followed. CoinGecko lists no centralized-exchange pair, and none of Coinbase Exchange, Binance, Kraken, OKX or Bybit listed a cbBTC spot market on November 17. It lists no venue on Tempo, where the Uniswap v4 OUSD/cbBTC pool (§2.1) is the only usable one.

| **Venue** | **Type** | **Pair** | **24h Vol** | **+2% Depth** | **−2% Depth** |
| --- | --- | --- | --- | --- | --- |
| Aerodrome Slipstream (Base) | DEX | cbBTC/WETH | $153.60M | $97k | $97k |
| Uniswap V3 (Base) | DEX | cbBTC/WETH | $65.27M | $430k | $428k |
| Aerodrome Slipstream (Base) | DEX | cbBTC/USDC | $55.98M | $110k | $109k |
| PancakeSwap V3 (Base) | DEX | cbBTC/WETH | $46.00M | $84k | $84k |
| Aerodrome Slipstream (Base) | DEX | cbBTC/WETH | $15.40M | $87k | $87k |
| Uniswap V3 (Base) | DEX | cbBTC/USDC | $13.09M | $119k | $119k |
| Aerodrome Slipstream 3 (Base) | DEX | cbBTC/WETH | $12.65M | $33k | $33k |
| Orca (Solana) | DEX | cbBTC/USDC | $12.05M | $79k | $79k |
| Aerodrome Slipstream (Base) | DEX | cbBTC/USDC | $9.02M | $106k | $105k |
| Uniswap V3 (Ethereum) | DEX | cbBTC/WBTC | $8.60M | $161k | $160k |

Source: [CoinGecko](https://www.coingecko.com/en/coins/coinbase-wrapped-btc), November 19, 2026. Each row is one pool.

### 2.4 Growth

Supply on Base grew in 50 of the 52 weeks reviewed, with small outflows in the other two.

On Tempo, the October rise from 4.05 to 41.11 cbBTC came mostly from the single 36.87 cbBTC transfer that seeded the OUSD/cbBTC pool and does not reflect broad demand.

 ![Exhibit 4](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/3X/8/f/8f90cbddf62c9a64d70f3786d04c2cddfae7ce2b.png)

Source: [Tempo pool logs](https://explore.tempo.xyz/address/0x3b54b8c2bcbb673a42c98db9f6ec95128d46c71e), LlamaRisk calculations.

In September, three Morpho borrowers unwound about 242 cbBTC of collateral in about five days. During those five days, 247.86 cbBTC left Tempo in 23 transfers of up to 39.04 cbBTC. The largest 24-hour outflow was 104.69 cbBTC, below the 144 cbBTC that a full bucket plus a day of refill allows. On November 17, 2026, Morpho Blue held 0.77 cbBTC on Tempo against $29.6K of debt across its three cbBTC markets.

### 2.5 Oracle and Price Feed Treatment

Neither a Proof of Reserves feed nor a BTC/USD feed exists on Tempo. Chainlink’s [cbBTC/USD feed on Tempo](https://data.chain.link/feeds/tempo/tempo/cbbtc-usd-shared-svr) prices the cbBTC token itself, so a discount of cbBTC to BTC would pass through to Aave positions. It reads one [aggregator](https://explore.tempo.xyz/address/0x3868BDFA1427C67AbF2d0e172FDdeA0A95c37630) through two proxies, a [standard proxy](https://explore.tempo.xyz/address/0x09025C12E6aA648a209f68B82839b786fbAea2d1) and a [Shared SVR proxy](https://explore.tempo.xyz/address/0x0a49f0fFB5e3eECC4482a5db8b36fE732D05C7F3), and both returned $63,989.38 from round 1385 at the November 17 block. Chainlink’s [SVR documentation](https://docs.chain.link/data-feeds/svr-feeds) does not list Tempo.

Chainlink’s [feed page](https://data.chain.link/feeds/tempo/tempo/cbbtc-usd-shared-svr) lists a 0.5% deviation threshold and a 24-hour heartbeat for the feed. From July 15 to October 25, 2026, it posted 989 rounds, a median 1.06 hours apart. Against [Chainlink BTC/USD on Base](https://basescan.org/address/0x64c911996D3c6aC71f9b455B1E8E7266BcbD848F), 99% of rounds were within 0.40%, and the range was −0.76% to +0.46%.

 ![Exhibit 5](https://europe1.discourse-cdn.com/flex013/uploads/aave/original/3X/3/e/3e1729cb77172d79974849c515cb10a238d2567f.png)

Source: [Tempo cbBTC/USD feed](https://data.chain.link/feeds/tempo/tempo/cbbtc-usd-shared-svr), [Chainlink BTC/USD on Base](https://basescan.org/address/0x64c911996D3c6aC71f9b455B1E8E7266BcbD848F), LlamaRisk calculations.

## 3. Smart Contract Security

### 3.1 Architecture and Access Controls

#### 3.1.1 Contract Modification Options

The following addresses controlled the cbBTC token on Base at the November 17 block:

| **Holder** | **Role** | **Functionality** |
| --- | --- | --- |
| [EOA](https://basescan.org/address/0xbbc9b6001cf0a4FCcfFAB7bDda1ab16cafb9dB4F) | `owner` | Transfers ownership; updates `pauser`, `blacklister`, `rescuer`, `masterMinter` |
| [EOA](https://basescan.org/address/0x42D90b3faF2287475cdc863706Bd7cc3E938C2Af) | Proxy admin | Upgrades the implementation contract |
| [EOA](https://basescan.org/address/0x2B5b99D0096a1Ae5641f5041F780A33D004fc1D3) | `masterMinter` | Configures per-minter allowances; `configureMinter()` / `removeMinter()` |
| [EOA](https://basescan.org/address/0x7399168043B684B57f198c42fC31558467cF2D6a) | `pauser` | Pauses and unpauses the token |
| [EOA](https://basescan.org/address/0x158cFA498B1f72f458aCf8DF993c709efCA11e31) | `blacklister` | Blacklists and un-blacklists addresses |
| None | `rescuer` | Not configured |

Source: [cbBTC proxy](https://basescan.org/address/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf) on Base, November 17, 2026.

Coinbase-controlled EOAs hold all token-level administrative roles, with no onchain timelock or multisig. The proxy admin can therefore upgrade the implementation without delay, and the pauser can halt all transfers immediately. The blacklister can freeze any address on its own authority, a standard feature of Circle- and Coinbase-issued tokens. A pause, or a blacklist on the Base pool’s address, would stop the pool from releasing cbBTC to a liquidator.

No Coinbase address holds any role on the Tempo token or pool. At the November 17 block, the admin role sat with the CCIP RBACTimelock and the minting role with the Tempo pool. The pause, `BURN_BLOCKED` and `BURN_AT` roles were unassigned. [`BURN_AT`](https://github.com/tempoxyz/tempo/blob/main/tips/tip-1006.md), added in the T12 network upgrade, lets its holder burn any balance without consent, including an Aave Hub’s. Only a short list of protected protocol contracts is exempt. Transfer policy 1 in the [TIP-403 registry](https://explore.tempo.xyz/address/0x403c000000000000000000000000000000000000) allows every transfer, so there is no blacklist today. Through the timelock, or at once through the bypasser, the admin can grant minting to a new address, which could then mint unbacked cbBTC. It can also grant pause or `BURN_AT`, switch to a restrictive policy, or change the pool’s rate limits and remote pool. None of these powers has been used.

#### 3.1.2 Timelock Duration and Function

**CCIP LockReleaseTokenPool (Base)**

The Base pool is owned by an [RBACTimelock](https://basescan.org/address/0x7B0328745A01634c32eFAf041d91432a075B308D) with a 3-hour minimum delay, which governs all pool-level changes, including rate limits, chain additions and removals, and rebalancer updates. A proposer queues a change, the executor carries it out after the delay, a canceller can stop it before then, and the bypasser can carry it out at once.

| **Role** | **Address** | **Function** |
| --- | --- | --- |
| PROPOSER | [ManyChainMultiSig](https://basescan.org/address/0xF9f0a7B42202fAE9F5c03610dd9eE4Cf48FCc3DA) A | Proposes timelock actions |
| PROPOSER | [ManyChainMultiSig](https://basescan.org/address/0xA68B757d60B5542F09A3123b72B96A03d07c50aB) B | Proposes timelock actions |
| PROPOSER | 6-of-12 [GnosisSafeProxy](https://basescan.org/address/0xdbE2d99519E9C70669129Dfa9387E51E443fb48F) | Proposes timelock actions; operator unconfirmed |
| EXECUTOR | [CallProxy](https://basescan.org/address/0xEeE2b71c85Db5c919963Aab330f62AE4a76aC5b1) | Executes queued actions after the delay |
| CANCELLER | ManyChainMultiSigs A, B and C, one further [address](https://basescan.org/address/0x29adcafedb612cbddafaddb676b72e9ac80682f2) and the GnosisSafeProxy | Cancels queued actions |
| BYPASSER | [ManyChainMultiSig](https://basescan.org/address/0x68c38b653535daAF7E067CBC814cD34E88280CfE) C | Executes authorized actions without the delay |

Source: [Base RBACTimelock](https://basescan.org/address/0x7B0328745A01634c32eFAf041d91432a075B308D), November 17, 2026.

The ManyChainMultiSig (MCMS) contracts are Chainlink’s multisig implementation for CCIP governance, and each one arranges signers in nested groups, every group with its own quorum. The 3-hour delay gives Aave a limited window to respond to queued changes.

**cbBTC token and BurnMintTokenPool (Tempo)**

The CCIP RBACTimelock on Tempo owns the Tempo pool, the [CCIP Router](https://explore.tempo.xyz/address/0xa132F089492CcE5f1D79483a9e4552f37266ed01) and the [risk management proxy](https://explore.tempo.xyz/address/0x65615642056b48BCB8120C109f7e7c0c3623A8BF), also with a 3-hour minimum delay at the November 17 block. The [proposer MCMS](https://explore.tempo.xyz/address/0xD3F31950e5Ec340b021D0d27454F44Edb7304C18) proposes changes, and an [executor address](https://explore.tempo.xyz/address/0x1560304ce794C67302580895f4d6a36C03E14AD3) executes them. All three Tempo MCMS contracts can cancel, including the [canceller MCMS](https://explore.tempo.xyz/address/0xf58A2e303e519f6A1b772137995871967e30391a), and the [bypasser MCMS](https://explore.tempo.xyz/address/0x7f0252830b6946152152c37bD0d02Dd5158d9D71) can skip the delay.

#### 3.1.3 Multisig Threshold / Signer identity

Signer identities are not published for any of these multisigs. Onchain reads at the November 17 blocks show:

| **Multisig** | **Chain** | **Role** | **Signers** | **Approval rule** | **Operations executed (nonce)** |
| --- | --- | --- | --- | --- | --- |
| [6-of-12 Safe](https://basescan.org/address/0xdbE2d99519E9C70669129Dfa9387E51E443fb48F) | Base | Proposer and canceller | 12 | 6 of 12 | 0 |
| [Proposer MCMS](https://explore.tempo.xyz/address/0xD3F31950e5Ec340b021D0d27454F44Edb7304C18) | Tempo | Proposer | 41, in groups of 17, 17 and 7 | 2 in each of 2 of the 3 groups | 217 |
| [Canceller MCMS](https://explore.tempo.xyz/address/0xf58A2e303e519f6A1b772137995871967e30391a) | Tempo | Canceller | 46, in nested groups | Nested quorum across groups | 0 |
| [Bypasser MCMS](https://explore.tempo.xyz/address/0x7f0252830b6946152152c37bD0d02Dd5158d9D71) | Tempo | Bypasser | 46, in nested groups | Nested quorum across groups | 0 |

Source: Basescan and Tempo Explorer, November 17, 2026.

The bypasser can carry out any timelock action at once, so the 3-hour delay protects Aave only against changes that go through the proposer. The bypasser also lets Chainlink stop a lane quickly in an emergency.

### 3.2 Multi-Chain Evaluation Scope

cbBTC on Ethereum, Arbitrum and Solana is natively issued by Coinbase, with no CCIP bridging.

**Base pool coverage.** Every lane draws on the same Base pool; Aptos uses a RegulatedTokenPool on its side, according to the [Chainlink CCIP directory](https://docs.chain.link/ccip/directory/mainnet/token/cbBTC). On November 17, 2026, the Base pool held 160.30 cbBTC against 159.77 cbBTC on Monad (91.43), Tempo (37.98), Robinhood (30.35) and Katana (0), covering those lanes with 0.53 cbBTC to spare. Aptos supply, 0.0002 cbBTC in October, is excluded. A shortfall in this shared escrow, from any lane, would affect Tempo even when its own buckets have room.

### 3.3 Audit Coverage

Coinbase’s cbBTC uses Circle’s FiatTokenProxy and FiatTokenV2\_1 codebase, which USDC also uses. [Circle’s whitepaper](https://www.circle.com/legal/mica-usdc-whitepaper) describes audits of USDC, and [OpenZeppelin’s audit](https://www.openzeppelin.com/news/coinbase-liquid-staking-token-audit) covers Coinbase’s cbETH, not cbBTC. We could not tie a published audit to the deployed Base cbBTC implementation.

The CCIP pools run standard Chainlink code ([version 1.6.1](https://github.com/smartcontractkit/chainlink-ccip/tree/contracts-ccip-v1.6.1)), which Chainlink’s bug bounty covers, but we found no public audit of the v1.6.1 pool contracts. The TIP-20 and TIP-403 precompiles change only through a Tempo hard fork and have no public audit. [Cyfrin’s August 2026 audit of Securitize’s TIP-20 service layer](https://github.com/Cyfrin/cyfrin-audit-reports/blob/main/reports/2026-08-28-cyfrin-securitize-tempo-tip20-v2.0.pdf) covers Securitize’s compliance contracts, not Tempo’s native token code. Tempo’s [security policy](https://github.com/tempoxyz/tempo/security) states that the chain is still undergoing audit, and Tempo told us that Sigma Prime reviews its hard forks privately. Neither T12, which added `BURN_AT`, nor T13, which added OUSD as a fallback fee token, has a published review.

### 3.4 Bug Bounty Program

Coinbase runs a bug bounty on [HackerOne](https://hackerone.com/coinbase/) for its off-chain systems, with up to $1,000,000 for unauthorized access to Coinbase-owned wallet assets or private keys. For onchain code, its [Cantina](https://cantina.xyz/bounties/55316f42-3c5e-4746-9bd0-0f18dcbc344b) program has a critical maximum of $5M, with cbBTC in its top tier. Chainlink’s [$3M Immunefi program](https://immunefi.com/bug-bounty/chainlink/information/) covers eligible CCIP findings, with a $100,000 minimum for a critical one.

None of these programs covers the Tempo token itself, which runs on the TIP-20 precompile, and Tempo has no bug bounty of its own. Tempo told us a program is planned but has not confirmed when it will launch, whether it will include the precompiles or what it will pay for a critical finding.

### 3.5 Dependency Risk

Coinbase remains the custodian of the backing BTC and can freeze or blacklist cbBTC. The PoR feed checks reserve balances on the Bitcoin chain, but only for the addresses Coinbase lists. On Tempo, cbBTC also depends on three additional components:

- **Chainlink CCIP.** A forged CCIP message could mint up to the 79.2 cbBTC inbound limit at once. A compromised bypasser could grant the minting role to a new address with no delay and no rate limit. On Aave, the add cap limits how much unbacked cbBTC could be supplied, not losses on cbBTC already supplied. A lane halt would remove the bridge exit.
- **The Base pool.** A Coinbase pause, blacklist or upgrade on Base, or a fault on another lane that drains the shared pool, would cut off the Base sale that larger liquidations rely on.
- **The Tempo network.** At the November 17 block, [ValidatorConfig V2](https://explore.tempo.xyz/address/0xCCCCCCCC00000000000000000000000000000001) listed 19 active permissioned validators, which a [2-of-5 Safe](https://explore.tempo.xyz/address/0xdC659efF2784cf79fbA88f85d26B1392270CcA33) adds and removes. Under Tempo’s [consensus rules](https://tempo.xyz/developers/docs/protocol/blockspace/consensus), the network halts if more than one third go offline, and a halt would freeze liquidations. Network upgrades can change the token precompiles, as Tempo’s [upgrade documentation](https://tempo.xyz/developers/docs/protocol/upgrades) and [release notes](https://github.com/tempoxyz/tempo/releases) describe.

## 4. Regulatory Review

See the [initial review](https://governance.aave.com/t/arfc-onboard-cbbtc-to-aave-v3-on-base-and-mainnet/18988/11). Coinbase issues cbBTC to verified customers under the [Coinbase User Agreement](https://www.coinbase.com/legal/user_agreement/united_states), which sets out eligibility and when Coinbase may pause or refuse redemption. Coinbase supports direct cbBTC deposits and withdrawals on Base, Ethereum, Solana and Arbitrum, not Tempo ([Coinbase help](https://help.coinbase.com/en/exchange/crypto-transfers/wrapped-assets)), so a Tempo holder’s claim against Coinbase runs through the Base cbBTC locked in the Base pool. We found no Coinbase terms specific to Tempo.

### Disclaimer

This review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.

The information provided should not be construed as legal, financial, tax, or professional advice.
