LumiWave Protocol (LWP) Price

LumiWave Protocol is a Layer 1 blockchain node implementation built with the Cosmos SDK, and its node binary is named lumiwave-protocold. Its public code includes application wiring, custom modules, protocol definitions, and testnet genesis files; the README describes the repository as node software for extensible custom modules and testnet operation. Therefore, LWP should be understood as the protocol’s native unit of account, rather than an in-game item. The public code also includes Cosmos components for staking, minting, distribution, governance, IBC, and CosmWasm; these components show that the protocol implements and configures the relevant modules, but they do not by themselves prove that a feature has been deployed on a production mainnet or actually adopted.

LWP is the display unit and ulwp is the base unit; they represent the same native asset, with 1 LWP = 1,000,000 ulwp. In other words, on-chain balances, staking amounts, and some parameters may be recorded as integer ulwp, while wallets or interfaces can display them as LWP with 6 decimal places. For example, 500000000000 ulwp equals 500,000 LWP. Before transferring funds or setting fees, confirm whether an interface uses LWP or ulwp: treating the two units as the same numeric value creates a 1,000,000-fold quantity misunderstanding. The public testnet genesis file and configuration both identify ulwp as the base/bond/mint denom and LWP as the display denom.

What can be confirmed from public materials is that the repository README lists network parameters and public endpoints in its “Testnet” section, and the testnet genesis file has a genesis_time of 2026-01-29. In a March 2026 announcement, the project said it planned to launch an independent mainnet on April 1, 2026; that announcement is a launch plan and cannot, by itself, prove that the mainnet continued operating afterward or that its proposed services remain available. This distinction affects how parameters and asset status should be understood. The testnet genesis file lists a supply of 770175466000000 ulwp, or 770,175,466 LWP; it describes the supply in that testnet genesis snapshot, not the current circulating supply or a maximum total supply, and it cannot be used to infer mainnet balances or market-tradable supply.

The public testnet configuration uses the Cosmos SDK proof-of-stake structure: validators stake ulwp as the bond denom to participate in block production, and holders can also delegate staking weight to validators. The configuration sets goal_bonded to 0.67, meaning the minting module targets a 67% staking rate; this is not a “guaranteed 67% return,” but a network target parameter that influences the direction of inflation adjustment. The same configuration sets mint_denom to ulwp, with both initial inflation and inflation_max at 0.3441, and blocks_per_year at 6,307,200. Under the meaning of that configuration, new tokens are denominated in ulwp, the initial and maximum annualized inflation parameters are both 34.41%, and settlement is based on the configured annual block count; the actual amount newly issued also depends on whether the chain runs with these parameters, whether blocks are produced, and whether parameters are later changed. It cannot be equated directly with an individual delegator’s return rate. Reward allocation is also affected by distribution rules: the configuration’s community_tax is 0.917, meaning 91.7% of rewards subject to distribution under that configuration enter the community pool, while only the remainder follows the protocol’s distribution path for validators and delegators. Validators may also charge their configured commission from the delegation rewards they receive. The 10% validator commission rate shown in the genesis transactions is a parameter for that testnet genesis validator, not a fixed rate for every validator.

In the public node configuration, the minimum transaction-fee price is 0.025 ulwp/Gas. The fee a user ultimately submits is generally “Gas amount × chosen Gas price”: the Gas amount reflects the computational resources required to execute the transaction, while the Gas price determines how many ulwp are paid per unit of Gas. Therefore, 0.025 ulwp is the minimum accepted price in that node configuration, not a guarantee that every transaction costs only 0.025 ulwp or a permanently fixed network-wide rate. The configuration also sets validator downtime constraints: within a rolling observation window of 100 blocks, at least 50% of blocks must be signed; otherwise, the downtime slashing fraction is 0.01% and the validator is jailed for at least 600 seconds. This mechanism links continuous block-production participation to staked-asset risk: validators that fail to remain available are penalized, and delegators should also consider a validator’s operational reliability when choosing one.

The migration arrangement disclosed in the project’s March 2026 announcement was that existing LWA would be exchanged 1:1 for LWP on the independent network: under the announced arrangement, 1 LWA corresponded to 1 LWP. The announcement scheduled the independent mainnet launch for April 1, 2026 and said the arrangement resulted from two prior DAO governance votes; these are the plan and background described in the announcement and should not be used to infer that migration or mainnet services remained open on any later date. The eligible asset scope is LWA, not every LumiWave ecosystem asset. The announcement explicitly states that SSR does not participate in this migration; in-game assets, NFTs, and other ecosystem items also do not change because of the LWA→LWP exchange. In other words, the migration changes the relationship between eligible LWA tokens and new LWP, rather than automatically converting game items or NFTs into LWP.

Under the migration process in the announcement, holders of LWA in private wallets needed to complete a manual action through the official migration page and retain a small amount of Sui in the original Sui wallet to pay Gas for that on-chain transaction; the announcement listed Keplr, Cosmostation, and Leap Wallet as the receiving Cosmos wallets. It also required a desktop browser with the necessary wallet extensions installed and did not support mobile environments. After a migration request was submitted, the announcement said the team processed requests weekly and that most requests would be completed shortly after submission. Thus, manual submission did not mean LWP would immediately appear in the receiving wallet: the request had to enter the processing cycle before the corresponding migration was completed. LWA held in exchange custody was not necessarily migrated automatically. The announcement stated at that time that the team was discussing automatic migration with centralized exchanges and would provide an update once finalized; whether an exchange handled it therefore depended on subsequent confirmation by that exchange and the project. The announcement set a deadline of one year from the migration start date; the deadline, entry point, supported wallets, processing schedule, and exchange handling were all specific arrangements, so before taking any action, the relevant official channel and custodian platform notices at that time should be followed.