Bitdeer Technologies Group [BTDR]
As of: 2026-07-29 · Spot: $8.92 (2026-07-29 close) · Framework: v1.5.1 / criteria.md 2026-07-29
This memo issues no position verdict — no Long, Short, Watchlist or Avoid. It scores Criteria and outputs an analysis. Whether this analysis justifies a position is a question about a particular book, and the book decides. What follows are the constraints any position would face, not a recommendation.
| Value | |
|---|---|
| Shares traded 2026-07-29 | 2,185,397 |
| Dollar volume | $19.49m |
| Verdict | PASS |
2026-07-29 was a high-volume down day across the entire complex, so this figure is generous relative to a
normal session. Liquidity constrains position sizing, never admission (criteria.md).
No options chain was pulled for BTDR. Liquidity Criteria is explicit: "Any proposed options structure requires the actual chain pulled first — open interest and quoted size for the specific strikes and expiry… A vehicle that cannot be filled is not a vehicle." The HCA precedent (maximum open interest of 18 contracts across an entire March-2027 chain) is why this is a hard rule rather than a preference.
Accordingly no strikes, expiries, Greeks or structures are proposed. Doing so without the chain would
manufacture an uninvestable vehicle. Pulling the BTDR chain from
data.alpaca.markets/v1beta1/options/snapshots is a prerequisite to any options expression.
Common stock only, until a chain is pulled and open interest and quoted size are verified at specific strikes.
criteria.md names inverse-volatility sizing as the active protection on the Downside Criteria, "because a
fat-left-tail name is almost always a high-volatility name and is sized down automatically."
| Value | |
|---|---|
| 252-day realised volatility (screen record) | not in the screen record — BTDR was dropped as INDETERMINATE, so no vol_252d_pct was computed. Peer range 64.7–127.3% |
| Implication | among the highest in any book; inverse-vol sizing cuts this hard |
| One-day move, 2026-07-29 | −13.1% |
On 2026-07-29 every name in this complex fell together:
| HIVE | HUT | IREN | CORZ | BTDR | WYFI | SHAZ | CRWV | APLD | NBIS | WULF | CIFR | RIOT | MARA | CLSK |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| −11.1% | −12.8% | −13.5% | −12.4% | −13.1% | −12.7% | −10.9% | −9.6% | −12.7% | −13.7% | −12.8% | −13.3% | −14.0% | −11.6% | −10.8% |
Fifteen names, one factor, a 4.4pp range. Any two positions in this cluster are effectively one position.
This is a book-level exposure and correlation-limit question, not a single-name question, and it must be
resolved by portfolio-book before any BTDR position is sized. Treating cluster members as independent names
would breach the correlation limit while appearing diversified.
Confirming observable: the FY2026 20-F showing (a) the $108.3m ASIC hardware line persisting or growing, (b) gross margin recovering from 9.8%, and (c) the $753.8m of current borrowings refinanced or repaid without material dilution. All three are needed; the hardware line alone is not enough if margin keeps falling.
Refuting observable, in priority order: 1. Failure to refinance the $753.8m of current borrowings, or refinancing at materially dilutive terms. This is the binding constraint and it includes $275.0m owed to a related party. 2. Gross margin below 9.8%. It has fallen 21.1% → 19.0% → 9.8% over three years while R&D rose to 24.8% of revenue. A fourth consecutive decline would establish that scale is not producing operating leverage. 3. The ASIC line reverting toward zero. It went $2,000 → $585,000 → $108,328,000; a single year is not a trend, and it is the only genuinely non-bitcoin, non-declining revenue line BTDR has. 4. Any disclosure on the $135.6m of "cryptocurrencies — receivables" identifying a counterparty of poor quality.
The structural problem with all of the above: none of it is observable until roughly April 2027. BTDR has no quarterly reporting obligation. A position here is unmonitorable on a quarterly cadence, which is a position-construction fact, not merely an inconvenience.
portfolio-book.