Blockchain Rollback After an Exploit: What Happens to Your Tokens When a Chain Is Reset

A blockchain is treated as a ledger you can only add to at the end. That very promise is up for debate whenever a protocol, hit by an attack, starts weighing a rollback. Because a rollback does not erase only the attack. It also erases the purchases and transfers of uninvolved holders.

Since August 12, 2026, this can be watched in a live case: on the layer-1 chain Harmony, an attacker created roughly four billion ONE out of nothing, according to an external analyst's estimate. The team shipped an emergency patch and has been weighing a rollback of the chain ever since. This article explains what happens technically in that process, why the window for an unwind closes fast, and what an unwound purchase means for your holding period.

What a blockchain rollback is and why it breaks the promise of immutability

A rollback is a network's agreement to reset the state of the chain to an earlier block and to keep writing from there. Everything that happened between that block and the decision drops out of the recognised history.

A rollback is not a button a board presses. It works only if enough validators or miners install a software version that treats the old state as valid. Anyone who does not follow along stays on the old chain. Immutability therefore rests on an agreement that carries technical costs.

A reorg and a rollback are two different things

A reorganisation, reorg for short, belongs to normal operation and concerns one or two competing blocks. A rollback, by contrast, reaches back in a coordinated way over hours or days.

The Harmony case: four billion ONE from a faulty cross-shard receipt

On August 12, 2026, the Harmony team confirmed an incident on mainnet in which ONE tokens were created without authorisation. The protocol instructed validators to install the emergency version v2026.1.1, halted its own bridge and asked exchanges to block balances from four named addresses. In its own words, it was working on "a patch and rollback options".

On the amount there is still no confirmation from Harmony itself. The on-chain analyst Juiceberg estimated roughly four billion newly created ONE, a premium of about 26 percent on the roughly 15 billion previously in circulation; some 2.8 billion of them are said to have reached exchanges. These figures come from an outside observer and are expressly not confirmed by the protocol, as CryptoSlate notes.

The price loss on the day of the incident ranged between roughly 26 and 40 percent depending on the measurement point, as CoinDesk traced over the course of the day. More important than the percentage is the state that has persisted since: the patch prevents further minting, no decision has been taken on the tokens already created, and a block from which a reset would start had not been named by the team as of mid-August.

A protocol with a history

It is not the first incident: in 2022, roughly $100 million was taken through the Horizon bridge, and in 2023 a staking bug produced roughly 146.3 million ONE too many.

Infinite-mint exploit explained: how a validation flaw becomes new money supply

Infinite mint describes attacks in which an attacker gets the protocol to credit them a balance without anything being debited elsewhere. So no money is stolen; money is created. For the remaining holders the effect is the same as with a theft.

At Harmony the published code changes centred on the cross-shard receipts that carry the result of a transaction from one part of the chain to another. The first weakness lay in the quorum check: the verifier counted the full committee instead of the validators actually represented, so a receipt went through without the necessary approvals. The second lay in the marking that a receipt has already been spent: because individual proof fields were not bound to the signed block header, a processed receipt could look like a new one. The destination shard credited the amount again without the source shard being debited, and it is in that gap that the additional money supply arises.

The pattern is not new. In April 2026, a flaw in a bridge's proof procedure created more than a billion counterfeit DOT on Ethereum, with thin liquidity limiting the damage. You will find the comparison in our write-up on the Hyperbridge exploit at Polkadot.

Patch, freeze and rollback: a protocol's three tools after a mint exploit

A protocol has three means at its disposal, and each later one is harder to enforce than the one before.

First: the patch

The emergency patch closes the gap so that nothing more is added. But it only takes effect once a sufficient share of validators has installed it. At Harmony, reports say roughly 53 percent had updated about four hours after release. That ratio is the yardstick of an emergency response, not the speed of the press release.

Second: the freeze

Freezing works only where someone holds control, that is, at centralised exchanges and stablecoin issuers. The protocol publishes addresses and asks for a block; whether the exchanges respond is their own decision. At Harmony, it was disclosed neither which venues went along nor what amount was frozen. The effectiveness is therefore barely verifiable for you.

Third: the rollback

The rollback is the most expensive means. It requires a majority of validators, the consent of the largest venues and a community that accepts the break with immutability. The longer the vote drags on, the more uninvolved transactions hang on the period that is to be erased.

Why a rollback gets harder once the tokens have reached the exchanges

As long as the unauthorised tokens sit on the chain, an unwind is technically clean: the blocks concerned fall away, the tokens no longer exist, and no one outside has paid anything for them. Once the attacker has sold them on a centralised exchange, the process has stepped out of the chain: the buyer handed over real euros and holds a claim in the exchange's books in return.

A rollback of the chain does not undo that trade; it only devalues the basis on which the exchange made the credit. The gap between chain state and internal ledger then has to be carried by someone: the venue out of its own pocket, or the customers through adjusted balances. The estimate that roughly 2.8 billion tokens reached exchanges at Harmony therefore above all describes how small the window for a clean unwind has become.

Ethereum 2016 and Ravencoin: what earlier rollback decisions show

The best-known case is the attack on The DAO in the summer of 2016. The Ethereum community opted for an unwind, part of the operators did not go along, and the chain split; the variant without the unwind runs to this day as Ethereum Classic. The underlying risk: in the end there can be two chains and two tokens, and your holding sits on both, with very different values.

One day before the Harmony incident, it struck Ravencoin, whose network had accepted invalid blocks. The miners rebuilt the chain from a point before the flaw, putting several days of transactions at risk. Both cases show the same trade-off: whoever reverses an attack always reverses legitimate transfers as well.

Exchange account or self-custody: where a rollback hits you differently

If your tokens sit on a centralised exchange, you legally hold not a coin but a claim against the venue. In an emergency the venue decides what happens to your balance: deposits and withdrawals are stopped, trading is suspended, and whether your holding stays unchanged depends on the provider's booking practice.

In self-custody it is the other way round. Your key stays valid, but the chain state decides what it controls. If a reset happens, the account balance of the restored block applies to you, and every transaction after it is gone. Anyone wanting to self-custody will find the device classes in our hardware wallet comparison.

A common misconception persists here. A hardware wallet protects your private key from outside access. It does not protect you against a change in the money supply at the protocol level, and just as little against a rollback. Both happen one layer down, where the validity of the chain is decided.

Acquisition date and holding period: what an unwound purchase triggers for tax

In Germany, gains from selling crypto assets held as private assets are treated as a private disposal transaction under Section 23 of the Income Tax Act. What counts is the one-year period between acquisition and disposal: if it is exceeded, the gain stays tax-free; below it, the €1,000 exemption threshold per calendar year applies. How that works in practice is set out in our explainer on the holding period for cryptocurrencies.

A rollback calls into question the very figure this calculation hangs on: the acquisition date. If the block your purchase sits in falls out of the chain and the transaction is executed later or not at all, the start of the period shifts, or the deal never came about. For this case there is no explicit rule in Germany you could rely on.

What you take from this in practice

Do not rely on your software reconstructing it later. Portfolio and tax programs draw their data from exchange interfaces and from block explorers. If the chain is reset, one source changes retroactively while the exchange data stays put, and from that moment the two states diverge.

So save your exchange's transaction history as a file while it is still available, keep the transaction hashes of your own transfers, and note the time and price of your purchases. These records are the only basis on which a diverging chain history can later be explained to the tax office. For larger amounts, the case belongs with a tax adviser.

How to gauge, before buying, how large a chain's rollback risk is

The ability to rescue quickly and the ability to rewrite history are the same ability: a network in which a small team rolls out a patch within hours and everyone follows can just as quickly decide on an unwind. Watch for these features:

• Number and distribution of validators. A few dozen operators who know one another decide differently from thousands of nodes.
• Track record. A protocol that has already put addresses on a block list will do it again.
• Complexity of the architecture. Sharding, bridges and cross-chain receipts enlarge the attack surface, because every handover of value is a check.
• Verifiability of the money supply. Can the circulating amount be recalculated independently from the chain's raw data? In the Harmony case that was a problem, because the reported total did not show the increase at first.
• Communication in an emergency. Anyone who, after days, has named no reference block and no figures has not reached agreement internally.

None of these features is a knockout on its own. Together, though, they tell you how much trust the finality of a booking on this chain deserves.

Gauging rollback risk: what to take away

1. Separate the venue from custody deliberately. Keep on an exchange only what you actively trade, and check your provider's terms and supervision in the comparison of regulated crypto exchanges.
2. Document your acquisitions independently of the chain. Export the transaction history regularly and store the files off the exchange. Which programs output them in a form fit for the tax office is shown in the crypto tax tools and portfolio trackers.
3. Move larger holdings into your own custody, but with realistic expectations. Your key protects against outside access, not against decisions of the protocol. The right devices are in the hardware wallet comparison.

(As of August 15, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)