06-reference/research

cxmt ddr5 cost per bit yield parity tripwire

2026-09-12·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
memory-cyclecxmtdramcost-per-bittripwireinvesting-thesis

CXMT's DDR5 cost-per-bit tripwire: not tripped, unlikely by year-end, and keyed to the wrong mechanism

The question

"Does CXMT reach DDR5 cost-per-bit within ~10% of the big three by ~late 2026 (yield-parity tripwire) - the point at which aggressive pricing becomes sustainable rather than loss-making, flipping CXMT from Phase-3 accelerant to Phase-2 pricing-discipline breaker?"

Context: this is the second of the two tripwires the parent brief [[2026-07-03-cxmt-dram-capacity-memory-oligopoly-risk]] proposed. The first (bit-share) was derived in [[2026-09-08-cxmt-ymtc-bit-share-phase3-threshold]]. This brief does the same job for the cost leg of tripwire row 5 in [[2026-07-07-dram-hbm-phase2-phase3-early-signals]].

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Verdict: NOT TRIPPED as of 2026-09-12 (medium-high confidence). Tripping by end-2026: unlikely (Ray estimate: roughly one-in-five or less). The exact crossing date cannot be known from public data. The arithmetic runs as follows; every step is a Ray derivation from the numbers above. Cost per bit ≈ wafer cost ÷ (density × yield). The density ratio alone (~0.40 vs 0.239 Gb/mm²) would make CXMT's cost ~67% higher. The observed gap is only ">30%", which implies CXMT's cost per processed wafer runs at roughly 75-80% of the big three's (cheaper domestic inputs, no EUV depreciation, subsidised capital). If that wafer-cost advantage holds, reaching 1.10x needs CXMT's density at about 0.28 Gb/mm² against today's big-three baseline, or about 0.32-0.33 Gb/mm² once the big three's own 1b-to-1c shrink is counted. In practical terms, CXMT's 16Gb DDR5 die must shrink from 67 mm² to about 48-56 mm², a 15-30% cut, and the new node must yield well within one to four quarters. G3 to G4 delivered a ~20% cell shrink over roughly two years. A full ramp of a successor node with that yield by December is not supported by anything found. The Sept 8 brief's flat bit-share-to-capacity ratio (~0.7) reaches the same conclusion from a separate direction.

The larger finding: the tripwire is keyed to the wrong mechanism, so it would not flip CXMT to a Phase-2 breaker even if it tripped. The question assumes aggressive pricing is currently "loss-making" for CXMT. It is not. At an 80-88% gross margin, CXMT's cost of goods is 12-21% of today's price. Even with a 30% cost disadvantage, it could cut DDR5 prices by more than half and stay gross-profitable. What stops CXMT from breaking pricing discipline in Phase 2 is volume and incentive, not cost. It is capacity-constrained, it sells everything it makes into a market TrendForce models at -1% to -2% sufficiency, and a sold-out seller gains nothing by undercutting. Relative cost-per-bit becomes load-bearing only at the trough. That is when prices fall toward the big three's cash cost and a 30% disadvantage means losses, while a 10% disadvantage means rough breakeven alongside the marginal incumbent. Even then, CXMT's state-backed ~77% capex intensity means losses slow it less than they would slow a market-funded competitor. So cost parity is a Phase-3 depth-and-duration variable. It sets how low and how long the down-leg runs and how much share CXMT takes on the way down. It is not a Phase-2 trigger. This matches the Sept 8 result on the share leg: on DRAM, both China legs lower the threshold rather than trigger Phase 3, and the trigger is still a demand event.

What to change in the instrumentation (reversible, no posture change). First, memory-cycle-v1.1 posture is unchanged and no disqualifier trips. Second, move the cost leg out of tripwire row 5a's AND-condition and re-file it as a Phase-3 severity modifier: "if Phase 3 starts while CXMT's cost gap is ≤10%, expect a deeper and longer trough and faster share loss for Micron in commodity DRAM." Third, drop the name "yield parity" and replace it with "density/cost parity". Yield is plausibly already close to peers; density is the gap. Fourth, replace the unobservable cost-per-bit number with the proxies below. The cleanest of them does not need a teardown. It is margin beta in the first down-quarter: when contract prices first fall, a higher-cost producer's gross margin compresses faster than peers' in percentage points. If CXMT's margin falls less than SK hynix's and Micron's DRAM margins in the same quarter, the cost gap has closed, whatever SemiAnalysis's number says.

Indicators to monitor

# Observable Source and cadence Crossing condition Next read
1 CXMT gross margin vs SK hynix / Micron, quarter-aligned CXMT A-share quarterly reports; SK hynix and Micron earnings Q2's +3-4pp gap over peers persists through Q3 despite mix differences (tests explanation d) CXMT Q3 report, due by Oct 31 2026
2 Margin beta in the first quarter of falling contract prices Same, paired with TrendForce contract pricing CXMT's margin drop in pp ≤ peers' drop First down-quarter (not expected in 2026)
3 Die size of CXMT's next-node 16Gb DDR5 TechInsights teardown (report is gated; headline and blog summaries are usually public) Die ≤ ~56 mm² (watch) / ≤ ~48 mm² (trip) Whenever the G5-class part ships at retail
4 An independent refresh of the ">30%" cost-per-bit estimate SemiAnalysis, TrendForce, Counterpoint commentary Any second house at ≤15%, or SemiAnalysis revising below 20% Ad hoc
5 CXMT's discount to big-three contract DDR5 TrendForce contract/spot bulletins, channel reports Discount widens past ~15-20% while the market is still short, which would signal that CXMT is choosing share over price Monthly
6 CXMT inventory days CXMT balance sheet, now quarterly Rising inventory = unsold bits, the actual precondition for price aggression CXMT Q3 report

Indicator 6 is the one that links the cost question to the discipline question. Cost parity with empty warehouses changes nothing in Phase 2. Rising CXMT inventory at any cost gap is the early sign that the price discipline around CXMT is starting to fail.

Why this is in the vault

It closes the second of the two CXMT tripwires that the 2026-07-03 brief proposed. The recommendation is to re-key row 5 of the 2026-07-07 tripwire table: move the cost-per-bit leg from a Phase-2 trigger condition to a Phase-3 severity modifier, with named quarterly proxies. That completes the China-entrant re-keying of the memory-cycle-v1.1 trigger stack that the Sept 8 brief began.

Open follow-ups

Related

Sources

Vault

Web