Silicon Peninsula #021 — CXMT's sample milestone moves the qualification watchlist
Monday, November 2, 2026 · For memory sourcing and semiconductor supplier teams · Current reporting and dated-source follow-up
The judgement and the tape
Put CXMT on a qualification watchlist, but do not change an approved supplier list on this evidence alone. The weekend report concerns a technical milestone; a purchasing decision also needs an identified product, customer acceptance and delivery terms. This edition separates that reported development from older production evidence and our scheduled NAVER Cloud CXL follow-up. We omit market prices because we did not verify a current close.
Signal 1 — a reported sample milestone, with a remaining customer gate
Global Times reports that CXMT completed engineering-sample validation of its sixth-generation, 4F² platform, citing a company statement sent to the outlet on October 31. The account says customer qualification precedes progression toward mass production. We have read that reporting, but have not recovered the underlying issuer statement separately or independently tested the samples. Original reporting.
Why it matters: Move the research question from whether a roadmap exists to what the qualification package contains. A buyer should ask for the exact module and revision, the test workload, compatibility requirements, reliability criteria and the party that signs acceptance. These are diligence requests, not documents we claim to possess. A sample can justify technical evaluation while leaving the commercial switching decision open.
The decision sheet
| Observation | Implication | Action before changing a plan |
|---|---|---|
| CXMT sample validation is reported. | Technical progress warrants attention. | Obtain the issuer statement and product qualification package. |
| Customer acceptance remains a separate gate. | A sample is not an accepted delivery. | Define the customer's pass criteria and delivery commitment. |
| A system demonstration is documented. | Workload relevance can be investigated. | Request reproducible conditions and production-service evidence. |
Signal 2 — keep the older production platform in its own row
CXMT's September 20 English announcement explicitly describes G5 mass production and 24Gb LPDDR5X products for mobile devices. Its gross-dies-per-wafer comparison is normalized to an 8Gb baseline. That earlier document supports a different product and milestone; it does not establish server acceptance for the newly reported platform. Company announcement.
Why it matters: Keep platform, product, qualification status and production status in separate columns. Otherwise a reader can accidentally borrow a mobile product's production status to fill an unanswered server question. Likewise, a geometric cell label alone does not tell a buyer the delivered price, usable output or field failure rate. Request those measurements rather than calculate a commercial advantage from a label.
Signal 3 — our NAVER CXL follow-up remains a deployment question
SK hynix's October 16 account describes proof-of-concept validation using NAVER Cloud workloads: KV-cache sharing and embedding sharing for OmniServe. That is documented system work, not an announced paid production-service rollout. In today's review of the cited account and NAVER Cloud's public press list, we did not obtain a later document resolving that deployment question. This describes our search boundary, not the entire private market. SK hynix account; NAVER Cloud press list.
Why it matters: Ask the service owner which workload moves into operation, who measures the benefit and what acceptance condition triggers expansion. A useful follow-up would identify the baseline system, workload characteristics, operating constraints and accountable owner. Do not merge a component sample milestone with a separate system demonstration into a single adoption forecast.
What changed, Korea-only radar and the next review
Compared with issue 020's earnings reconciliation, today's task is product qualification. Compared with issue 011, new reporting advances the CXMT sample question, while independently checked customer acceptance remains unresolved. English reporting already exists, so we claim neither Korea-only exclusivity nor a measured lead. We will update the watchlist when an issuer statement, qualification outcome or identifiable delivery record changes the evidence.
Today's number and seven-day calendar
24Gb is the per-die capacity of the older LPDDR5X products in CXMT's cited production announcement, not a specification for the reported new server platform. Our editorial checks are November 3 for CXMT/FADU documents, November 4 for earnings reconciliation and November 9 for NAVER CXL deployment evidence. These are our review dates, not company promises. Product source.
Silicon Peninsula reads Korean semiconductor filings and company sources, separates documented facts from interpretation, and records the next evidence to check. Reply with a company you want tracked. Our 30-day Korea Watchlist Pilot covers an agreed watchlist; scope is confirmed before payment.
Korea's chip supply chain, read from the source, on Monday, Wednesday and Friday, with additional material alerts.