How it works

Addressed to an identity, held by a program, released by proof.

@recipient

Resolved to X user ID

Escrow

Per-payment PDA on Solana

X login

OAuth 2.0 + PKCE

Wallet

Signed ownership proof

You authorize with X's official OAuth 2.0 (Authorization Code + PKCE). Our server validates the state and verifier, calls GET /2/users/me with your token, stores only your numeric ID, username and avatar, and then discards the token. Your session is a signed, HttpOnly cookie.

Handles can be changed, released and later claimed by someone else. The numeric ID is permanent for an account, so every payment is locked to the ID resolved at send time. A rename never redirects funds.

Availability

X sign-in configured
X lookup key configured · API credits also required
Direct mainnet payments configured · verified wallet required
Devnet escrow deployed and transaction-tested

How it works

How does sign-in work?

Why the numeric X user ID, not the @handle?

Where is the money held?

What does the oracle do?

Fees?

Refunds

Residual risks

Is this available everywhere?

Affiliation

Availability