Every X account already has a vault.
Anyone can launch a Pons token and dedicate it to any X account. The trading fees go not to the deployer but into a vault bound to that account's permanent numeric id, so the owner may know nothing about the token until the day they decide to look.
Resolves to a permanent numeric id and the vault address derived from it.
Six steps. The id is the only thing anyone is trusted with.
- 01
Pick the account
An X handle is turned into its permanent numeric id. A handle can be renamed, dropped and taken by somebody else, while the id never moves, so the id is what the contract is told.
Not the handle, the id. A renamed account still reaches the same vault.
- 02
The vault exists as an address first
The vault address is derived from that id by arithmetic, so it is settled before anything is deployed to it. Every X account has one in this sense, holding nothing, waiting.
Nobody holds a key to it. It is a contract address, not a wallet.
- 03
Launch the token at that address
The launch names the vault as the fee recipient, and the Pons factory wires the redirect inside the same transaction. The token is dedicated from the block it is created in, with no second step to forget.
Already have a Pons token? Route its fees instead, from the wallet that deployed it.
- 04
Fees accrue without anyone watching
Every trade leaves a fee in the Pons locker, and collecting it is permissionless: anyone can trigger the payout, and it still lands only in the vault. The person it belongs to need not know the token exists.
Routing is one-way. Once fees point at a vault they stay there.
- 05
The owner proves the account
Signing in with X proves control of the numeric id the vault was built for. That is the only thing that opens it, which is why no proof of ownership is asked for at launch.
OAuth proves the id to our signer. The signer issues a voucher. The contract checks the voucher. We never hold funds.
- 06
Withdraw to any wallet
The owner names a wallet, receives a signed voucher and takes everything accrued. No lockup, no service fee, no window to miss. Until then it simply sits there, for as long as it takes.
The wallet does not have to have any history with the token, the chain or the deployer.
Vaults that exist today.
Two contracts, no proxy, no rescue.
Fees still inside the Pons locker are under Pons' control until collected; the locker is upgradeable by Pons. Once collected they are in the vault, which is not.
Factory and signer are placeholder addresses until deployment. Verified source will be linked here before any token is launched. Do not trust an address that is not on this page.
The vault has no owner, no upgrade path and no admin call. The only function that moves money out is claim(voucher, sig), and it moves money only to the payout the voucher names. You can check this on the Read Contract tab.
Five rules, printed here so you can hold us to them.
- 01
No promised return.
Fees depend on trading that may never happen. Nothing here pays a rate.
- 02
We never touch keys.
A vault is a contract address derived from an id. There is no key to hold, so there is nothing for us to hold.
- 03
Claims go only to the owner's payout.
The voucher names the address the owner chose. The contract moves funds nowhere else, and cannot be told to.
- 04
Routing is one-way.
Once fees point at a vault they stay there. Nobody, the deployer included, can point them anywhere else afterwards.
- 05
Collection is permissionless.
Anyone can pull fees from the Pons locker into the vault, because the money can only move to the vault.