Nakamoto Stock Slides to Record Low on $239M Q1 Loss as Company Steps Up Bitcoin Sales

Nakamoto’s pivot into a “Bitcoin operating company” is colliding with market reality. After reporting a first-quarter net loss of nearly $239 million tied to the Bitcoin drawdown, NAKA printed a fresh 52-week low of $0.16 on Thursday before stabilizing around $0.166. That puts the stock down more than 99.5% from its 52-week peak of $34.77—a hard reset for a former medical company now centered on BTC exposure.

Management says the transformation is deliberate: scale operating businesses, grow revenue, and compound shareholder value via disciplined capital allocation anchored in long-term Bitcoin conviction. The operating line, however, remains small relative to balance sheet volatility. Q1 revenue totaled roughly $2.7 million, with about 41% (around $1.1 million) generated by an “actively managed derivatives” program. Leadership has emphasized that Bitcoin on the balance sheet will be managed, not left idle.

That stance materialized in more BTC monetization. Nakamoto sold 284 BTC—about $22 million—as Bitcoin traded above $80,000 on Thursday, surpassing the roughly $20 million of BTC sold in Q4. Management framed the sales as supporting working capital. The company also disposed of 40 BTC (around $3.2 million) earned from option premium income. Even after these transactions, Nakamoto still holds more than 5,000 BTC, valued at over $400 million. Meanwhile, Bitcoin is up around 1.5% in the past 24 hours to about $80,922, roughly 35.8% below its all-time high near $126,080.

The fulcrum issue here isn’t the quarterly mark-to-market loss—it’s the treasury policy. A public “Bitcoin operating company” that actively trades and periodically sells core holdings is taking on a different mandate than a pure HODL vehicle. That choice matters for how the equity is priced, how stakeholders process risk, and how durable the strategy becomes across cycles.

- Strategy design: An options-premium program can smooth cash flow and reduce net cost basis, but it often caps upside at inopportune times and introduces collateral and liquidity management requirements. Without tight guardrails—strike selection, tenor ladders, position limits—the hedge can morph into an opportunity drag or, worse, a source of forced sales during volatility spikes.

- Signal to holders: Selling BTC for working capital helps avoid debt or dilutive equity raises, yet it can read as wavering conviction if not rules-based and pre-communicated. Investors in BTC-centric equities often expect policy clarity: what triggers a sale, what thresholds force risk reduction, what share of holdings can be encumbered.

- Business substance: With $2.7 million in revenue against a $239 million loss largely driven by BTC price action, the operating engine isn’t yet offsetting treasury swings. That’s manageable if investors buy into a transparent framework that harvests volatility while preserving asymmetry. It becomes problematic if the equity turns into a proxy for discretionary treasury timing.

- Governance and fairness: If the company is effectively running a volatility overlay on shareholder BTC, clear disclosures on risk, counterparties, and P&L attribution are essential. Shareholders should understand whether returns come from basis capture, covered calls, or other structures, and what happens when markets gap through risk limits.

What to watch next: - Codified treasury rules: position limits, liquidity buffers, and pre-set sell triggers that reduce narrative whiplash. - Derivatives P&L consistency: premium income as a stable contributor vs. episodic gains offset by larger missed upside or drawdowns. - BTC disposition cadence: whether sales remain tactical and limited, or migrate into ongoing operating funding—shaping perceived purity of the BTC thesis.

Nakamoto still controls a significant Bitcoin treasury and is leaning into active management to bridge operating needs. The market is voting on whether that framework enhances or dilutes the embedded BTC optionality in the equity. Clear, rules-driven execution can narrow that gap; improvisation tends to widen it.