1. Fee flow

A token is associated with an X handle at launch or afterwards. When that token generates creator fees on-chain, an indexer adapter records a fee event: source mint, transaction signature, gross amount, protocol fee and recipient net amount.

Each event is keyed by its transaction signature. Re-delivery of the same signature is ignored, so replays and indexer retries cannot double-credit or double-pay a recipient.

2. Routing

A recipient's routing configuration is a set of destination splits that must total exactly 100%. Destinations include holding in SOL, converting to USDC, withdrawing to a Solana wallet, an optional X Money payout adapter, token buyback, burn, a charity, or another recipient handle for creator/artist/community/charity splits.

Routing is evaluated per fee event. Changing routing never rewrites already-processed events.

3. Payout statuses

• Pending — attributed and queued for a rail.
• Processing — handed to a payout adapter.
• Paid — the adapter confirmed delivery.
• Claimable — the rail failed or isn't configured; the funds stay attributed to the recipient.
• Failed — a terminal adapter error; the balance becomes claimable, never swept.

4. Claims and fallback

If an off-chain payout cannot be delivered — no X Money account, a rejected transfer, a disabled adapter — the amount remains attributable to the intended recipient. It is never redirected to the protocol treasury.

To claim, the recipient signs in, verifies ownership of the handle, connects a Solana wallet and requests settlement of the claimable balance to that wallet.

5. Security assumptions

• CRYPTO never asks for, stores, logs or displays private keys or seed phrases.
• Withdrawals are user-signed, or executed by explicitly configured server infrastructure — never by pasted keys.
• Row-level security scopes recipient data to its owner; admin actions require an assigned role and are written to an audit log.
• Event ingestion and payout execution are idempotent and replay-protected.

6. Economics

The protocol fee is a configurable setting, not a hard-coded constant. The demo configuration is 90% recipient / 10% protocol and is visible in the admin settings area.

7. Status of this deployment

All records currently visible are labelled demo data. No real money moves until payout and indexer credentials are configured. See integrations for the exact status of each adapter.