The unexpected 12% gain in bitcoin's value, denoted as BTC $75,867.72, during the Iran conflict has defied conventional expectations, prompting Bitwise CIO Matt Hougan to offer an alternative perspective. As the largest cryptocurrency outperformed traditional assets, with the S&P 500 falling 1% and gold dropping 10% since the onset of U.S. and Israeli airstrikes on February 28, Hougan posits that bitcoin's performance can be attributed to its dual role. On one hand, it functions as 'digital gold,' competing for a share of the $38 trillion store-of-value market.
On the other hand, it serves as an out-of-the-money call option on its potential to operate as a genuine currency. The Iran conflict has significantly altered the dynamics of the latter bet, as the country announced plans to collect a $1-per-barrel toll in bitcoin from ships traversing the Strait of Hormuz, equivalent to roughly $20 million per day. This move marks one of the first instances of a sovereign state utilizing bitcoin as a settlement mechanism for physical commerce. Hougan's argument, framed within an options framework, suggests that the value of this bet increases when the probability of achieving the strike price improves or the underlying asset's volatility rises.
The Iran conflict has simultaneously enhanced the likelihood of bitcoin being used as a currency and increased the volatility of the global monetary order. If Hougan's perspective holds, it implies that bitcoin may rally during future geopolitical conflicts, particularly those involving countries caught between the U.S. and Chinese financial systems, and that its total addressable market exceeds the gold market alone. However, a counterpoint exists, suggesting that Iran's use of bitcoin stems from necessity rather than preference, highlighting the limitations of dollar-denominated enforcement.
Nevertheless, Hougan's core observation remains valid: the market is pricing bitcoin differently during this conflict than in previous geopolitical shocks, and the 'digital gold' thesis alone cannot account for this shift.