DOCS
How it works
Protocol
Overview
Split is a layer on top of the Pons launchpad on Robinhood Chain. A team launches a token together, fixes in advance how the creator revenue is split across its wallets, and every member collects their own share. Every step is a transaction your own wallet signs. Split never takes custody of tokens or funds.
The market itself is Pons. The curve, graduation, the Uniswap pool and trading all work exactly as they do for any other Pons launch. What Split adds is who the creator is: not one wallet, but a splitter contract that holds a fixed list of wallets and their shares.
That removes the usual group-launch problem. Nobody has to act as treasurer, collect the fees and pay everyone out by hand. The split is on chain before the first candle, and it cannot be changed afterwards — not by the launcher, not by the team owner, not by us. See fee split and claims.
Pons in brief
Every Split token is an ordinary Pons V2 launch. This is the part Pons runs.
- 01Bonding curveThe whole supply — one billion tokens — is minted straight to a bonding curve. Nobody, including the team, holds tokens set aside before trading opens. You buy from and sell back to the curve.
- 02GraduationOnce the curve has collected its threshold, the launch graduates into a Uniswap v4 pool seeded from what the curve collected. The liquidity is locked permanently. Tokens in your wallet stay the same tokens.
- 03Custom pairsA launch does not have to be priced in ETH. Paired against another token, that token becomes the currency of the whole launch: trades, fees and payouts.
- 04Snipe taxBuys in the first seconds pay a steep tax that decays to zero (99 % over three seconds today). Wallets on the launch’s exemption list are spared.
- 05Launch feePons charges a small fixed fee in ETH per launch (0.0005 ETH today). It goes to Pons and is not creator revenue. Split adds no launch fee of its own.
The full picture, including how Pons handles fees after graduation, is in the Pons V2 docs ↗.
Teams and shares
A team is a list of wallets and a share for each of them. Shares always add up to 100 %.
A permanent team has a name, a profile, members and a revenue split, and can launch as often as it likes. A temporary team exists for a single launch only — you set the wallets and shares in the launch form, and that is the whole team.
Adding a wallet to a team means it receives revenue. Nothing more. It does not mean the wallet agreed to anything, and the app never shows it as if it had. See roles.
Launch lifecycle
Every launch goes through the same four steps. The first one is a single transaction.
- 01LaunchThe launcher signs one transaction. Inside it, a fresh splitter is created with the team’s wallets and shares, the token is launched on Pons with that splitter as its creator, and — with a Team Buy — the opening buy is made. If any part fails, none of it exists.
- 02CurveThe token trades on its Pons bonding curve. Every trade pays a fee, and the creator part of it accrues to the splitter, not to any one wallet.
- 03GraduationOnce the curve is bought out, Pons moves the launch into a Uniswap pool whose liquidity is locked. Nothing is required of the team, and the splitter keeps receiving the creator fees.
- 04ClaimAt any time, each member collects their own share. Nobody pushes payouts, and nobody can collect for someone else.
Fee split
Where every trading fee goes — from the trade to the member’s wallet.
Every trade pays Pons’ base fee of 1 %, on the curve and in the pool alike. Pons keeps 30 % of it (0.3 % of the trade); the other 70 % (0.7 %) is the creator’s. On top, the launcher can set a creator tax of 0 to 10 %, which goes to the creator in full. Base fee and tax together may not exceed 11 %. These are Pons’ numbers today; each launch keeps the ones it was created with.
The creator of a Split token is its splitter, so the whole creator revenue lands there, in the pair currency. Pons’ own optional buyback is switched off for these launches, so none of it is diverted. The splitter then divides everything it receives:
- 0180 % team poolDivided exactly by the shares the team set. Each member claims their part.
- 0220 % platform shareGoes to the platform revenue vault, which books half as treasury allocation and half as buyback reserve. See platform share below.
An example: 100 ETH of trading on a launch with a 2 % creator tax, launched by a team of three — Alice, Bob and Carl — split 50/30/20.
- Base fee, 1 %
- 1.000 ETH
- to Pons
- 0.300 ETH
- to the creator
- 0.700 ETH
- Creator tax, 2 %
- 2.000 ETH
- Creator revenue, in the splitter
- 2.700 ETH
- Platform share, 20 %
- 0.540 ETH
- treasury allocation
- 0.270 ETH
- buyback reserve
- 0.270 ETH
- Team pool, 80 %
- 2.160 ETH
- Alice, 50 %
- 1.080 ETH
- Bob, 30 %
- 0.648 ETH
- Carl, 20 %
- 0.432 ETH
The platform share is 20 % for every launch. The factory has a hard ceiling of 50 %, and that ceiling is used exactly once: for the launch of our own platform token, never for a team’s launch — see the platform token launch. The share in force when a launch happens is written into its splitter and stays there. There is no extra trading tax, and the tokens from a Team Buy are not touched: 100 % team, 0 % platform.
Claims
Claims are pull, not push. Every wallet collects its own share, whenever it wants.
Pons first holds the creator fees in its fee escrow, credited to the splitter. A harvest moves them into the splitter: it pulls the credit, books the 80/20 split for every member at once and sends the platform share on to the vault. Anyone can call it. A claim then pays out only the caller’s part. If a harvest is due first, claiming takes two transactions — the app shows the harvest as the first step and the claim as the second.
The order and timing of claims never change anyone’s final amount. Claiming early does not take from the others, and waiting does not lose anything. If sending the platform share fails, the harvest still counts and the team can still claim — the platform part waits in the splitter until someone retries it.
Tokens sent to a splitter by hand are not revenue and are never paid out. Only what arrives through Pons counts.
Team Buy
An optional opening buy, made in the launch transaction and owned by the whole team.
The launcher pays for it. The bought tokens do not go to the launcher but to a distributor created for this launch, which holds them for the team by the same shares as the revenue split. 100 % goes to the team; the platform takes nothing from a Team Buy. The distributor is exempt from the snipe tax.
Each member claims their tokens from the distributor in a transaction of their own. If the curve could not fill the whole amount, the rest is refunded to the launcher in the same transaction.
Snapshots
A launch is frozen at the moment it happens.
Wallets, shares, the platform share, the pair and the snipe-tax exemptions are written into the launch’s own splitter and can never be edited. Changing a team afterwards only affects its future launches.
Pons allows 32 extra snipe-tax exemptions per launch. The launcher takes one of them and, with a Team Buy, the distributor another — so you choose up to 31 wallets, or 30 with a Team Buy. The splitter and the router are exempt anyway. Team size is not limited by this; with more wallets, the launcher picks.
Platform share
What the protocol keeps, and where it goes.
The platform share of every launch goes to one vault, in whatever currency the launch is paired with. The vault books half as treasury allocation and half as buyback reserve — 10 % of creator revenue each under the normal 20 % policy.
The treasury allocation funds the project; only the treasury account can withdraw it, and only to itself. The buyback reserve cannot be withdrawn at all. Its only use is to buy the platform token and burn it: a stock-token reserve is first swapped to ETH, and the ETH buys the token on Pons, and exactly what was bought is burned in the same transaction. The platform token has not been launched yet, so the reserve is building up until then.
The platform token launch
One launch, and only one, runs at a 50 % platform share: the launch of the protocol’s own token.
Split will launch a platform token of its own on Pons, $SPLIT, paired with ETH. For that single launch the platform share is raised to 50 %; right after it, the policy goes back to 20 %. Because every launch keeps the share it was created with, no other launch — before or after — is affected. 50 % is the ceiling written into the factory, so it can never go higher, for this launch or any other.
The point is the burn. The vault still splits the platform share 50/50, so a larger share means more ETH in the buyback reserve — and that ETH buys the platform token back and burns it. Trading in the platform token itself therefore feeds its own burn. The platform token launches with a 0.5 % creator tax, so a trade pays 1.5 % in total with the base fee. Per 100 ETH traded:
- Base fee, 1 %
- 1.000 ETH
- to Pons
- 0.300 ETH
- to the creator
- 0.700 ETH
- Creator tax, 0.5 %
- 0.500 ETH
- Creator revenue, in the splitter
- 1.200 ETH
- Platform share, 50 %
- 0.600 ETH
- treasury allocation
- 0.300 ETH
- buyback reserve, burned
- 0.300 ETH
- Burned, as a share of all volume
- 0.3 %
In short: 0.3 % of all trading volume in the platform token is used to buy it back and burn it — on every buy and every sell, for as long as it trades. At the normal 20 % it would be 0.12 %, so the 50 % share burns 2.5 times as much. How many tokens that burns depends on the price at the moment of the buyback: the lower the price, the more tokens the same ETH removes. Buying back needs the platform token’s Pons pool, so the burn starts at graduation; what the curve phase collects waits in the reserve until then.
Risks
Transactions are irreversible once signed. Tokens can lose all of their value. A team is only as trustworthy as its members, and a wallet in a split is not an endorsement. Nothing here is financial advice.
Pons V2 has been live since August 2026 and is young. Pons keeps powers of its own: its owner can redirect a launch’s creator fees to another recipient after a three-day timelock, and it sets fees and caps for future launches. Launch Together cannot prevent either.
Web app
Wallet and sign-in
Your wallet address is your identity. There is no account and no password.
Connecting a wallet is enough to browse, trade and claim. To change anything the app stores — a profile, a team — you sign a message once (Sign-In with Ethereum). That signature costs nothing and moves nothing; it only proves the wallet is yours.
Explore and token pages
Explore lists every Split launch, newest first, with its market cap and how far along the curve it is. A token page shows the chart, trades, holders and the team behind it — the split, the members and what each of them has earned.
Market data comes from the chain directly while a token is on its curve, and from DexScreener once it has graduated. You can buy and sell from the token page: against the Pons curve, and after graduation in the Uniswap pool.
Teams and roles
Team Discovery lists every permanent team. Each wallet in a team has exactly one role.
- 01OwnerRuns the team: profile, members, the revenue split and who may launch.
- 02LauncherMay launch for the team. Only a member who has joined can be a launcher.
- 03Verified memberHas confirmed the membership from their own wallet. This is public.
- 04Unverified beneficiaryReceives a share and has confirmed nothing. Claiming does not change that — only the wallet itself can join.
Launching a token
The launch page takes you through the token, the pair, the team and its split, the creator tax, the exemptions and an optional Team Buy. Before you sign, every value that decides the economics — the fee, the platform share, the pair approval — is read from the chain again. If something changed, you see the new summary first.
For an ERC-20 pair with a Team Buy, a second signature may be needed first: an approval for the launch router. Everything else is the one launch transaction. See launch lifecycle.
Profile and dashboard
Every wallet has a page: its launches, its teams and what it can claim. A profile adds a name, an image and links, and is optional. If someone added your wallet to a team, your page shows what is waiting for you the moment you connect — even if you have never been here before.
Contracts
Deployed contracts
All contracts live on Robinhood Chain (4663). None of them can be upgraded.
- GroupLaunchRouter
0x15c285a9a8121751bd7cedc243d3555e4197cd6dEXPLORER ↗- GroupSplitterFactoryV2
0x4dd6cdd1a44c3fe9e8ef7ee1f5f720c1db29086cEXPLORER ↗- GroupFeeSplitterV2 (template)
0x61e76313b52e3cdcf348471e63abdeaf941ff377EXPLORER ↗- TeamBuyDistributorFactory
0xf4839f3aa70f9be4d24eb0916b5a3af8fe64057cEXPLORER ↗- TeamBuyDistributor (template)
0xf091a9cdae2ea9e7bff57a516dcc075c2b023d6dEXPLORER ↗- PlatformRevenueVault
0x9a8da6b681595ad90df154a824753e6d17a112bfEXPLORER ↗
Splitters and distributors are one per launch, cloned from the two templates; the template addresses are not the ones you claim from. The Pons contracts the router talks to:
- Pons LaunchFactory
0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7eEXPLORER ↗- Pons LaunchAndBuy
0xe33E9E479dF8802cb0866d5d05258bEc4cF62948EXPLORER ↗- Pons FeeEscrow
0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9eEXPLORER ↗- Pons MemeHook
0xE5e702641Ea86F4ae6cC3cDaeD2B886f976Be044EXPLORER ↗
GroupLaunchRouter
The only launch path. launch(request) creates the splitter, creates the Team Buy distributor if there is one, calls Pons, binds the launch to the splitter and activates the distributor — atomically. It has no owner and no admin functions, and is wired to the factories and Pons at deployment; that wiring can never change.
The request pins the platform share and treasury the launcher saw, and a deadline. If the policy changed in between, or the deadline passed, the launch reverts instead of going through under different terms. It emits GroupLaunched with the launcher, token, splitter, curve and distributor.
On Pons, the deployer of a Split token is the router. The wallet that actually launched is recorded in GroupLaunched.launcher — the only place it is.
GroupFeeSplitterV2
One per launch, cloned by GroupSplitterFactoryV2 from the template. It is the creator fee recipient on Pons and holds the snapshot: members, shares, platform share, treasury and pair currency. harvest() is permissionless and settles the fees; claim(asset) pays only msg.sender. There is no claimFor.
To check that a splitter is ours, compare its implementation() with the template address above.
The factory has an owner. It can change the platform share (never above 50 %), the treasury and the supported pairs — for future launches only. It has no power over existing splitters, their funds or their members.
TeamBuyDistributor
Created by TeamBuyDistributorFactory inside the launch, only when there is a Team Buy. It receives the opening-buy tokens, copies the splitter’s members and shares and lets each member claim() their part. distributorOf(splitter) finds it.
PlatformRevenueVault
Receives the platform share. sync(asset) is permissionless and books whatever arrived, 50/50 into treasury allocation and buyback reserve. withdraw is for the treasury only, pays only to itself and only from its half.
The owner runs the buyback: convertBuybackReserveToEth swaps a stock-token reserve to ETH, buybackAndBurn buys the platform token with ETH reserve and burns it. The platform token can be set exactly once and is not set yet.