Dedicate
Pick a GitHub account. We resolve the handle to its permanent ID, deploy a fixed-supply Pons token, and point the launch's fee redirect at a fresh vault keyed to that ID. Your wallet signs the deployment. We never hold keys.
fees / routing.diff
Dedicate a Pons token to any GitHub account. Trading fees collect in a vault locked to that account's permanent user ID — not its handle. The owner signs in with GitHub and withdraws whenever they want. No claim window, no application, no one to ask.
@@ pons v2 · token launch metadata @@ { name: "GitPons Dedication", supply: 1_000_000_000, // fixed, no mint fn- feeWallet: "0x9f3c…4b21", // the deployer. a stranger.+ feeWallet: vault(github_id: 583231), }
One line. Creator fees stop paying whoever pressed launch and start paying an address that only the holder of GitHub user 583231 can ever empty.
01 · identity
A GitHub username can be renamed, released, and re-registered by someone else in under a minute. The numeric user ID behind it is issued once and never reassigned. Vaults bind to the number, so a rename can't redirect anybody's money. Try a handle:
02 · mechanism
Each step is on-chain and each one is something anybody can verify or trigger. Nothing in this list requires us.
Pick a GitHub account. We resolve the handle to its permanent ID, deploy a fixed-supply Pons token, and point the launch's fee redirect at a fresh vault keyed to that ID. Your wallet signs the deployment. We never hold keys.
The token trades like any other Pons v2 launch — bonding curve first, then a pool. Every swap charges the standard creator fee. That fee has nowhere to go except the vault.
Fees sit in the launcher until someone sweeps them. collect() is public,
so anyone can push a vault's balance forward — a keeper, a holder, a bot, the author. The vault
balance is readable by anyone at any time.
The author signs in with GitHub and connects a wallet. The contract checks that the signed-in ID matches the vault's ID, then releases the balance to their address. Unclaimed vaults just keep accruing. There is no expiry and no one who can drain it early.
03 · ledger
Dedications, IDs, balances, and claim state are readable on-chain. Nothing here is hidden behind an account.
| Account | GitHub ID | Vault | Accrued | State |
|---|---|---|---|---|
| @octocat | 583231 | 0x7ac9…e410 | 4.812 ETH | unclaimed |
| @torvalds | 1024025 | 0x1f30…9b7d | 2.194 ETH | unclaimed |
| @sindresorhus | 170270 | 0xbb42…0c15 | 0.977 ETH | claimed |
| @antirez | 65632 | 0x4e8d…7712 | 0.431 ETH | unclaimed |
| @yyx990803 | 499550 | 0x9c07…33af | 0.208 ETH | claimed |
04 · questions
No, and that cuts both ways. Anyone can dedicate a token to any public GitHub account, which means a vault can be waiting for someone who has never heard of this. It also means a dedication is not an endorsement — a token named after a maintainer says nothing about what that maintainer thinks of it. If you'd rather not have one, you can leave the vault untouched forever; the funds stay locked and nobody else can take them.
Nothing. The vault is keyed to your numeric user ID, which follows you through any number of renames. The display name on the ledger updates the next time we resolve it.
They get the handle, not the ID. Their account has its own separate number, so it resolves to a different vault — an empty one. This is the main reason the binding is numeric.
No. The fee redirect is set at launch and the release condition is fixed in the contract. There is no admin key, no pause function, and no upgrade path that would let us move someone's balance. The tradeoff is that we also can't reverse a mistake for you.
A launch fee at deployment, disclosed on the dedication screen before you sign. Zero percent of the vault. The claim itself costs the author nothing but gas.
Neither. GitPons is an independent layer built on the public Pons launch contracts and the public GitHub API. GitHub is a trademark of its owner and this project is not endorsed by them.