Enter the Ethereum wallet that held XEN or HEX, the X1 wallet that held XNM, or the Solana wallet that held solXEN or XENCAT. We’ll check it against a sample list, show its share of a 200,000,000 XCORE pool — XEN 40% · HEX 15% · XNM 25% · solXEN 12% · XENCAT 8% — and let you try a mock claim. Rewards are curved: bigger holders get more, but each extra token counts for less — so whales get far less per token than small holders.
Paste an Ethereum address (starts with 0x) for XEN/HEX, an X1 wallet address (base58, from Phantom or X1 wallet) for XNM, or a Solana address (from Phantom or X1 wallet) for solXEN/XENCAT. We only look it up — we never ask for a password or seed phrase.
This walks through the claim, step by step. It is simulated in your browser — nothing is sent anywhere.
—
Enter the Solana address from your Phantom or X1 wallet. In the real claim, this is where your XCORE would arrive.
That’s a made-up sample address, just so you can try the flow. It isn’t a real wallet.
Mock only. Clicking this does not send XCORE, ask you to sign, or run a transaction.
For XEN/HEX you’d prove the Ethereum wallet is yours with a free signature (no fee, no transaction); for XNM you’d prove your X1 wallet in Phantom or X1 wallet. Then choose a Solana/X1 destination in Phantom or X1, and either we send your XCORE or you run one claim transaction yourself and pay a small fee.
The demo pool is 200,000,000 XCORE, split 40% to XEN holders, 15% to HEX, 25% to XNM (X1), 12% to solXEN and 8% to XENCAT (Solana). Inside each pool the reward is curved: early tokens count most and the curve flattens for very large wallets, so whales get less per token than small holders. Holding both XEN and HEX earns from both pools in one Ethereum claim; holding both solXEN and XENCAT earns from both in one Solana claim. The biggest single claim is capped at 4,000,000 XCORE. Liquidity pools, programs, contracts and burn addresses are excluded and their share goes to real holders.
No. XNM holders are separate claims keyed by their X1 wallet address — we can’t link an X1 wallet to an Ethereum wallet without both signatures, so they are never merged here. Solana (solXEN/XENCAT) claims are separate again: even when the same address string appears on X1 and Solana, those are two different chains and two separate claims. In the real flow you’d prove the X1 wallet is yours (in Phantom or X1 wallet) to claim the XNM part, separately from any XEN/HEX claim.
No. This is a friendly demo on a small sample list. No real XCORE is sent here.
The real list will come from the Oct 1 snapshot, which is still to be loaded. This demo instead uses samples taken Oct 18, 2026 — Ethereum block 26,221,154 for XEN/HEX and X1 slot ~86,970,660 for XNM — so not finding a wallet here proves nothing about the real list.
Snapshot 6 (default) is snapshot 5 with each claim's HEX share capped at 100,000 XCORE. Snapshot 5 is the curved 200M XEN+HEX+XNM+solXEN+XENCAT sample on this page with liquidity pools, programs, contracts and burn addresses excluded and their share redistributed. Snapshot 4 is the same sample without exclusions. Snapshot 3 is the previous XEN+HEX+XNM curved sample. Snapshot 2 is the previous XEN+HEX curved sample, snapshot 1 is the old 1:1 XEN sample — both kept untouched and queryable. Snapshot 900 is a throwaway TEST snapshot used only in scripted API tests. The mock claim on this page is simulated in the browser and never calls the claim or voucher endpoints for snapshot-3/4 addresses, because those real holders can’t sign here.
GET /api/claims/health
GET /api/claims/snapshot?snapshotId=1|2|3|4|5|6|900
GET /api/claims/allocations/{eth-x1-or-solana-address}?snapshotId=1|2|3|4|5|6|900&chain=x1|solana
POST /api/claims/auth/nonce → POST /api/claims/auth/verify (SIWE)
POST /api/claims/destination
POST /api/claims (Idempotency-Key header)
GET /api/claims/me
POST /api/claims/me/voucher
POST /api/claims/me/retry
Demo note: the lookup reads a real sample list from the API. The claim itself is simulated in your browser — no wallet signature, no transaction, no XCORE sent.