$LSK This story can’t be wrapped up with just two words: “burning.”

As of 19:25:33 Beijing time on September 24, 2026, the Binance LSK/USDT spot price is 0.388900 USDT. Over the past 24 hours, it is up 18.89% rolling. Trading volume for this pair is about 28.8496 million USDT, ranking fourth on this gainers list.

It’s been a very lively scene, but the changes happening in the project are even more worth taking a closer look: Lisk is shifting its focus toward enterprise treasury management. The old chain plan will be shut down on October 31, and LSK will be repositioned as a loyalty and reward token.

My question is: while reduced supply can change some conditions, can the new product actually create sustained demand for LSK?

First, verify the number that’s easiest for headlines to carry away.

When I checked the materials this time, Lisk’s two pages weren’t entirely consistent. The main site’s introduction and the DAO Cessation FAQ both state that 100 million LSK have been burned, bringing the total down to 300 million. But the LSK Token FAQ still says: “Burning in progress; after completion, it will drop from 400 million to 300 million.”

I didn’t resolve the conflict by picking a more updated copy; instead, I confirmed the Ethereum LSK addresses via LiskHQ’s contract repository, then used two public nodes to read the total supply at the same block. Around 19:30 on September 24 (Beijing time)—corresponding to Ethereum block 26047029—both PublicNode and dRPC return 300 million tokens.

Therefore, what can be clearly stated is: the on-chain total supply reading supports the 300 million status, while the progress wording in the old FAQ hasn’t been updated. This article does not provide a full replay of the burn transactions, nor does it invent an exact execution timestamp.

From 400 million to 300 million, the reduction is one quarter of the total supply. But that still doesn’t mean there are immediately one quarter fewer sell orders in the trading market. Whether the removed portion was previously locked and when it was originally set to be released affects its significance for short-term liquidity. Total supply, circulating supply, and the order book at the moment are three different metrics.

The users Lisk is serving now have already changed.

The new product targets enterprise finance teams. It puts accounts, payments, and approvals into a single workspace, while handling both fiat and stablecoin channels. What it wants to solve is how a company’s funds—scattered across multiple accounts, wallets, and business entities—can be viewed, paid, and reconciled in a unified way.

This need isn’t mysterious. Finance people often don’t care about parameters deep in the underlying blockchain; they care about who approved the payment, where the money comes from, whether the supplier actually received it, and whether the full records can be reconstructed at month-end. If a product can continuously reduce these frictions, it may have a reason to charge.

But there’s still a gap between “having a reason” and “already having scale.” The website currently labels it as Early Access. Accounts and payments are the main focus; for Portfolios, it still says Coming soon. I can’t describe an asset allocation module that’s still being previewed as a revenue source that enterprise customers are already using at large scale.

There’s also a small but concrete detail: on the website’s account display, the dollar symbol in the interface is explained in the footnote as USDL, not actual cash dollars. When researching products like this, you need to look at the valuation unit shown on the interface, the assets users hold, and the real services provided by partners separately. You can’t just add a bank-deposit attribute because the screen looks like a bank account.

The website’s feature description can confirm the product direction. As for the number of paying enterprises, the scale of ongoing payments, how much each customer contributes, and retention—this article does not obtain data that can be independently recalculated. Those are the key to judging the quality of the transition; today’s LSK trading volume can’t substitute for those metrics.

Closing the chain and token migration—don’t mix them into one thing.

Lisk has published the chain closure date as October 31, 2026; we are not there yet. Officially, Lisk provides an exploration path for ecosystem projects to migrate to Celo, while emphasizing that each project decides for itself. This is about the choices of application and development teams—not about LSK having to move to Celo in a unified way.

For the token, the current FAQ is very direct: the contracts on Ethereum remain unchanged; this round does not involve switching coins or changing denominations. LSK that is already on Ethereum or on exchanges is in a different situation from assets still on Lisk Chain or staked there. The latter involves exit arrangements before chain closure; this article doesn’t lump them all together as “automatically migrated well.”

This also needs to be distinguished from the historical migration in 2024. A support announcement from an overseas exchange confirmed that at the time, it was converted to Ethereum ERC20, with balances handled 1:1. The historical coin switch already happened; that doesn’t mean chain closure in 2026 creates a brand-new coin.

So, continuing to explain the new business using old-chain新增 address counts and the total number of on-chain applications will become increasingly meaningless. As the research subject shifts from network ecology to enterprise software, the measurement criteria should naturally change with the type of customer. In which part of the workflow is LSK placed?

The positioning that can currently be confirmed is the loyalty and rewards layer. Officially, the plan is to first obtain LSK rewards in recommendation scenarios, and then gradually add applications where users can pay app fees using LSK; the specific dates depend on product releases. The more important sentence is: using the product does not require holding LSK.

This is an actual trade-off. Enterprise customers can use the platform for their business needs first, reducing the entry threshold; but from the token perspective, it also means customer growth won’t automatically translate into holding demand on a one-to-one basis. A finance team could well like the product, yet have no immediate need to hold LSK.

When rewards are distributed, the first thing that increases is the number of tokens in users’ hands. After that, whether users use, keep, or transfer them depends on real entitlements and fee arrangements. If using LSK only provides limited convenience, while the rewards keep flowing into the market, business expansion may even first increase token circulation.

Conversely, only if paid scenarios have sufficient appeal does the demand relationship have a chance to become more solid.

This isn’t about judging whether it will definitely succeed or fail; it’s about accounting for the next steps: where the rewards come from, how much of the fees can be paid with LSK, and how the fee recipient handles the tokens after receiving them. Without these rules, it’s hard to evaluate transmission efficiency based solely on the claim that “the bigger the ecosystem, the more valuable the coin is.”

Meanwhile, the end of the DAO also changes the governance relationship. The governance infrastructure will be phased out according to the plan, so the old rationale for holding tokens—mostly driven by voting rights—needs to be reexamined. You can’t accept the centralization of company business while keeping the old DAO governance purposes unchanged in the new pitch. After destruction, what do we truly need to observe?

The most clear-cut progress for Lisk, in my view, is that it proactively ended dispersed investment and made the users and purposes of the new business easier to understand. The on-chain supply reading of 300 million tokens is also more reliable than simply seeing the title of a proposal. Evidence exists for supply changes; business demand still needs to be proven.

The strongest counterargument is this: a company might do a great job building enterprise financial products, yet the real function of LSK still remains limited to marketing incentives. There is no natural equivalence between product success and token demand. If the business is organized around stablecoin flows, it doesn’t mean all business value passes through LSK.

What can change this judgment is the subsequent disclosure and execution details of rewards and fee rules, along with a stable base of paying customers and repeat usage. If the platform’s spending of LSK remains consistently higher than the portion users truly are willing to consume or retain, token burn can only resolve part of the historical supply issue. If usage demand continues to form, the new positioning will have a sturdier foundation.

So, the focus of this LSK research ultimately comes down to after the burn: we can already see the subtraction of total amount, but the relationship between the new business and the token is the part that most needs to be proven next.

This article organizes publicly available information and presents personal opinions; it does not constitute any investment advice. The project’s self-reported data and content that has not been independently verified are labeled in the text—please verify for yourself.

Market data convention: Binance LSK/USDT spot, rolling 24 hours; as of 19:25:33 Beijing time on September 24, 2026.

Sources: Lisk (Introducing the New Lisk), page marked August 2026; Lisk official website and support documentation (LSK Token) (Lisk Chain Closure) (DAO Cessation), accessed 2026-09-24;

LiskHQ official contract repository (Addresses of Deployed Smart Contracts on Mainnet), accessed 2026-09-24; an overseas exchange (Notice of support for Lisk migration), with migration history content and page updated on 2026-09-01.

Cross-check of supply: the Ethereum mainnet LSK contract, at block 26047029 (19:30:35 Beijing time, 2026-09-24). PublicNode and dRPC return the same total supply of 300,000,000 LSK; this on-chain snapshot and the market snapshot are listed separately.