EPIK token claim

Solana · Launched

EPIK ran its token airdrop on Solana as two claim campaigns, with five ways to qualify. Visitors checked a wallet’s eligibility on EPIK’s site, then claimed from a claim console. My part was the campaign and claim implementation, from authentication to the on-chain distributor.

A claim’s proof is checked from its leaf up to the Merkle root.
My part
Campaign and claim implementation: authentication, deterministic claim tooling and an Anchor distributor.
Network
Solana
Stack
Next.js, Anchor, PostgreSQL
Status
Launched. Both claim campaigns have closed.
Verify
Claim Campaign 1 on Solscan (opens in a new tab)
Claim Campaign 2 on Solscan (opens in a new tab)
The claim status card on EPIK’s home page, marked Claims live: Claim your EPIK, Open claim console, routes 05, network SOL, start Sep 01.
The claim status card on EPIK’s home page while claims were open.

The home page while claims were open

A status card on the home page showed that claims were live, with the number of routes to qualify, the network and the start date, and one link into the claim console.

How the 2,132 wallets were counted

2,093 wallets claimed directly and 91 through the social list. 52 claimed both ways and are counted once, which gives 2,132 unique wallet addresses. Checked on 14 September 2026 at finalized Solana slots 446,937,885–886. A wallet address is not a person.

The EPIK eligibility checker in four steps: connect a Solana wallet, verify control, link X for social eligibility (optional), then check eligibility.
Checker steps 1 and 2: Connect a Solana wallet, which sends no transaction or token approval, and Verify control, by signing one readable, expiring message.
Checker steps 3 and 4: Link X for social eligibility, which is optional, and Check eligibility, which reads the current lists and published amounts only.
The eligibility checker, in four steps.

Verifying a wallet with a signed message

The checker connects through the Wallet Standard, so it works with the Solana wallets that support it. To prove a wallet is theirs, a visitor signs one readable message. It cannot move funds, it expires, and it only counts for this site and this attempt.

Optional X account linking

One route to qualify was a social list. Linking X is its own step and only checks that list: it confirms which account made the selected posts, and never asks for permission to post. A wallet that qualifies alone never needs it.

Checking eligibility without a transaction

The last step reads the current lists and the published amounts for the wallet, and prepares nothing to sign. Claiming was separate, in the claim console on mainnet, with a proof checked against the campaign’s Merkle root.