In a March 2016 interview, Max Kordek described founding Lisk with Oliver Beddows as a platform for decentralized applications and customizable blockchains. JavaScript developers were the intended audience, and an interconnected collection of blockchains was the ambition. Kordek connected that vision with open standards and research into connected devices, rather than limiting the project to one payment application. This is a first-person founding account, not evidence that every proposed device integration became a product. It also shows how much the architecture later changed.

The original pitch concerned developers running their own application chains; the later OP Stack version offered a shared Ethereum execution environment instead.

Lisk's legacy migration guide records a snapshot at block 24,823,618 and a two-year claim window beginning May 21, 2024. The process connected evidence of a legacy account to a claim on Lisk L2, with separate handling for multisignature accounts. It also required ETH on the destination network to pay the claim transaction's gas. This is materially different from sending an old-chain transaction to an Ethereum address and hoping the same balance appears. At this review, the stated two-year window has elapsed.

The continued availability of the old walkthrough is not proof that its claim deadline was extended. It belongs to the project's migration history, rather than serving as an unqualified current recovery instruction.

The L2 introduction describes Lisk as an OP Stack network working with Gelato as its rollup service provider and participating in the Superchain initiative. Solidity and Vyper applications could use familiar Ethereum development tools rather than the earlier custom-chain SDK model. The practical appeal for a builder was compatibility and a larger shared infrastructure ecosystem. That did not make every network in the initiative operationally identical.

It also did not make a deployment permanent: the same documentation still advertises ongoing growth and governance while newer official pages announce closure. Reading the architecture alongside the lifecycle notice gives a more accurate account than treating the surviving introduction as the latest business commitment.

The network configuration gives Lisk Mainnet chain ID 1135 and ETH as its native currency. Lisk Sepolia is a different network, with chain ID 4202 and test assets. Those identifiers matter when a wallet, explorer or market-data table uses the word Lisk for both a network and a token. LSK is the project's token, but a normal rollup transaction spends ETH for gas. Owning LSK alone therefore does not fund every transaction needed to move it.

The distinction also prevents a misleading economic inference: more execution on this network would not automatically mean every user bought and spent LSK as transaction fuel.

The fee guide separates L2 execution from the cost of publishing transaction data to Ethereum. The execution component depends on gas consumed and the applicable gas price. The data component depends on the transaction's estimated compressed size, Ethereum pricing and configured scalars. This is a more useful model than a fixed promise that every transaction costs a fraction of a cent. It explains why a wallet's estimate and the amount ultimately charged can depend on external network conditions.

The guide contains older implementation-specific formulas and comparison tables, so this account does not turn them into permanent price ceilings. The underlying distinction remains: running code and making its data available are separately funded activities.

The official contract directory distinguishes the Ethereum LSK contract from the portal, bridge, message-passing contracts and system configuration. It identifies the L1 token as 0x6033F7f88332B8db6ad452B7C6D5bB643990aE3f. Other entries describe proxy administration, sequencer configuration and withdrawal proof handling. This division is important during a wind-down: a token can remain transferable on Ethereum even when a particular execution network stops receiving support. It also means that checking only the token contract does not explain the safety of assets held in a bridge.

The directory is a map of components and responsibilities, not an assurance that every listed implementation is immutable or that a testnet contract can substitute for its mainnet counterpart.

L2BEAT's September review says Lisk's deployed fault-proof system is not functional because the committed program's registry snapshot omits its chain ID. It identifies reliance on permissioned proposers and challengers, immediate upgrades and withdrawal dependence on authorized state proposals. It also records Ethereum publication of transaction data. These observations should be kept together: data on Ethereum is useful, but it does not itself remove every operator or upgrade assumption. The assessment warns that significant changes are underway and some details may lag.

This article therefore attributes the finding to that dated assessment rather than presenting it as a permanent property of every OP Stack deployment or as evidence of a confirmed theft.

The DAO constitution describes staking-derived voting power, delegation and onchain proposal contracts. It distinguishes funding proposals from general proposals whose implementation could depend on feasibility, cost and the Foundation. Its scope also excluded proposals incompatible with Superchain commitments. These were bounded governance powers, rather than ownership of every corporate decision. That distinction helps explain why a treasury vote and a company's business direction were related but not identical.

The public proposal overview records a fourteen-day voting-period change, seasonal funding, market-making allocations and the later investment fund. It also records that the July 2025 vote on burning one hundred million LSK did not reach quorum. That outcome cannot be compressed into either a completed burn or an affirmative decision that every voter wanted the treasury retained. Quorum rules determine whether a proposal becomes valid, even when participating voters express a strong preference.

The overview is a useful historical index, but approval alone does not reconcile subsequent spending. To evaluate a funded program, readers need its implementation and accounting records as well as the vote that authorized it.

The DAO Fund team's August 25, 2026 closing statement says the vehicle began with four million LSK in October 2025. It describes investments in LovCash, Cr3dentials and Jamit through instruments such as SAFEs and SAFTs. Its legal handover had already completed in May 2026, before the planned two-year term ended. The investments moved to Onchain Ventures AG and residual capital returned to Lisk Ltd after termination costs. This is a concrete lifecycle event, not merely a proposal for future restructuring.

It also limits an older investment narrative: plans for a DAO-managed portfolio cannot be assumed to continue unchanged after the vehicle and responsibility for its assets have moved elsewhere.

Max Kordek's August 2026 announcement presents Lisk's new focus as finance operations for businesses managing multiple entities, jurisdictions and payment rails. The early-access product combines accounts, payments and approval policies, while cards and some treasury features remain future work. In the same announcement, the team schedules the chain shutdown for October 31 and says the DAO cessation proposal passed. These statements describe a deliberate change of product and institutional structure, not a consensus upgrade that preserves the old application environment.

As of September 30, the shutdown is still a scheduled future event. The article does not report it as already completed simply because the wind-down has been announced.

The current closure FAQ tells users to move assets off Lisk Chain before October 31, 2026. It describes an initial withdrawal, a proof transaction on Ethereum and a final claim after the challenge period. The countdown begins with proving, rather than simply clicking withdraw. Its estimate is roughly eight days for bridging, with additional time for previously staked LSK. The page also distinguishes unwrapping WETH from transferring native ETH. These details explain why a fast L2 block time does not imply an instant canonical exit.

The warning covers assets beyond LSK, including stablecoins and application positions; users should follow current official asset-specific instructions rather than assume that an exchange listing automatically retrieves their onchain holdings.

The Celo migration guide asks each team to review contracts, users, liquidity and infrastructure dependencies before defining an approach. Participation is optional and assessed individually. It explicitly says that funding and support should not be assumed without confirmation. This is an offer to work through redeployment, not an automatic state transfer between two networks that happen to share Ethereum tooling. An application may need new contracts, indexed history, oracle configuration and a user-facing asset plan.

The guide's requirement to establish a clear path before public communication is sensible for that reason. A token-holder article should not announce that every Lisk application has successfully moved merely because the invitation is available.

The token FAQ says the Ethereum LSK contract remains unchanged and that moving LSK out of the rollup is a bridge transfer, not a redenomination. It describes the future role as loyalty and rewards for the new product, with earning and spending features arriving in phases. Holding LSK is not required to access the finance platform. The same FAQ says new staking is closed and governance concludes with the DAO. These are material changes to the reasons someone might hold the token.

A planned rewards program does not recreate a former treasury vote, and optional fee use does not establish guaranteed demand, profit sharing or a claim on the company's revenue.

The DAO cessation FAQ says the one-hundred-million-token burn is complete, while the token FAQ still calls it in progress. A read of the canonical Ethereum contract at block 26,092,010 returned a total supply of three hundred million LSK with eighteen decimals; Blockscout's token API independently displayed the same quantity. That observation supports the current total-supply figure without pretending to reconstruct the precise burn transaction. It is also not a circulating-supply measurement. Treasury holdings, bridge custody and freely traded units are different categories.

The contradiction illustrates why a material supply statement deserves an execution-level check instead of choosing whichever official page best fits an investor narrative.

Lisk's USDL explanation says its payment-account dollar balances are backed by a Bridge-issued stablecoin and that conversion happens within the product. It separately places assets such as LSK, BTC and ETH in portfolios rather than treating them as that dollar balance. The product also acknowledges partner fees and settlement timing tied to banking and crypto rails. This distinction keeps three identities separate: the discontinued chain service, the continuing LSK token and a business payment account.

A user should not infer that holding LSK provides a dollar redemption right, or that seeing dollars in the new interface means those funds are ordinary native balances on Lisk Chain.