If you sent a transaction on the Cronos chain on August 30, 2026 between 12:38 and 14:33 UTC, it no longer exists today. Your balance stands at the value it held before that window. For most holders this is not expropriation but a complete reversal: whatever went out in that period was never debited either. There are cases, though, in which it does turn into real damage. This article shows you exactly which time window is affected, how to check your own transaction in a few minutes, and where the all-clear stops.
On September 8, 2026 the team behind Cronos published its post-mortem on the attack against the lending protocol Tectonic. A post-mortem is a project's after-the-fact investigation report into an incident. Only there do the hard numbers appear that had been missing until then.
The sequence, as the trade publication Cointelegraph relays it from the report: the attacker drove the price of the TONIC token up almost three hundred fold on thinly traded venues. A lending protocol lends out funds against posted collateral and values that collateral continuously through a price feed. That valuation is exactly where the attack landed. Against the artificially inflated collateral, the attacker borrowed $120.4 million across nine lending markets, spread over eleven transfers. The initial stake was around $5 million.
The incident was detected at 12:49 UTC, according to the report. At 14:32:47 UTC the network came to a standstill. The developers describe it as “a hard decision, taken together with the validators, weighing the finality users expect from a chain against the funds at risk”. A validator is an operator that proposes and confirms blocks; on a chain with a few dozen such operators, a coordinated agreement is technically feasible.
We described the network halt itself on August 31 in Cronos halts the chain after the Tectonic exploit. That article ended at the standstill, because the post-mortem was still outstanding at the time. This one supplies the resolution.
A block is a package of transactions that a blockchain records in fixed order. A rollback is the coordinated reset of a chain to an earlier block: everything confirmed after that point is discarded, and the chain is rebuilt onward from there.
By its own account, Cronos discarded 10,961 blocks. That amounts to one hour and 54 minutes of chain history. What matters for you is the sentence that appears in the reporting on the post-mortem: every transaction in that window was reversed, regardless of whether it had anything to do with the attack. Open positions in running applications were repriced when the chain restarted.
In terms you can orient yourself by: the reset point sits at the block carrying the timestamp August 30, 12:38:55 UTC. The standstill began at 14:32:47 UTC. Everything in between is discarded. Block production only resumed at 23:49:01 UTC the same day, a good eleven hours after the reset point.
In the basic case the answer is no. Your balance was reset to its state as of August 30, 12:38:55 UTC. A transfer you sent at 13:10 UTC has vanished, and with it the debit. A swap you executed at 14:00 UTC never took place, so you hold the original token again. Funds that sat at your address before 12:38:55 UTC are still sitting there unchanged.
The all-clear has edges, though, and those are the real reason for this article:
The post-mortem names one important practical limitation itself: according to Cronos, the reversed transactions can only be traced through archived records, no longer through the public block explorers. Anyone who needs proof should therefore build it from their own documentation.
The check requires no expertise and no extra tooling. A block explorer is a website that makes the current contents of a blockchain searchable. Important for understanding it: it shows you the chain as it stands today, meaning the rebuilt version.
Call up the official Cronos block explorer and enter your receiving address. You need neither connect your wallet nor enter a key. An address is a public identifier; whoever searches for it can move nothing.
Look at the transaction list around August 30, 2026. The window that counts runs from 12:38:55 to 14:32:47 UTC. Convert it to your own time zone; in Central European Summer Time, two hours ahead, the window falls between roughly 14:39 and 16:33.
If you find no entries in that window, your address was not affected. If you do remember a movement in that period and it is missing, then it was discarded. The funds it would have moved are back where they were before.
Save the transaction hash, the unique identifier of your transfer, along with the timestamp and amount from your wallet history or from a confirmation email. These records are the only proof left to you if you have to explain to a trading counterparty, an exchange or the tax office why an event is missing from the chain.
The limit of such a reset runs exactly along the chain boundary. A blockchain can rewrite only its own history. Once value has moved across a bridge to another chain, an independent and valid event sits there, out of reach of the resetting chain. A bridge is an application that transfers value from one blockchain to another by locking on one side and issuing on the other.
That is precisely what happened here. According to the post-mortem, $9.19 million had already left the chain before the halt, 7.6 percent of the affected sum. Those funds count as not recovered. Cointelegraph, citing the data service Bitquery, puts the share traced onto the Ethereum blockchain at $8.3 million. The reversal therefore undid $111.2 million and failed on the remainder.
For you as a holder, a sober rule follows: a reset protects you only as long as the event has not left the chain. How such an intervention works in principle and which cases it covers is something we described in general terms in what happens to your tokens when a chain is rolled back. The Cronos case is the first major application of that mechanism this year.
You do not have to take the project's figures on trust. The event leaves an imprint that anyone can measure with a simple query. We did so on September 10, 2026 at around 00:40 UTC via the chain's public access point.
The chain ID was 25, the Cronos mainnet, and the height stood at 92,926,013 blocks. The block numbered 90,896,189 carries the timestamp August 30, 12:38:55 UTC. The block immediately following it, 90,896,190, carries the timestamp August 30, 23:49:01 UTC. Between two consecutive blocks there is thus a gap of 11 hours, 10 minutes and 6 seconds, where a few seconds would normally sit. That jump is the standstill.
The second measurement is more telling still. The block numbered 90,907,150, the height at which the chain was halted according to the report, carries the timestamp August 31, 05:59:27 UTC on today's chain. It was therefore created a good 15 hours after the attack. These block heights have demonstrably been produced anew. The branch that users saw as confirmed on August 30 has disappeared from today's chain.
Anyone wanting to check the arithmetic needs neither an account nor a subscription. Two block numbers and their timestamps are enough, and both can be retrieved from any public explorer.
Trading venues keep their own books and credit a deposit once a set number of confirmations is reached. After that they post internally without consulting the chain again for every movement. If the chain is subsequently reset, a credit can be left standing without the transaction it rests on. Conversely, a withdrawal that reached you can be missing from the chain.
Stick to three sober points in that case. First: send nothing again before the position is clarified. Duplicate payments are the most common knock-on damage after an incident like this. Second: secure the transaction hash, timestamp and amount before you write to customer support. Third: compare today's position in your exchange account against your own last record from before August 30. If you buy regularly through a trading venue, our comparison of the best crypto exchanges sets out how many confirmations each provider requires for a credit.
One note on context, so that nobody draws the wrong lesson: the incident is an event of the chain, not the failure of an individual provider. An exchange that corrects a deposit after a rollback does so because the underlying booking is missing.
Finality is a chain's promise that a confirmed transaction will not be reversed. That promise is the reason a blockchain is fit to serve as a settlement layer at all. A rollback suspends the promise for a defined window.
What is notable is that the project names this conflict openly itself. In the passage quoted above, Cronos explicitly sets the finality users expect against the funds at risk and calls the decision a hard one. The trade-off is therefore on the record, rather than disappearing behind a success notice.
Whether a chain whose operators can roll back its history by agreement still credibly honours the promise of finality is a matter of judgement. The numbers alone cannot settle it, and this article does not settle it. What can be recorded is the verifiable fact: the intervention was possible, it was carried out, and it worked for around $111 million. Anyone deriving an expectation for future incidents from that is making their own assessment, not stating a finding.
The obvious lesson would be that self-custody was of no help here. That is true, and it also shows what self-custody actually protects against. Whoever holds their own keys is protected against the insolvency of a custodian and against third-party access to their account. No key protects against a rule change on the chain the value sits on, because the key proves only entitlement, not the state of the chain.
Two things follow in practice. For one, it is worth not leaving larger holdings permanently on a single chain with a manageable circle of operators. For another, your own bookkeeping counts for more than many assume: transaction hashes, timestamps and wallet statements are the only proof that survives an intervention like this. If you keep your keys separate from your everyday device, our hardware wallet comparison sets out the differences between the devices.
And one more point that gets lost in the excitement: after a network halt the chain is unreliable for hours. Time-critical payments over a chain that has just been stopped are an avoidable risk in the first days afterwards.
(As of September 10, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
