Docs

Split is a launchpad built on pons, the token protocol on Robinhood Chain. A token launched here goes through the pons factory on exactly the same terms as any other pons launch — the same bonding curve, the same trade fee, the same graduation into a Uniswap v4 pool.

One thing is different. Pons pays creator rewards to a single address. Split points them at a set of social accounts instead — an X handle, a GitHub user, a TikTok account, a wallet — split by whatever percentages you choose.

The recipients do not need to know this site exists. Rewards accrue to their account and wait. When they turn up, they sign in with that platform, connect a wallet, and withdraw.

A standard launch charges a trader 2.50%: pons’ own 1.00% trade fee, plus a 1.50% creator tax on top.

Where it lands is less obvious than it looks. Pons does not keep its whole base fee: it takes a 30% protocol share and passes the other 70% to the creator fee recipient, along with the entire creator tax. That was measured against the live protocol on a fork, not assumed — which is why an ordinary 1%/1% trade pays the creator 1.70% rather than 1.00%.

Split’s 0.50% comes out of the reward stream, not added on top of a trade. Trading a token here costs exactly what trading it on pons costs. A Split launch simply carries a larger creator tax, which is the thing that funds the rewards in the first place.

Set a different creator tax and these numbers move. The launch form shows the real ones as you change it rather than quoting the default at you. The contract’s share of the stream is capped at 25% by a constant in its bytecode, so it cannot be raised past that by anyone, including us.

Two facts about how pons pays creators shape everything else here. Both were established by reading the live chain rather than the documentation.

Creator fees are pulled, not pushed

Pons credits a fee escrow keyed by recipient address, and the recipient calls claim(). Because a recipient’s escrow balance commingles every launch it serves, one shared contract could never say which token a given wei belonged to.

So every launch gets its own RewardVault — a minimal clone, deployed at a deterministic address, installed as that launch’s pons creator fee recipient. Attribution stays on-chain and exact instead of depending on an indexer.

A trade does not credit the escrow

Fees sit on the bonding curve until someone calls sweepFees, which pons gates to the fee-sweep operator or to the curve’s deployer slot — and that slot holds the current creator fee recipient, which is the vault. So the vault is an authorised sweeper, and one harvest() call does the sweep and the claim together.

1. 1

   Someone trades

   Fees accrue on the pons bonding curve.

2. 2

   The vault harvests

   Sweeps the curve into the pons escrow, then claims out of it. Permissionless — anyone can trigger it.

3. 3

   The distributor splits

   Takes Split's share, then credits each recipient by basis points. Floor division, with the remainder going to recipients rather than to us.

4. 4

   A recipient withdraws

   Proves the account is theirs, then claims to their own wallet. The destination is fixed by the registry, so nobody else can redirect it.

A recipient is never identified by a handle. Handles change hands; the person who owns @alice today may not own it next year, and rewards pointed at a name would follow the name rather than the person.

What goes on-chain is the platform’s own immutable account id — X’s numeric user id, GitHub’s database id, TikTok’s open id — hashed with the platform so X:123 and GITHUB:123 are different identities. The readable handle is emitted in events for display only and is never load-bearing.

Claiming an account

1. 1

   Sign in with the platform

   OAuth, through the platform's own login. Split never sees a password.

2. 2

   Connect the wallet you want paid

   Any wallet. It does not have to be one you have used here before.

3. 3

   Send the binding transaction yourself

   The registry requires that the wallet being bound is the transaction sender, so an intercepted attestation is useless to anyone but that wallet.

What the verifier can and cannot do

Proving an X account belongs to a person is inherently an off-chain claim — someone has to run the OAuth flow and attest to the result. That is the verifier key. What the contracts do is make sure it is an identity oracle and never a custodian:

• It cannot move funds. It has no role in the distributor at all.
• A signature alone binds nothing — the destination wallet must send the transaction.
• Re-pointing an account that already has a wallet is timelocked three days, and the current wallet can cancel it outright.
• The current wallet can always move its own identity instantly, with no verifier involved.

The residual risk, stated plainly: a stolen verifier key could bind a never-claimed account to an attacker’s wallet and take what had accrued to it. Claimed accounts are protected by the timelock. This is unavoidable for OAuth-based identity without putting OAuth inside the EVM.

A reward split is fixed when the launch is registered and cannot be edited afterwards. That is deliberate, and it is the point of the product.

A creator points rewards at someone; that person starts telling people about it; a week later the creator quietly redirects the split back to themselves. If that were possible, every promise this product exists to express would be worthless. So it is not.

The escape valve belongs to pons, not to us: a creator can change where their creator fees are sent at any time, and that change is visible on-chain for anyone watching.

Up to 20 recipients per launch, any mix of platforms and wallets, allocations in basis points that must total exactly 100%.

The launch form reads every constraint from pons at the moment you load it — the launch fee, the creator-tax cap, the approved pair assets, and whether your wallet is allowed to launch at all. None of it is hardcoded, because pons can change all of it and several values already disagree with its published docs.

If pons has launching closed, the button says so and stays disabled rather than taking your money and failing.

Launching on pons directly instead

You can create a token on pons itself with the creator fee recipient set to the vault address this site will deploy, then attach a split afterwards with adoptLaunch. Nothing is taken on trust: the launcher checks that pons already records you as the deployer and that the fee recipient matches the address it computes.

Deployed on Robinhood Chain (chain id 4663). These are the addresses this site is running against right now — read from the same configuration the launch button uses.

The contracts are the source of truth. Everything this site indexes is a cache: prices on a token page are re-read live, trades simulate before they sign, and every figure that decides what someone is owed comes from the distributor.

• Rewards depend entirely on trading. If nobody trades a token, there are no rewards. Nothing here is a promise of income.
• A social handle on a token is not an endorsement. Anyone can point a launch at any account, and the account holder need not have agreed to anything.
• A split cannot be undone from this site once set.
• Token prices are volatile and a token can lose all of its value.
• Split never takes custody of your tokens or your wallet. Every transaction is signed by you.

Full terms are on the Terms page, and what we collect is on Privacy.