What is IndexPad?
IndexPad is a permissionless launchpad for index tokens on Robinhood Chain (chainId 4663 mainnet / 46630 testnet). Anyone can launch a fixed-supply token backed by a basket of tokenized stocks and ETFs — pick the basket, set how trade fees are split, and let every swap deepen the token's backing. There is no keeper, no snapshots, and no off-chain fee pipeline: the whole split runs inline inside the Uniswap V4 hook, in the same swap, on-chain.
IndexPad is live on Robinhood Chain testnet (46630) and has not been professionally audited. Mainnet promotion is gated behind a custody spike for tokenized equities, US-person geo-gating, legal review, and a professional audit. See Security.
Try it
- App: indexpad-launchpad.vercel.app
- Indexer API: indexpad-indexer-production.up.railway.app/stats
- Explorer: IndexFactory on Blockscout
The core idea
Every IndexPad token is built from three mechanisms:
- A fixed 1,000,000 supply, never mintable. No premine and no founder pre-mint — the entire supply is seeded as single-sided liquidity on a
USDG / indexUniswap V4 pool, opening at a 20,000 USDG market-cap floor ($0.02/token) and walking up a fixed price curve toward $1.00 as buyers arrive. Supply can only ever decrease, via redemption burns. - An inline, keeper-free fee split. The shared V4 hook skims the fee on every swap and, in the same lock, routes it three ways — into the index's USDG reserve, into basket stocks bought straight into the treasury, and (optionally) into buying the index token itself back into the treasury as bond inventory. Nothing waits for a keeper; there is no batch job to run.
- A redeemable backing floor. All of that accrues as backing in a per-index treasury. Any holder can burn their index tokens for a pro-rata slice of the whole backing basket (USDG + every stock) at any time, minus a small spread — an on-chain floor beneath the market price, with no oracle in the redemption path.
Where every fee goes
The protocol takes a flat 0.30% base fee on swap volume, plus a fixed 10% of the volatility-scaled index fee. The creator allocates the remaining 90% of the index fee across three destinations, all fixed at launch:
| Share | Recipient | Configurable? |
|---|---|---|
| 0.30% of volume + 10% of the index fee | Protocol treasury (USDG) | Fixed |
rfvShareBps (of the 90%) | The index's USDG reserve — redeemable floor | Chosen by the creator at launch, then immutable |
buybackShareBps (of the 90%) | The index token itself, taken in-kind into the treasury as bond inventory | Chosen by the creator at launch, then immutable |
| Remainder (90% − rfv − buyback) | Buys the basket's tokenized stocks into the treasury as backing | Follows from the two shares above |
rfvShareBps + buybackShareBps ≤ 9000. A creator can dial this from a pure reserve index (all 90% deepens the USDG floor) to a basket-heavy index (most of the fee buys stocks) to a buyback-heavy index (fees accumulate index-token inventory for future bond markets).
What makes it different
- No trusted operator anywhere. The fee split is a property of the swap itself — it executes inside the V4 hook's
beforeSwap/afterSwapin the same PoolManager lock. There is no keeper whose honesty or liveness holders depend on. - Fair single-sided launch. No seeded USDG and no premine: buyers bring the quote asset, so the 20k-mcap floor is a hard price floor and the launch is a one-sided bonding curve. An optional creator pre-buy is just a real market buy in the same transaction.
- Volatility-responsive fees with a snipe guard. The index fee starts at 1% (buy) / 1.5% (sell), scales up with recent price volatility toward a 3% cap, and is forced to 5% for the first two blocks after launch to tax snipers of the thin floor.
- Oracle-free redemption. Burning for backing is pure pro-rata arithmetic over the treasury's raw balances — always available, even if every price feed is down. NAV/backing displays use Chainlink, but the exit path never does.
- Hard on-chain caps. Fixed 1M supply, basket ≤ 16 stocks, stocks must be on the governance allow-list, bond discount ≤ 10% — all enforced in the contracts, not the UI.
Next steps
- Follow one fee end-to-end: How it works
- Launch your own index: Launching an index
- Integrate the contracts: Contracts overview
- Live deployment: Deployed addresses