Docs

What PonsShare solves

PonsShare is a non-custodial launch layer for pons on Robinhood Chain. It adds social fee routing on top of the same on-chain factory — without changing how tokens launch or trade.

The problem

On pons, the wallet that launches a token usually receives the creator share of trading fees (70% on current factory launches). That works when the launcher and the person who should earn are the same.

It breaks down when you want to:

  • Launch a token for a creator, promoter, or collaborator
  • Route creator fees to a specific wallet at launch time
  • Assign fees to an X or GitHub handle before that person has connected a wallet on-chain

What we built

Social fee sharing

At launch, set feeWallet to your own address, a custom wallet, or a pre-generated wallet tied to an X or GitHub handle.

Same pons launch flow

Your wallet signs launchToken() on the active pons factory. Tokens trade in the same WETH pools with the same graduation rules.

Claim when ready

Fee recipients log in on /claim, see launches linked to their handle, and claim creator fees on-chain when they are ready.

How fee sharing works

  1. Launch — connect your wallet on /launch, upload token metadata, and optionally assign creator fees to another wallet or social handle.
  2. Register — PonsShare records the launch and, for social sharing, creates or reuses a fee wallet for that handle.
  3. Trade — the token trades on pons like any other launch. Creator fees accrue to the configured payout address.
  4. Claim— the fee recipient signs in, confirms ownership of the handle, and claims fees via the pons locker's collectFees(token) call.

Why we use Privy for login

The Claim page uses Privy for X and GitHub login instead of rolling our own auth. That keeps identity verification safe, standard, and auditable.

  • OAuth, not passwords— recipients sign in with X or GitHub through Privy's hosted flow. PonsShare never stores social passwords.
  • Verified handles — only the account that owns the handle can link to the fee wallet assigned at launch.
  • Persistent sessions — Privy keeps you signed in securely across visits so recipients do not need to log in every time.
  • Wallet linking on first login — when a handle logs in for the first time, their pre-generated fee wallet is linked to their Privy account.
  • Export stays gated — private keys for social fee wallets can only be exported by the Privy account that owns the linked handle.

PonsShare will never ask for your seed phrase. Launches always require your own wallet signature — Privy is used for fee-recipient identity on /claim, not for custodial control of launch funds.

What stays non-custodial

  • Launches are signed by your connected wallet — we never hold launch ETH or tokens.
  • Fee claims happen on-chain through the pons locker contract.
  • Token metadata, pools, and fee routing live on Robinhood Chain.
  • PonsShare is an interface layer — not a new protocol or custodial launchpad.

Pages