SliceClaiming with X
You prove you own the X account, and we send its balance in SOL to a Solana wallet you name. No wallet is needed to see what is waiting, and nothing waiting ever expires.
Signing in
Claim sends you to X to approve the sign-in, using OAuth 2.0 with PKCE. We ask only for the read access X’s sign-in requires. We cannot post, follow, like, or read your messages. X gives us a short-lived access token, which we use once to read your X user id, handle, name and picture, and then discard. It is never stored.
What we keep is a signed session cookie holding your X user id and handle, valid for seven days. It is HttpOnly, so page scripts cannot read it. Signing out deletes it.
Your first sign-in also pins to your X user id any handle of yours that was named on a token while X could not be asked who owned it, unless a later lookup already pinned it to you. From then on the money on those handles is yours whatever you rename to. See Whose money it is.
What you see
| Figure | Meaning |
|---|---|
| Credited | Every credit from every sweep of every token that names a handle pinned to you |
| Paid | Payouts to your wallets that have not failed, including any still in the queue |
| Burned | Credits you routed to buy and burn |
| Balance | Credited minus paid minus burned. What you can claim now |
The same figures are public at /x/<handle> for anyone, signed in or not. That page is what to send to someone who has been named on a token and does not know it yet.
Claiming
- Paste a Solana wallet address. It must be a wallet: a public key on the ed25519 curve that is either unused or a plain system account. Program-derived addresses, token accounts, program accounts, the treasury, and the mints and fee addresses of tokens launched here are refused. SOL sent to most of them could never be moved again, and SOL sent to a fee address would be swept back in and credited a second time.
- The claim takes your whole balance, which has to be at least 0.01 SOL. The API also accepts a smaller amount; see POST /api/claim.
- The claim is queued, and that amount leaves your balance at once so it cannot be claimed twice. You can have one payout open at a time.
- The payout job signs a transfer from the treasury, stores its signature, and sends it. The network fee is paid by the treasury, not taken from your amount. A short memo in the transaction identifies the payout.
- When the chain confirms it, the payout is marked confirmed. Its signature is public, so you can open it on Solscan.
When a payout waits
- Payouts are paused. The operator can pause them from the console. New claims are refused while the pause lasts, with a message that says so, and payouts already queued wait and resume as they were. Balances are not touched.
- The treasury is low. A payout is sent only if the treasury keeps at least 0.05 SOL back afterwards for network fees and rent. Otherwise the job stops, raises an alert for the operator, and tries again on its next run. It stops rather than skipping ahead, so payouts are always sent in the order they were queued.
Why not X Money
Paying people through X itself sounds natural and does not work. X Money offers no interface that lets another product pay an X account, so every route through it depends on something X can close at any time, and fee-sharing products that paid out that way are exactly the ones that have had to pause payouts. We pay in SOL, on Solana, to a wallet you choose. Nothing about a payout depends on X beyond the sign-in that proves the account is yours.
Not wanting to claim by hand
Set a routing once instead. Autopay sends your balance to a saved wallet whenever it reaches 0.05 SOL. Burn turns each new credit into a buy and burn of the token it came from, and Decline does the same while saying so publicly. See Routing.
Nothing expires
There is no deadline to claim. Credits wait on your handle for as long as it takes, and they are never redistributed to other recipients or moved to the platform. The treasury is checked against every unclaimed balance on the proof page.