Coinbase’s new B20 stock tokens on Base place Apple, Alphabet, Meta and Nvidia-linked exposure on a blockchain that keeps trading through the weekend.
AAPLc, GOOGLc, METAc and NVDAc confer beneficial claims on underlying shares held within Coinbase’s tokenization structure; they are designed for eligible users outside the United States and differ from ordinary US-listed shares.
Coinbase describes continuous secondary transferability, while Base presents the assets as building blocks for decentralized finance. That DeFi pitch includes a prominent borrowing example. Base says a holder could use tokenized Nvidia exposure as collateral on Aave, creating an obvious risk question when the token continues trading and the underlying equity market is closed.
A Sunday review of the official Aave V3 Base address book found no reserve for any of the four tokens. The weekend therefore produced two separate findings: secondary-market prices were observable, while Aave lending behavior had no verified live B20 market to measure.
At 05:45–05:47 UTC on Aug. 30, the four leading Aerodrome USDC pools traded within roughly 0.6% of Chainlink reference values last updated Friday. Those held references make the measurement a snapshot of weekend token pricing against the last available equity-linked values. They do not provide a continuously refreshed estimate of the underlying shares.
Coinbase stock tokens separate continuous token trading from the operational rails behind the claim. Coinbase’s product page says primary minting and redemption are handled by KYC-onboarded institutional partners and Authorized Participants. Once issued, Base says the tokens can be transferred without wallet whitelists and traded through always-on automated market makers. A trader can therefore buy or sell tokenized exposure even while the primary US equity market is closed.
A snapshot of the leading Aerodrome pools at 05:45 UTC showed about $6.07 million in aggregate displayed liquidity and $7.08 million in aggregate 24-hour volume. DEX Screener defines pool-liquidity and volume fields for its live endpoint, but displayed liquidity remains a rough depth indicator. It does not promise that a trade of a particular size will clear near the quoted price.
The four official Chainlink feed proxies at 05:47 UTC returned Friday update times: 17:01:55 UTC for AAPL, 15:59:21 for GOOGL, 19:10:19 for META and 18:50:11 for NVDA. Comparing those held values with DEX Screener’s rounded dollar prices produced this Sunday snapshot:
All four gaps were smaller than 0.6% at the cutoff. This supports a dated statement about prices in those pools, rather than a durable peg, an issuer-solvency test or a guaranteed arbitrage relationship. Prices, volumes and pool balances can change after the timestamp. The comparison also says nothing about the execution price available for a large order.
The small gaps are still informative. Traders had a weekend market and chose prices close to the held equity references, despite the lack of fresh primary-market discovery. That behavior kept the first measured dislocation contained. Its relevance to collateral depends on a second layer: the rules a lending application uses when its reference feed stops advancing.
Base’s B20 integration guide says the launch assets use Chainlink 24/5 total-return feeds. Each value is derived from the underlying equity price and a multiplier, rather than the token’s DEX price. On weekends and holidays, the feed holds the last value and its updatedAt timestamp stops advancing. The Friday timestamps observed on Sunday were consistent with that documented behavior.
The weekend state reflects the feed’s schedule. It is distinct from an oracle outage. Chainlink’s equity-stream documentation describes extended market coverage and market-status data, while Base tells integrators to inspect updatedAt, apply staleness bounds and avoid settling or liquidating against a frozen value. Data delivery supplies the inputs; an application’s contracts still decide whether collateral can be deposited, borrowed against or liquidated.
That separation becomes important when the DEX market moves during a closed reference window. A sharp rise in the token price would not automatically lift a feed calculated from the held equity value. A sharp decline would require equally explicit handling so that a lending protocol does not rely on stale information for liquidations.
The Sunday prices remained close enough that this hypothetical pressure never emerged in the measured pools, yet the schedule mismatch remained present for roughly 35 to 38 hours at the snapshot.
Coinbase’s public page says primary creation and redemption are limited to KYC-approved institutional partners and Authorized Participants. The NVDA prospectus separately gives a “Vested Holder” a redemption right subject to prescribed instructions, compliance checks and operational acceptance.
The prospectus contains no categorical weekend bar on submitting an order. It defines a business day to exclude Saturdays, Sundays and holidays, and cash or stablecoin settlement requires the issuer to sell the underlying shares after validating a request. The terms also allow rejection, delay, suspension or modification in specified circumstances. Accordingly, the underlying sale and settlement process cannot be assumed to provide instant weekend arbitrage even while the token itself keeps trading.
For Coinbase stock tokens, this is the core 48-hour gap: the onchain secondary market remains available, the equity-linked feed follows a 24/5 schedule, and underlying execution and settlement retain business-day dependencies. A tight Sunday spread reduces the observed dislocation at one point in time. The different operating clocks remain in place.
The official Aave V3 Base address book contained no reserve, aToken, variable-debt token or Aave oracle entry for AAPLc, GOOGLc, METAc or NVDAc at the Sunday review. That finding is limited to the official V3 deployment list. It does not rule out every unrelated or unindexed contract anywhere on Base, yet it is the authoritative record for evaluating whether the marketed Aave use case had current V3 reserve parameters.
The forward-looking record points to work still ahead. An Aug. 3 Aave governance proposal said the initial assets, oracle configuration, risk framework and deployment contracts for V4 on Base would be finalized and published later. The proposal establishes direction, while leaving the B20 asset list and its risk controls unresolved.
No defensible live values were therefore available for a B20 loan-to-value ratio, liquidation threshold, supply cap, borrow cap or outstanding borrowing. There was also no verified Aave B20 liquidation activity from which to infer closed-market behavior. Base’s reference to Aave describes an integration goal; a live lending market requires deployed reserves and inspectable parameters.
Those eventual parameters will determine whether the timing mismatch becomes manageable collateral infrastructure. A lending deployment would need explicit oracle-freshness checks and a policy for deposits, borrowing and liquidations during closed reference periods. Conservative LTVs and liquidation thresholds could provide buffers. Supply and borrowing caps could bound exposure. None of those controls can be credited to the four tokens before the contracts and settings exist in the verified market.
The first weekend nevertheless supplied a useful baseline. Four active Aerodrome pools generated about $7.08 million of 24-hour volume and stayed within roughly 0.6% of held Friday values at the timestamp. That is evidence of orderly secondary-market pricing during one closed-market window. Its limits are equally concrete: the reference feeds were carrying Friday information, the prospectus preserved business-day dependencies for underlying sales and settlement, and the promoted Aave collateral layer lacked a verified live reserve.
Coinbase has made the market-hours mismatch visible onchain. The decisive stress test will begin only after a lending venue publishes its B20 reserve configuration and users place debt against the tokens. Until then, this weekend’s record belongs to the DEX and oracle layers, with collateral safety still awaiting deployed controls.
