Skip to content
A little coin. A clear purpose.

From a trade
to their wallet.

Ponsed adds a destination to creator fees. Launch on Pons V2, choose who gets paid, and let the route do its work.

  1. Launch with a destination.

    Give your coin a name, ticker, logo, and trading pair. Choose a GitHub user or organisation, an X account, a wallet, or a split of up to three recipients. Ponsed sends one transaction to Pons V2 on Robinhood Chain. The coin has a fixed supply of 1B and starts trading on a bonding curve.

  2. Every trade has a route.

    Every buy and sell pays Pons's 1% curve fee (70% of it to the creator, 30% to Pons), plus any creator tax you set (up to 10%, all to the creator). When the coin reaches its pair's graduation threshold, it moves into a permanently locked Uniswap v4 pool and keeps paying the creator through Pons's hook.

  3. Fees find their people.

    For GitHub and X routes, fees accrue to a vault derived from the account's identity, even before its owner joins Ponsed. A wallet route goes directly to that wallet. A split uses a fixed share table, and anyone can trigger a payout to its recipients.

  4. Connect the identity.

    The recipient signs in with GitHub or X and chooses a payout wallet. Ponsed's verifier signs a short-lived attestation that links that identity to the chosen wallet. The binding is recorded on-chain and can only use the wallet named in the attestation.

  5. Claim what comes your way.

    The vault pulls fees from Pons's escrow and forwards them to the bound wallet. It cannot pay a different wallet. For a single identity route, the owner can also take over as the creator on Pons directly, removing Ponsed from that coin's fee route.

The details

Good questions.

What exactly gets routed?+

The creator share of every trade. Pons charges a 1% curve fee on each buy and sell and pays 70% of it to the creator (30% to Pons). Any creator tax you add (up to 10%) goes 100% to the creator. After graduation the same recipient keeps earning from the Uniswap v4 pool through Pons's hook. Fees are paid in the coin's quote asset, ETH by default.

How does Ponsed work with Pons?+

A Ponsed launch is a normal Pons V2 launch: same factory, same bonding curve, same graduation. Pons only asks for one address, the creator fee recipient. Ponsed fills that field with a wallet, a per-identity vault, or a fixed split contract, and records the human-readable route on-chain.

Does the recipient have to do anything?+

Not until they want the money. Fees accumulate in Pons's escrow under the vault. When they are ready they sign in with GitHub or X, pick a wallet, and claim. A single wallet recipient is paid by Pons directly; wallets inside a split are paid whenever anyone collects the split.

Can a route be changed after launch?+

A split can never be changed. A single GitHub or X route can only be changed by the account's verified owner, who may hand the creator seat to any wallet (for example their own, taking Ponsed out of the loop). Nobody else, including whoever launched the coin or the Ponsed team, can move it.

What if they never claim?+

The fees stay claimable forever. There is no deadline, no sweep to a treasury, and no way for anyone else to take them.

Is this custodial?+

No. Ponsed holds no keys that can move fees. Vaults and splits are immutable contracts whose only outputs are the bound owner's wallet or the split's recipients. The one trusted piece is the verifier key that signs sign-in attestations; it can bind an identity to a wallet but can never withdraw, and every binding is a public on-chain event.

What does it cost?+

Pons's launch fee (0.0005 ETH) plus Robinhood Chain gas. Ponsed adds no fee.

Designed to be verifiable

What you're trusting.

  • Fees accrue in Pons's escrow and may also sit in a vault or split until collected. Claims follow the contract's payout rules: a vault pays its bound owner, and a split pays its fixed recipients.
  • A vault can only pay registry.ownerOf(identity). There is no admin withdraw, no upgrade, no pause on claims.
  • The verifier key can only produce bindings. A rogue verifier could bind an identity to a wrong wallet. Bindings are public events, the key is rotatable, and the identity's owner can re-bind with a fresh sign-in.
  • Handles are lower-cased and validated on-chain against each platform's username rules, so one account maps to exactly one vault.
  • Everything is verifiable: launches are indexed on-chain by the launcher itself, no off-chain database.

Verify the contracts

Robinhood Chain · 4663

Give your coin a destination.

Choose the people and projects you want it to support.

How it works · Ponsed