Lisk completed its migration from Mainnet v2 to Mainnet v3 at approximately 14:00 Central European Summer Time—12:00 UTC—on August 21, 2021, activating the network’s largest protocol overhaul to that point.

The migration changed how Lisk represented accounts, priced transactions, selected block-producing delegates and determined when blocks were final. It also moved Lisk Core onto a more modular software architecture intended to support future blockchain applications.

The central fact is supported by Lisk’s contemporaneous account of the completed migration and by the project’s Lisk Core 3.0.0 release record. The release had been published on July 27, 2021, with an explicit warning that it would induce the hard fork and migration of the version 2 mainnet. A contemporaneous German report also recorded the successful August 21 transition.

Accounts and fees changed

Mainnet v3 replaced Lisk’s former address and account-identification system. Existing accounts were migrated automatically, but their displayed Lisk addresses changed. Lisk said users’ private keys, public keys and 12-word mnemonic passphrases remained unchanged.

The new addresses incorporated a checksum intended to detect typing errors. The project said the format could reliably detect as many as four mistyped characters. That was an operational security improvement, although the claim describes error detection in the address format rather than protection against compromised keys or deceptive interfaces.

Lisk also replaced a static transaction fee with a dynamic system. The project reported that the minimum fee for a basic transaction fell from 0.1 LSK to 0.00136 LSK. Calculated from those two stated figures, that is a 98.64% reduction. Actual fees could differ because the system allowed users to choose higher fees, including when replacing an unconfirmed transaction. Lisk said the minimum portion would be burned.

Consensus received a broader redesign

The migration overhauled Lisk’s delegated-proof-of-stake system. According to the project, the new design introduced a different voting mechanism, two randomly selected delegates in each forging round and penalties for malicious delegates.

Existing delegate votes were not carried into Mainnet v3, so token holders who wished to participate had to cast new votes. That made the upgrade more than a software change for node operators: it reset an important part of the network’s governance and validator-selection state.

Mainnet v3 also introduced Lisk BFT, the project’s Byzantine-fault-tolerance mechanism. Lisk estimated that a block would become final after an average of 155 blocks, or roughly 26 minutes. Those were project specifications and estimates available in August 2021, not an independently measured service-level guarantee.

Why the migration mattered

The upgrade consolidated several years of protocol work into one coordinated mainnet transition. Lisk Core 3.0.0’s release notes described four roadmap areas—network security, economics, consensus and longevity—and connected the release to prior beta versions, security auditing, testnet migration and community testing.

For users, the immediate consequences were new addresses, lower minimum fees and the need to recast delegate votes. For developers and infrastructure operators, the migration changed data storage and core protocol behavior while introducing the modular architecture of the Lisk SDK.

Lisk also presented Mainnet v3 as preparation for a future interoperability release. On August 21, however, that interoperability system was still prospective. The completed event was the v3 migration itself; claims about later cross-chain applications remained roadmap statements rather than capabilities demonstrated by this upgrade.

The surviving record verifies that the coordinated transition occurred and identifies its principal protocol changes. It does not independently establish the project’s promotional performance claims under sustained production load, nor does it by itself measure adoption or economic value created by the migration.

Primary sourceLisk — Meet the New Lisk Mainnet, contemporaneous project-authored record

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.