JPYC on Upbit: Price Dislocation, Issuance Interruption, and Recovery
JPYC's first Upbit trading day combined three distinct developments: a new South Korean trading venue, a short-lived venue-specific price dislocation, and temporary JPYC EX issuance-reservation interruptions on Ethereum and Polygon. Both issuance routes recovered within hours, and SOG keeps the asset itself active.
Upbit began JPYC trading on September 17, 2026 in KRW, BTC and USDT markets. The launch time was postponed twice and ultimately moved to 18:00 KST. The launch-stage notice specified Ethereum for deposits and withdrawals.
JPYC then traded far above its one-yen issuer reference on Upbit. Yonhap reported 35.7 KRW at 18:42 KST, while Upbit's own asset data later recorded a September 17 all-time high of 37.60 KRW.
The Upbit move was extreme, but SOG does not convert a single-venue listing spike into a permanent JPYC lifecycle reclassification. JPYC EX continued to define issuance and redemption against Japanese yen, and the reviewed evidence does not establish reserve impairment, issuer insolvency, or a lasting inability to redeem at the issuer.
Upbit's data surface subsequently showed JPYC around 9.21 KRW, close to the yen-linked reference region and far below the 37.60 KRW listing-day high. That supports treating the episode as a short-lived market dislocation rather than a durable four-times revaluation of JPYC.
| Network | Suspended | Restored | SOG treatment |
|---|---|---|---|
| Ethereum | Sep. 17, 20:34 JST | Sep. 17, 23:43 JST | Recovered issuance-reservation interruption |
| Polygon | Sep. 17, 22:19 JST | Sep. 18, 00:22 JST | Recovered issuance-reservation interruption |
JPYC's issuer described both as temporary suspensions of issuance reservations while the cause was under investigation. The notices did not say that already-issued JPYC stopped transferring, that redemptions failed, or that reserves were impaired.
The reviewed issuer notices also do not establish that the issuance-reservation interruption caused the Upbit premium. SOG therefore records the operational interruption and the market dislocation as related in time, not as a proven causal chain.
On September 18, JPYC Inc. announced that cumulative issuance through JPYC EX had exceeded JPY 10 billion. That is a cumulative service milestone, not a point-in-time circulating-supply figure.
Independent on-chain analysis by ChainAnalyzer estimated that circulating JPYC rose from about JPY 1.93 billion to JPY 4.41 billion in the roughly 48 hours after the Upbit listing, with most of the increase occurring on Ethereum and Polygon. The same analysis reported that issuer-side flows had turned net-redemption across the four tracked chains during the first half of September 19.
Those on-chain figures are useful market-structure context, but they are third-party analysis rather than issuer accounting. SOG does not promote the address-cluster interpretations or a causal explanation for the listing-day premium into canonical asset facts.
SOG records a provider-scoped South Korea Market Access observation for JPYC spot trading on Upbit from September 17. It is deliberately narrow: it says that eligible Upbit customers gained buy/sell access in the KRW, BTC and USDT markets.
The launch-stage notice specified Ethereum for deposit and withdrawal. At 18:44 KST, Upbit announced that Kaia and Polygon would be added, and at 19:23 KST it updated the notice to say deposits on both networks had opened. SOG therefore records current provider-scoped deposit access across Ethereum, Kaia and Polygon from the September 17 date, while avoiding a withdrawal-effective-time claim that the reviewed update does not establish.
| Question | SOG treatment |
|---|---|
| JPYC lifecycle status | Active — unchanged. |
| Issuer issuance incident | Canonical recovered event covering the Ethereum and Polygon reservation interruptions. |
| Upbit listing | Canonical provider-scoped Market Access record for buy/sell availability. |
| 37.60 KRW high | Material listing-day price dislocation; not treated as a lasting asset-wide depeg. |
| Cause of issuance interruption | Not established in the reviewed issuer notices. |
| Link between outage and premium | Not established; timing alone is not treated as causation. |
| JPY 10 billion figure | Issuer-reported cumulative JPYC EX issuance milestone as of September 18. |
- any issuer postmortem or explanation for the September 17 issuance-reservation interruptions;
- dated Upbit notices that establish when Kaia or Polygon deposit/withdrawal support became effective;
- whether JPYC trading liquidity on Upbit remains close to the yen reference under normal market conditions;
- issuer disclosures that distinguish cumulative issuance from circulating supply and redemption flows;
- any future interruption that affects redemption, reserve access, or already-issued token transfer rather than only issuance reservation.
- Upbit, September 17, 2026 — PYUSD and JPYC trading-support notice — KRW/BTC/USDT markets, launch timing and launch-stage Ethereum network scope.
- JPYC Inc. official X account, September 17–18, 2026 — Ethereum and Polygon issuance-reservation suspension and restoration notices.
- Yonhap News Agency, September 17, 2026 — listing-day JPYC/KRW price dislocation.
- Upbit official Telegram, September 17, 2026 — Kaia and Polygon network-addition notice and 19:23 KST deposit-opening update.
- Upbit Data Lab — JPYC asset summary — recorded 37.60 KRW high, subsequent market data, and current Ethereum/Kaia/Polygon network listing.
- JPYC Inc., September 18, 2026 — JPYC EX cumulative issuance exceeds JPY 10 billion.
- ChainAnalyzer, September 19, 2026 — third-party 48-hour circulation and issuer-flow analysis.