Fees for an X account
A coin can be launched for an X account rather than for a wallet. When it is, the
creator share of its trading fees belongs to that account, and the account’s owner claims
it here by pointing the account at a wallet.
Signing in with X is not live yet
The finished flow is: you sign in with X, our server checks with X that the account is
yours, and it then signs an authorisation naming your account’s id and your wallet. The
contract verifies that signature. That login does not exist yet — nothing on this
page will ask you for X credentials, and no page that does is ours.
Everything else here is real and reads the chain: what an account is owed, which wallet it
has bound, and the claim itself. Only the step that produces the authorisation is
waiting on the bot’s API access, and until it arrives this page cannot produce one.
1The account
X user ids are numbers. The id is the truth here and a handle is not: a handle can
be renamed and can change owner, so this site never resolves one and never guesses one.
A coin’s page shows the id it was launched for.
Every coin launched on VVVX is checked against this id, straight
from the chain. Nothing is typed into a database here and nothing is remembered.
2What this account is owed
3Bind a wallet
Binding points the account at one wallet: from then on that wallet, and nothing else, can
claim what the account has earned. It can be changed later — people lose keys — and
every change is an event on chain, visible for ever.
4Claim
A claim pulls each coin’s creator share out of the fee lock and forwards it to the bound
wallet in the same transaction. Nothing is held in between, and anything unclaimed simply
stays where it is.
What this asks you to trust
Whoever holds the signer key can bind any X id to any wallet, and could therefore take any
unclaimed creator fees of any account that has not claimed yet. A chain cannot check who
owns an X account, so something off chain has to vouch for it, and here that something is one
key. This is the same trust as “our server says this login is real”, written down
plainly instead of left implied.
What limits it: the signer is separate from the address that deploys the contracts and
from the one the platform fee is paid to, it can sign nothing but bindings — it
holds no money, owns no contract and cannot move a coin, a pool or a fee — and every
binding it authorises is an event on chain, so a wrong one is visible immediately and for
ever.
The signer can be a multi-signature Safe rather than a single key: the contract accepts a
contract wallet’s signature as readily as a key’s, so no binding is possible without
the Safe’s threshold agreeing, and the Safe’s owners can be swapped if one is lost
or leaked. The address below cannot be changed — there is no setter, deliberately, because
one would hand whoever controls it the one pot of money a compromised signer can reach. Read
that address: if it is a Safe, rotation exists; if it is an ordinary key, it does not,
and a leak could not be undone.
Unclaimed fees are never swept. There is no expiry, no reclaim, and no path by which
the platform can take them. While an account has bound no wallet, its fees sit in the fee lock
and nobody at all can move them — not the platform, not the signer, not the
binding contract. That is the resting state of every X launch, and it costs nothing to leave
it there for years.
Binding contract—
Signer it accepts—
Fee lock it pulls from—
Read from the contract in this browser, not written into this page.
Every other address · How an X launch works