Official certification of the first liquidity injection into the LUXA / SHARD pool, the procedure that was followed, and the rules that govern every future injection.
On 10 October 2026, on the sovereign LUXA Network (Chain ID: luxa-1) blockchain, the inaugural liquidity injection for the decentralized LUXA / SHARD trading pair was finalized and recorded in the immutable ledger.
add_liquidity)The activation respected the separation of powers and the cryptographic security standards of the protocol. Each step below is anchored to the block where it was recorded.
The source luxa_amm_pair.wasm was compiled with Bulk Memory vectors disabled and validated locally with cosmwasm-check, to guarantee full compatibility with the Wasmer engine of the consensus node. It was stored as Code ID 1 (tx 84AD7807…F988).
The contract was instantiated in transaction A54B03D6…36AA, and administrative ownership was assigned to the Root Validator (luxa1qgx52…).
In line with the cryptographic separation of duties (the Security Matrix), the Root Validator did not inject funds from its own validation account. It funded the complementary 1,000,000,000 SHARD to the Liquidity Vault (luxa1ghmun…) in this transaction:
66663AA79AC01E4263E10EFBF6637DDABE0D036354A92EC8E9848642723C4991
The Liquidity Vault called add_liquidity and deposited both tokens in the same message (sent_funds_count == 2). This created the initial constant product (k = 1026) and opened the market.
A test swap of 1 LUXA (tx A7F03941…DD23) validated the exchange formula: 9,969.9006 SHARD were released after the 0.3% fee, and the contract state updated automatically.
The native LUXA token is designed as an asset with programmed mathematical scarcity. The Root Validator and the Liquidity Vault are bound by strict rules that prevent arbitrary dilution, price depreciation or market manipulation.
The AMM contract rejects, by code, any injection made of only LUXA or only SHARD (sent_funds_count == 2).
Every future liquidity addition must deposit both assets, calculated at the instantaneous market price of the pool in that block. Depositing tokens at a ratio different from the current value would unbalance the pool immediately, to the advantage of arbitrageurs.
A new intervention using treasury reserve funds (the 200,000,000 LUXA allocated to the Liquidity Vault) is allowed only when one of the following objective conditions occurs.
If the community buys large amounts of LUXA by giving up SHARD, the LUXA reserve in the pool falls.
Trigger: the LUXA reserve drops below 20% of the initial liquidity, meaning fewer than 20,000 LUXA left in the pool. The Liquidity Vault may then add a supporting top-up so slippage does not block normal user transactions.
With the Telegram Mini App, listings or cross-chain bridges, high trading volume may call for a deeper pool.
Trigger: the price impact of average transactions stays above 2% to 3%. An incremental tranche of liquidity is then authorized.
The entire treasury reserve must never be poured in at once.
Top-ups happen in controlled tranches (for example 100,000 to 500,000 LUXA per intervention), proportional to the real organic demand of the network.
No intervention to push the price down. If the price of LUXA rises naturally in the pool against SHARD, the protocol must not step in to force it back down. The free market determines the value of scarcity.
No arbitrary rescue of speculative positions. Intervention exists only to guarantee the technical solvency of the decentralized exchange, never to manipulate its accounting value.
The state of the pool and of the two wallets involved, right after the pilot swap.
These figures are a snapshot at block #3301. For current balances, use the Block Explorer.
This document attests that the facts above match the state recorded on-chain, and serves as a binding guideline for future liquidity management on the LUXA Network (luxa-1) mainnet.
Certified by Raqeem Primary Consensus & Architecture, .