The Ledger
BitcoinZ Rewinds Its Chain After a Block Mints 105 Billion BTCZ
A counterfeit BitcoinZ block created 105 billion BTCZ before emergency release 2.3.1 removed it from the valid chain. The rollback left 150 million wBTCZ on BNB Smart Chain, with the project still undecided on whether to burn the tokens.

Five invalid transactions created 105 billion BTCZ
BitcoinZ block 1,860,181 created 105 billion BTCZ on Oct. 21, before the project’s emergency software release removed the block from the valid chain. The BitcoinZ team says the block contained five Sprout JoinSplit transactions, each claiming to release 21 billion BTCZ without transparent inputs. Their proof data was all zeros.
The BitcoinZ team’s post-mortem corrected a June security audit that had found no way to counterfeit or inflate the coin. The same proof-validation bug had already let an invalid transaction into a June block, according to the project. In October, a separate integer overflow also defeated a check designed to keep the shielded pool’s value within valid limits.
“That finding was wrong.”
BitcoinZ team, authors of the post-mortem
Release 2.3.1 replaced the counterfeit block
BitcoinZ published version 2.3.1 on Oct. 21. The release rejects the counterfeit block and returns upgraded nodes to block 1,860,180; miners then produced a valid replacement for block 1,860,181 at 22:22 UTC. The project says 2.3.1 also fixes the proof check and stops accepting Sprout JoinSplit transactions from that height onward.
The error involved how nodes handled block validation, rather than a stolen private key or a 51% attack. A technical analysis by Safeguard says a cached validation flag could allow a node to skip proof checks after an earlier, less strict check. BitcoinZ’s account confirms the key failure: the node did not verify the Sprout proofs in blocks it received from peers. The project urged node operators, pools, exchanges, wallet backends and explorers to upgrade, because older versions could accept the invalid chain.
For wallet users, BitcoinZ said balances on the valid chain were unaffected and most transparent transactions from the incident window were confirmed again. Shielded transactions anchored at or before block 1,860,180 could be reconfirmed; transactions anchored to a later block could not, because they referred to a note commitment tree that no longer existed. The team advised users whose later-anchored shielded payment or message did not arrive to send it again.
The bridge carried the lasting exposure to BNB Chain
The chain rollback did not reverse activity on BNB Smart Chain. BitcoinZ traced 510 million counterfeit BTCZ sent to its wBTCZ bridge across seven deposits. Three deposits were credited, producing 150 million wBTCZ, which the attacker sold on PancakeSwap for 2,892.18 USDT, according to the project’s transaction-by-transaction account.
The remaining counterfeit BTCZ stayed on the invalid BitcoinZ chain, but the wrapped tokens persisted on BNB Smart Chain after the rollback. BitcoinZ said it had not decided whether to burn the 150 million wBTCZ. Its post-mortem also links the October activity to the June incident, in which an invalid Sprout proof created a 56,305,778 BTCZ withdrawal that remains on the valid chain.
The audit correction leaves a bridge decision open
The June audit had concluded that BitcoinZ could not be inflated; the project has since added a correction acknowledging that its review missed the validation flaw. The October incident shows the separate reach of the defect: fixing the BitcoinZ chain could invalidate counterfeit BTCZ there, but it could not automatically undo tokens already minted on another network.
BitcoinZ’s post-mortem says the network was running on 2.3.1 by Oct. 22 and blocks had resumed at a normal pace. The unresolved figure in the report is 150 million: the wBTCZ minted against the invalid deposits and still awaiting a decision on BNB Smart Chain.
Sources
- Original source BitcoinZ getbtcz.com
Other pages read