Claim XCORE
XEN holders · testXEN pool · separate from HEX. The XEN and HEX claims draw from two independent pools. Held both? You can claim both: this page for XEN, /claim-hex for HEX. Claiming one never reduces the other.
not connected- Snapshot
- —
- Balance source
- —
- Allocation rule
- —
- Minimum XEN
- —
- Network fee
- None signature only, no gas
You sign a free message (personal_sign) that names your Ethereum address, the destination and a one-time code. No transaction, no approval, no gas.
Claim recorded
Simulation: recorded on the demo server. No XCORE was sent.
- XCORE allocated
- —
- XEN counted
- —
- From (Ethereum)
—- To (Solana / X1)
—- Recorded
- —
- Claim #
- —
One claim per Ethereum address. In production the destination wallet would collect this XCORE from an on-chain claim program on Solana / X1.
Admin · test allowlist
Give an Ethereum address a test XEN balance so it can try the claim without holding XEN. A test balance replaces the on-chain balance for that address and is labelled “test” everywhere.
- Snapshot block
- —
- Block time
- —
- XEN total supply at snapshot
- —
- Claims recorded
- —
Balances are read with balanceOf at the snapshot block from a public Ethereum archive RPC.
XEN contract 0x0645…6Fb8 ↗. XEN also lives on other EVM chains; this test checks Ethereum mainnet only.
Allocation
Example parameters · not final—
- XCORE pool
- —
- Minimum XEN
- —
- Cap per address
- —
- Claims per address
- 1
None of these numbers are decided. The pool size, formula, minimum, cap, snapshot block, chains and claim window are open decisions.
Recent claims
Simulated| Time | Ethereum | Solana / X1 | XCORE |
|---|
No claims yet.
How it works
- Snapshot. XEN balances are fixed at one Ethereum block, so buying or moving XEN afterwards changes nothing.
- Prove the wallet. Connect the Ethereum wallet that held XEN and sign a free message. The message names that address, your Solana / X1 destination, the snapshot block, a one-time code and an expiry. The server checks the signature and that the code was never used.
- Claim. The allocation is computed from your snapshot balance and recorded once per Ethereum address.
On this test page
Balances come live from a public Ethereum RPC at the snapshot block. Claims are stored in the demo database. No XCORE exists yet and nothing is sent. Admins can give a test wallet a test XEN balance.
In production
- Index every XEN holder at the snapshot block from
Transferlogs (or an indexer), compute every allocation and publish the full list plus its Merkle root. - A claim program on Solana / X1 holds the XCORE pool and stores the root. The Ethereum signature binds the XEN address to one destination; the destination then submits the Merkle proof and receives XCORE.
- No Ethereum transaction and no ETH gas for holders. The destination pays a tiny Solana / X1 fee to receive the tokens.
- Contract wallets (multisigs) need EIP-1271 signature checks; this test supports normal wallets only.