{"id":12837,"date":"2026-09-04T21:24:19","date_gmt":"2026-09-04T21:24:19","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=12837"},"modified":"2026-09-04T21:24:19","modified_gmt":"2026-09-04T21:24:19","slug":"xrp-futures-yield-gap-reveals-bitwises-97-5-hedge","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=12837","title":{"rendered":"XRP futures yield gap reveals Bitwise\u2019s 97.5% hedge"},"content":{"rendered":"

<\/p>\n

\n

Bitwise has given the market a rare look inside an institutional XRP carry trade.<\/p>\n

The Bitwise Crypto Carry Fund, or USCC, paired XRP held in custody with an almost equal short position in September Coinbase XRP futures. The structure was 97.48% matched by quantity, leaving limited exposure to a parallel move in XRP while positioning the fund to collect the premium between futures and spot.<\/p>\n

At 4 p.m. EDT on Sept. 1, Bitwise’s holdings table showed 10,781,438.36 XRP in custody and a displayed futures quantity of negative 10,510,000. The futures row carried a 14.57% implied-yield label.<\/p>\n

The disclosure supports a specific conclusion about one private fund: XRP was serving as inventory for a near-market-neutral basis trade. Broader institutional XRP demand, including demand for Bitwise’s separate spot product, remains outside the scope of this position.<\/p>\n

How a 0.91% premium becomes a 14.57% annualized rate<\/h2>\n

The hedge coverage comes first. Dividing the futures quantity by the custody quantity produces a 97.48% offset and a residual long position of 271,438.36 XRP. The displayed notionals differ by $232,776.<\/p>\n\n\n\n\n\n\n\n
USCC XRP leg<\/th>\nDisplayed quantity<\/th>\nNotional value<\/th>\nCalculated unit mark<\/th>\n<\/tr>\n<\/thead>\n
Custody<\/td>\n10,781,438.36<\/td>\n$14,255,218<\/td>\n$1.3222<\/td>\n<\/tr>\n
September Coinbase futures short<\/td>\n-10,510,000<\/td>\n-$14,022,442<\/td>\n$1.3342<\/td>\n<\/tr>\n
Calculated difference<\/td>\n271,438.36<\/td>\n$232,776<\/td>\nNot applicable<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\"Infographic\"Infographic<\/p>\n

The spread is the second number. Dividing each notional by its displayed quantity produces a spot-equivalent mark of about $1.3222 and a futures-equivalent mark of $1.3342. The futures level was therefore roughly 1.2 cents, or 0.91%, above spot.<\/p>\n

Cash-and-carry strategies seek to monetize that gap. A fund buys the asset and sells a future trading above it; convergence at settlement can lock in the premium while much of the asset’s directional move cancels between the two legs. Bitwise describes USCC as a qualified-purchaser fund built to capture futures premiums over spot across crypto markets.<\/p>\n

Annualization produces the third, and largest, number. Bitwise defines holding-level implied yield as an annualized figure if the position is held to maturity or otherwise not sold. Its 14.57% label therefore expresses a short-term premium as a yearly rate. The two displayed XRP marks differ by 0.91%.<\/p>\n

Realized investor returns use a separate measure. Bitwise reports the fund’s 30-day yield separately and lists a 0.75% management fee. The public methodology leaves the XRP line’s treatment of execution, financing, custody, margin and roll costs unspecified, so 14.57% is best read as Bitwise’s annualized implied rate for the displayed futures holding.<\/p>\n

Residual risks remain even with a 97.48% quantity match. Spot and futures prices can move differently before settlement, the fund must maintain custody and margin, and the cash-settlement benchmark may differ from the price available for its custody inventory. The remaining 271,438.36 XRP also retains direct price exposure.<\/p>\n

The public table supports the quantity comparison while leaving the contract count unresolved. A Coinbase Derivatives filing specifies 10,000 XRP for its standard monthly XRL future. Coinbase lists multiple XRP futures products, however, and Bitwise identifies the venue and month without publishing a product code. Any conversion of the displayed quantity into a number of contracts would therefore be conditional.<\/p>\n