Coins for X accounts

The X account is the recipient

A launcher may assign the fee to themselves or to somebody who has never visited XCoins. No account or wallet is required to begin earning. The readable handle is stored when the coin launches and cannot be replaced later.

At the first claim, signing in with X proves control of the account. The system then binds the handle to X’s stable numeric account ID so a future handle rename does not redirect the entitlement.

Lifecycle

The payout system advances through explicit, replay-safe states. A worker may resume a failed request, but it may not skip a required transition or run a completed leg twice.

CREATED → TRADING → GRADUATED → CLAIMABLE → BRIDGING → SETTLED

if current_state !== required_state:
    refuse_transition()

Bonding curve

New coins begin on a bonding curve. Creator fees accrue from the first trade, but those fees remain inside the curve system while trading is active. “Earned” is therefore not the same as “available.”

Graduation

When the bonding curve sells out, the market graduates. Liquidity is seeded into a permanent pool and locked. Only then does the creator-fee escrow become claimable by the payout keeper.

Creator fees

Every trade allocates 2% to the X account written into the launch. The assignment is immutable. Each graduated coin has its own vault, which isolates claims and makes partial payout progress observable.

Proving a handle

X sign-in is only required to collect. The claim service verifies the account, resolves every eligible coin assigned to it, and creates guarded payout requests. Wallet ownership is not the creator identity.

Coin vaults and the keeper

The keeper claims one graduated coin at a time into that coin’s vault. Separate state for each leg prevents a successful claim from being repeated when another coin fails later in the batch.

Payout settlement

The existing design claims onchain value, converts toward a dollar-denominated asset, and hands it to an off-ramp for final delivery. The settlement boundary is deliberately explicit because banking rails are asynchronous and independently fallible.

Arc deployment

Arc is an EVM-compatible Layer 1 designed for stablecoin finance, with USDC used as native gas and deterministic sub-second finality. That makes it the target network for this edition.

No Arc contract addresses or adapter implementation were included in the supplied source. Contract controls in this interface use representative launch records for visual and interaction testing; production trading, charting, wallet signing, identity proof, and payout calls require the existing backend and Arc contract adapters.

ARC_CHAIN_ID=awaiting_deployment_config
LAUNCH_FACTORY=awaiting_deployment_config
FEE_ESCROW=awaiting_deployment_config
MARKET_DATA=awaiting_adapter
PAYOUT_SETTLEMENT=partner_pending

Risks

• XCoins is independent from X Corp.
• Coin prices are volatile and may go to zero.
• Graduation is a market state, not a quality signal.
• Anyone can create a coin for a public handle; names and images may impersonate people or brands.
• The contract address is the only reliable coin identity.
• Wallet transactions are irreversible. Verify the network, contract, amount, and recipient before signing.

FAQ

Does the recipient need to launch the coin?

No. Anyone can launch for any X account.

Can I change the fee recipient?

No. The X handle assignment is immutable.

Why can’t I collect an earned amount?

The coin has not graduated, so its fees remain locked on the curve.

Is the Arc deployment live?

This source does not include Arc deployment configuration. Do not treat fixture addresses or interface previews as production contracts.