Skip to content
Data provided by CoinGecko
Brief

Crypto brief: October 30, 2026

October 30, 2026 was the first full day of writing after the Binance drain. The exchange updated its notice. A tracing firm published its own assessment the same morning. Neither item replaces the desk special.

Away from that incident, Hashdex filed an 8-K: Jane Street Capital signed an authorized-participant agreement for the Hashdex Nasdaq CME Crypto Index ETF. The agreement date in the filing is October 27. The file date is October 30. Kraken’s status page reported a spot and derivatives connectivity break that lasted about an hour, from 02:42 UTC to 03:42 UTC.

On Ethereum Research, a cryptography note set out a signatureless way to authorize actions with a fresh zero-knowledge proof. Figures in this brief are the ones those pages stated. They are not a later market snapshot. Bitcoin’s history, Ethereum’s history, and the stablecoin glossary are the background links.

  1. Hashdex files Jane Street as an authorized participant

    A Form 8-K for the Hashdex Nasdaq CME Crypto Index ETF, filed October 30, 2026, reports a material agreement. On October 27, 2026, Jane Street Capital, LLC entered an authorized-participant agreement, acknowledged by the trust and by Hashdex Asset Management Ltd. as sponsor. The filing says the agreement sets the procedures for creating and redeeming baskets. It does not report a creation or a redemption on that date, and it does not state an asset total for the trust.

    Source: SEC EDGAR

  2. Binance's October 30 update puts the freeze near $3 billion

    Binance updated its incident notice on October 30, 2026. At that update the company said about $3 billion had been frozen, that investigators had not found a private-key leak, and that withdrawals stayed suspended while deposits remained open. The notice said customer balances would be covered with company funds and the SAFU reserve. It said a proof-of-reserves snapshot would follow remediation, and it did not give a date for that snapshot.

    Source: Binance

  3. Chainalysis assesses the drain as TraderTraitor

    Chainalysis published its Binance findings on October 30, 2026 at 09:34 UTC. The firm assesses the hack, which it sizes at $6.4 billion, as the work of the North Korean group TraderTraitor, based on on-chain activity in the hours after the theft. The post says funds began leaving Binance hot wallets around 4:20 p.m. Eastern on October 29. On Ethereum, it says, an operational wallet funded through Tornado Cash submitted signed authorizations. This is the firm's assessment, not a government finding. The FBI alert came the next day.

    Source: Chainalysis

  4. Kraken spot and derivatives drop for about an hour

    Kraken opened a spot-exchange connectivity incident at 02:42 UTC on October 30, 2026 and marked it resolved at 03:42 UTC. The first notice said the break affected spot and derivatives clients on web and mobile, and on REST, WebSocket, and FIX connections, including clients trying to submit orders. The page later marked the incident resolved. It did not publish an order count or a loss figure.

    Source: Kraken Status

  5. A draft describes short-lived capability tokens

    A second Ethereum Research post on October 30, 2026, at 05:23 UTC, describes scoped capability tokens for a proposal it calls STVA. The tokens are short-lived, limited to a purpose, and revocable. The post says they can be EIP-712 typed data or ERC-1271 compatible, and that they grant only a named action, such as an upgrade or a transfer of a set amount. It says a simulation result can be bound into the capability. This is a forum draft, not an accepted standard.

    Source: Ethereum Research

  6. A research note sketches signatureless authorization

    A note on Ethereum Research, posted October 30, 2026 at 07:13 UTC, argues that post-quantum signatures change the cost of proving authority. It describes signatureless authorization: an authority publishes a commitment to a reusable secret, and each action is authorized by a fresh zero-knowledge proof of knowledge of that secret, bound to the action. The note says the hard problem is safe reuse, because an attacker can collect valid proofs. It is a research post, not a shipped standard.

    Source: Ethereum Research