fees / routing.diff

The fees go to
whoever wrote the code.

Dedicate a fixed-supply pons token to any GitHub account on Robinhood Chain. The creator's share of trading fees is redirected to a vault locked to that account's permanent user ID — not its handle. The owner signs in with GitHub and withdraws whenever they want.

locker.feeRedirectsthe whole idea
  @@ pons v2 · creator fee routing @@  // 70% of pool fees belong to the creator.-  feeRedirect: 0x9f3c…4b21          // the deployer. a stranger.+  feeRedirect: vault(github_id: 583231)

One line. The creator's share stops paying whoever pressed launch and starts paying an address only the holder of GitHub user 583231 can empty.

01 · identity

Handles change. IDs don't.

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 · what you can do

Three places to start.

Dedicate a token

Pick a GitHub account, launch a fixed-supply token, and point the creator fee at a vault bound to that account's ID.

Open the dedicate flow

Launch a plain token

No dedication. Same fixed supply and locked pool, with the creator fee going to a wallet you choose.

Open the launch flow

Browse the ledger

Every dedication, its bound ID, its vault, and whether the author has claimed — read straight off the chain.

Open the ledger

Claim your vault

Sign in with GitHub, connect a wallet, and withdraw anything dedicated to your account.

Open the claim flow

03 · network

Running on Robinhood Chain.

GitPons is a thin layer over the public pons launch contracts. Everything below is readable on-chain by anyone.

networkRobinhood Chain
chain id4663
quote assetWETH
supply1,000,000,000 · fixed
pool fee1.00%
launch fee0.0005 ETH
creator / protocol70% / 30%
graduation4.2 ETH paired