Waves rolls back chain after abnormal-fee blocks credited WAVES

By Elena Vasquez

Waves reset its layer-1 blockchain to block height 5,481,020 after abnormal-fee blocks credited multiple addresses with WAVES that did not exist, according to the network’s incident notice. The replacement chain resumed at block 5,481,021 and has continued from that starting point, while transactions initiated during a 10-hour, 21-minute Nov. 8-9 window may be affected.

What caused the rollback?

Waves said a third party generated blocks with unusually high fees on Nov. 9. The notice said those blocks caused multiple addresses to be credited with nonexistent WAVES, but it did not provide the address count or aggregate amount.

The network therefore accepted an invalid balance state before operators replaced the affected history. Waves did not identify the third party or explain how it generated the blocks.

Takeaway: Unusually high-fee third-party blocks produced balances the network could not support.

Which transactions may be affected?

The warning draws a precise boundary around the disruption. Waves wrote: “Transactions initiated from 6:55 p.m. ET Nov. 8 through 5:16 a.m. ET Nov. 9 may be affected.” The period covers 10 hours and 21 minutes across midnight in ET.

The use of “initiated” matters because the notice does not list affected transaction hashes, confirmations, addresses or wallets. Users cannot determine from the warning alone which submitted transactions differ between the original and replacement histories.

Any service that indexed the pre-reset chain may need to compare its records with the replacement chain. The notice does not supply a transaction-by-transaction reconciliation list.

Takeaway: The warning defines a time window, not a complete inventory of affected transactions.

What did the reset change?

Waves said the network reset to height 5,481,020, removed the erroneous balances and resumed activity on a replacement chain starting at 5,481,021. The replacement chain has continued from that starting point since the reset. Block height is the chain’s sequence marker, so the two numbers identify the reset point and the first block after it.

Waves is a layer-1 network, meaning its blockchain maintains its own chain history. That structure allows the network to replace history, but also makes consistency dependent on every node operator applying the same reset.

The notice did not state how many historical blocks were discarded or explain how each transaction from the affected window was handled. It also provided no reconciliation showing which submissions survived unchanged.

Takeaway: The reset removed fabricated credits, but the notice does not reconcile every affected transaction.

What must node operators do?

Operationally, the instruction has two parts. Waves stated: “Node operators must install version 1.6.5 and manually roll back.”

Every node operator must:

• Install software version 1.6.5.
• Manually roll back using Waves’ release instructions, with the replacement chain starting at block 5,481,021.

Because the process is manual, an upgrade alone does not establish that a node reached the designated reset point. Waves published no completion deadline and did not describe the code changes in version 1.6.5.

Takeaway: Installing the software and aligning chain history are separate obligations, and the notice sets no deadline.

What remains undisclosed?

The account rests on Waves’ notice; the source cites no court, regulator or law-enforcement agency. The notice offers no total balance, no count of credited addresses and no aggregate fee figure, so the incident cannot be sized from the published account.

It also does not state whether user funds were lost, whether an exchange or custody platform adjusted balances, or whether compensation was available. Those omissions matter because services built around a single chain history need a reconciliation rule, not merely an upgrade notice.

Takeaway: Without address counts or balance totals, the scale and final financial consequences remain unresolved.

What changes for users and the network?

Users who saw balances appear during the affected interval may find those balances absent from the replacement chain, because Waves said the reset removed erroneous credits. Transactions initiated in the window may also have different status after the manual rollback.

Market participants should verify transaction and balance records against the replacement chain rather than treat pre-reset confirmations as durable. The market-structure change is chain-history replacement, not a disclosed change to WAVES issuance, fees or governance.

Takeaway: The repair changes what the network recognizes, making coordinated node action the central execution risk.

The next checkpoint is node convergence: if every operator installs version 1.6.5 and applies the same rollback point, the replacement chain can settle on one history. Waves published no completion deadline, so the remediation schedule remains undefined.