Swap is offline

The LXON swap interface is not available right now, and it is not a connectivity problem. Chain 724 was restarted on 2026-11-03 from its original genesis file on a fresh, empty data volume, after the previous node and its database were lost. The chain identity is the same — block 0 is still the same hash and it is still sealing blocks every five seconds — but everything created in blocks 1 to 242,493 is gone, including the token, the wrapped token, both pools and the router this page traded against.

What that means for a swap: the eight chain-724 contracts still hardcoded in the swap interface currently have no code deployed at them. There is no liquidity to route through and no token to move. Publishing the trading form against those addresses would invite you to sign approvals and send transactions to contracts that do not exist, so the page is withdrawn instead.

`eth_getCode` read directly from the live node through its read-only RPC on 2026-11-03. Labels are the ones the swap page itself gives these constants. The two control rows are there because an empty result only means something next to a read that is not empty.
address	used by the swap page as	`eth_getCode` now
`0x99801a78639975d448eeb2f8a807738dc8df67dc`	`LXON_ADDRESS`	no code
`0xcb742c31f0815648e13ff24d8131b89075ff32e2`	`WETH_ADDRESS`	no code
`0xC0CF6B0E6C5a0705F319BA5c629a6Bc7E82FEf00`	`WLXON_ADDRESS` / LXONWrapper on 724	no code
`0xd969211d7efb154e86d41a80ff0fd3cc0eb70468`	`ROUTER1_ADDRESS`	no code
`0x272a3ed4b91112005ade5b4161af1adc856ab3f4`	`PAIR_ADDRESS`	no code
`0xaa0e4bb075f108b34dc0e279a7747980c76b8d75`	`ROUTER2_ADDRESS`	no code
`0x8e90675e054826f61745c0016b895cdc4f220ebc`	`PAIR2_ADDRESS` — wLXON/LXON peg pair	no code
`0x9B15fEe95995a15Da2d64D8E2958f9792D5D6a25`	`BRIDGE_724`	no code
`0x1111111111111111111111111111111111111111` (control)	an address that never had code	no code — so "no code" above is a real answer, not a failed read
`0xFaE699d2848957c7c3be67d8c90f0e456419cada` (control)	the validator	`eth_getBalance` returns `0x1337` followed by 60 zeros — the genesis allocation, read correctly

The swap page also names 0xbDC32d8Ca8Ce805E0654e7A7d0DD1eE0A21D4a95 and 0x7A3c0C34f157EfDD3E4913c5224C15E645469093. Those are Polygon (chain 137) contracts and are expected to have no code on 724; they are not part of what was lost, and they are deliberately not counted as evidence above.

Nothing here is estimated. The node answers at eth_chainId 0x2d4 and is producing blocks; it is the chain-724 contracts that are absent.

What would bring the swap back: redeploying the token, WETH, the pair and the router on chain 724 and funding a pool. Until then there is no honest price to quote and no route to show, so the figures on this site's other pages say not read rather than guessing — that behaviour is deliberate and is how the pages were built.

Chain 724 · node at 13.61.55.231 (eu-north-1) · measurements taken 2026-11-03