Understand the basket.
Follow every fee.

One launch. One fixed basket.

Basketstock attaches a basket vault to an existing, verified Pons launch on Robinhood Chain. The creator chooses its assets and allocation weights. Future creator fees can then fund those assets for token holders.

The original Pons token represents the claim on the basket. Basketstock does not mint a second token or separate vault shares. After the launch graduates on Pons, holders can burn their tokens to receive a proportional share of the backing.

Fixed weights apply to new fees. A 50% / 30% / 20% basket allocates each new fee in those proportions. It does not continuously rebalance existing holdings; market prices can change the portfolio’s actual weights.

Set up your token. Then build the basket.

1. Set up the token. Add a name, ticker, optional description, logo, and social links. The builder currently supports ETH-paired launches. These are draft details; this step does not mint a token. Token details, the logo, and basket weights are saved on your device without requiring a wallet or chain connection.
2. Build your basket. Add 1–20 distinct assets with positive weights totaling 10,000 basis points (100%). Official stock tokens and ETH can be selected while chain reads are unavailable. Custom token metadata requires a live read.
3. Review readiness. Connect a deployed Basketstock factory and check every asset route against ETH before starting a new token launch. Fresh stock listings and usable swap routes must be verified. A saved draft never restores route readiness or contract verification.
4. Launch on Pons. Copy the prepared token details and download your logo, then open the Pons launch form. The logo remains on your device until you upload it there. Complete the launch using the wallet that will create the index, and keep that wallet as the creator-fee recipient. Return with the token address. Basketstock checks the name, ticker, pair, and canonical Pons launch record.
5. Create the vault. Recheck the routes for your connected token, review the exact addresses and weights, then confirm creation in your wallet. Your wallet must be both the original Pons deployer and current creator-fee recipient. The token cannot back itself. Assets, weights, and routes become permanent.
6. Connect creator fees. In Manage & redeem, confirm the separate transaction that sets the vault as the Pons creator-fee recipient.

Drafts are local to this browser and device; private browsing, cleared storage, or a storage error can remove them. The save indicator reports when device storage is unavailable. Setup fields do not change an already-launched token’s metadata.

How fees become basket assets.

Pons credits creator fees to its escrow. Once the vault is the recipient, anyone can call collect() to claim available credits and allocate incoming revenue across the basket.

Amounts assigned to the fee token stay in that asset. Amounts assigned to other assets remain as pending fee-token balances until someone runs a swap for that leg. A failed swap leaves its allocation pending.

The supplied adapter uses direct Uniswap V3 pools. Each swap enforces an output floor based on a 30-minute time-weighted average price, less the pool fee and a 1% maximum deviation. Pools need sufficient price history and active liquidity.

Basketstock takes no additional protocol cut, keeper tip, or exit fee. “100% to the basket” means 100% of fees the vault actually receives. Pons deductions, swap fees, and network gas still apply. Fees held upstream in Pons curves or hooks must reach escrow before this vault can collect them.

Burn once. Receive your share.

After Pons graduation, open a basket in Manage & redeem, enter an amount, and preview the payout. If needed, approve the exact token amount first. The redemption transaction then burns those tokens and transfers your share of the assets and unspent fees.

The denominator includes all remaining tokens, including tokens held in liquidity pools or other contracts. It does not use an estimate of circulating supply.

A simple example

If the total supply is 1,000,000 tokens and you burn 10,000, you redeem 1% of each accounted balance. The amounts below are illustrative.

The app includes claimable escrow fees in its preview and uses the quoted amounts as minimum payouts. If the transaction cannot meet those minimums, it reverts. Burns are permanent; subsequent fees belong to the remaining supply.

A directory sourced from the chain.

The index directory reads the connected factory’s registry, newest first. You do not need a wallet to browse. Each page reads launch details, fixed allocations, fee-routing status, and graduation state at one block.

The newest page refreshes every 45 seconds while the tab is visible. Older pages keep the same block snapshot so new launches do not shift the records you are browsing. Refresh launches returns to the latest page.

Fees connected

The Pons creator-fee recipient matches the basket vault at the displayed block. This does not mean it has earned revenue.

Fee handoff pending

The vault exists, but the Pons fee recipient does not currently point to it.

Redemption open

Pons reports that the token has graduated. A payout still depends on the vault’s balances and a successful transaction.

Only indexes registered with the selected Basketstock factory appear here. This is not a list of all Pons tokens. No sample launches, estimated returns, or invented balances are inserted. A failed read is shown as unavailable, and a failed refresh keeps the last loaded snapshot labeled.

Official assets. Explicit route checks.

The asset picker loads Robinhood’s official catalog and selects deployments on Robinhood Chain. The list includes every stock and ETF contract returned for mainnet, without a ticker allowlist. Search by ticker, company, or the full contract address, then open a token to copy its address, view it on Blockscout, or add it to your draft. Active entries can be added; inactive entries remain visible for reference. A matching ticker alone never establishes that a custom token is a Robinhood Stock Token.

The catalog refreshes while the picker is open. A bundled snapshot of the official list is available immediately, including on a first visit during an API outage. Successful refreshes update the saved copy on this device. Saved listings show their date and can be used for drafting, but cannot verify current token status.

Before creation, Basketstock requires a fresh catalog response for selected official tokens, validates their onchain decimals, and searches the connected adapter’s supported V3 fee tiers. Each asset shows whether its route is ready, pending, or unavailable. A listed token may have liquidity only through another venue, so being active in the catalog does not guarantee that this adapter can buy it.

Current swap support is direct V3 only. RFQ, proprietary AMMs, and V4 routes require a compatible adapter; they are not enabled by changing a label in the picker. Every actual swap still needs simulation, wallet confirmation, and the contract’s output floor.

Robinhood Stock Tokens use raw ERC-20 balances with 18 decimals. Their corporate-action multiplier changes underlying-share exposure without changing those raw balances. Basketstock allocates and redeems raw token units, and labels payouts accordingly. It does not apply the multiplier to token amounts or apply it twice to a price.

Adding an asset does not grant a wallet allowance. Swap allowances are managed by the vault and adapter; a holder’s index-token approval is requested only when needed for a reviewed redemption. Robinhood’s product eligibility and transfer restrictions still apply.

Three contracts. Defined roles.

The factory and vault have no owner-controlled withdrawal, upgrade, or route replacement function. The app checks a connected factory’s deployed runtime against this build’s compiled contracts, then verifies its Pons dependency and any adapter runtime.

Wallets sign and submit transactions. Reads, simulations, and gas estimates can use your connected wallet on Robinhood Chain, with the app’s read-only RPC endpoint as a fallback. Chain checks reject responses from a different wallet network. The app does not hold your keys or sign for you. Runtime matching checks the build identity, not the safety of every dependency or basket asset.

Understand the limits.

• Development build, no independent audit. Local protocol tests do not replace an audit or testing against live chain dependencies.
• No guaranteed yield or value. Backing depends on received fees and asset prices. A basket can have no redeemable assets even after graduation.
• Asset behavior matters. Transfer-tax, rebasing, pausable, or restricted tokens can fail. A single asset that cannot transfer can block a multi-asset redemption.
• Routes are limited. This adapter supports direct V3 pools. V4-only assets, multihop routes, and an ETH/WETH-only wrap as a basket leg are not supported. An average-price floor cannot eliminate manipulation risk in illiquid pools.
• External dependencies remain. Pons controls its own fee accounting and governance. If escrow cannot pay, the contract has a claimFees=false redemption option for already-collected assets; the current website normally claims escrow during redemption.
• Listings are not endorsements. Verified launch origin and matching contract code do not establish an asset’s safety, legitimacy, or investment quality.