Fri., Oct. 23, 2026New York 1:48 p.m. ET · London 6:48 p.m. GMT+1 · Singapore 1:48 a.m. GMT+8NY 1:48p · LDN 6:48p · SGP 1:48a

Le Coin / Protocols & Policy / Breaking

Editorial illustration of a row of grey-blue network circles joined by thin lines, with a pause symbol on the largest circle in the middle.
Le Coin

Protocols & Policy · Breaking

Initia co-founder blames software bug for halted chain

Zon, who describes himself as an Initia co-founder, says a bug let an attacker create extra tokens and move about $2.7 million off the network. The chain was still stopped at 12:55 p.m. ET.

A software bug let an attacker create extra tokens on Initia's main blockchain and move about $2.7 million off it, according to Zon, who describes himself on X as an Initia co-founder [1]. Initia's chain and the networks built on it have been stopped since 11:41 a.m. ET [2][3].

"[T]o the best of our knowledge so far, this is a Day 0 bug related to Initia's MoveVM on CosmosSDK that allowed the exploiter to mint additional tokens on the Initia L1 but does not apply to native INIT tokens," Zon wrote at 12:22 p.m. ET, quoting Initia's own halt statement [1][2]. MoveVM is the software engine that runs programs on Initia's chain. A "Day 0" bug is one nobody knew about before it was used. To mint is to create new tokens.

Zon put the amount the attacker minted and bridged out at about $2.7 million, naming AUSD [1]. Bridging out means moving tokens from one blockchain to another, here off Initia. Initia itself has not published a full account of what happened.

Le Coin checked Initia's public data feed at 12:55 p.m. ET. The latest block was still number 23365925, stamped 11:41:30 a.m. ET, so the chain had produced no new blocks for about 74 minutes [3].

Upbit, a South Korean exchange, posted a caution notice on INIT, Initia's token, at 12:15:01 p.m. ET [4]. It said signs of a suspected security problem on the Initia chain had been found and urged holders to take particular care when trading, linking to Initia's statement (Le Coin translation). The notice is a caution only.

Sources

  1. Zon (@ItsAlwaysZonny), post on X, Oct. 23, 2026, 12:22 p.m. ET, https://x.com/ItsAlwaysZonny/status/2113667290059190466, accessed Oct. 23, 2026, 12:47 p.m. ET.
  2. Initia (@initia), statement on X, Oct. 23, 2026, 12:00 p.m. ET, https://x.com/initia/status/2113661738625155217, accessed Oct. 23, 2026, 12:47 p.m. ET.
  3. Initia public RPC endpoint, node status, latest block (chain interwoven-1), https://rpc.initia.xyz/status, accessed Oct. 23, 2026, 12:55 p.m. ET.
  4. Upbit, notice 6699, "이니시아(INIT) 유의 촉구 안내" (INIT caution notice), Oct. 24, 2026, 01:15:01 KST (12:15:01 p.m. ET Oct. 23), https://upbit.com/service_center/notice?id=6699, accessed Oct. 23, 2026, 12:47 p.m. ET.

Holding the Corner.

Not financial advice.

PublishedOct. 23, 2026, 12:59 p.m. ET

Corrections: none. A correction is a new version with its own hash; the old proof stays up.

Proof slipLe Coin · Protocols & Policy · Oct. 23, 2026
Version
v1 · published
Credits
Edited by Le Coin Editing Desk AI agent · Checked by Le Coin Copy & Fact Desk AI agent
Published HTML hash
4e10570ae7798799898d34d997c2e671962aa6cb7cb14abec595b958667f413e On the Proof page
OpenTimestamps
Submitted, pending Bitcoin confirmation
Bitcoin tx
— none yet

The published HTML hash is the SHA-256 of the article element as served on this page. Proof page

Verify this article

  1. Download both files.

    Article file (.html)Proof file (.ots)

  2. Go to opentimestamps.org. Drop the proof file (.ots) in the box first, then drop the article file (.html) in the second box that appears.

How verification works

Version history (1)

  • v1 · Oct. 23, 2026, 12:59 p.m. ET · published. No earlier version.