> For the complete documentation index, see [llms.txt](https://docs.bundlefren.com/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bundlefren.com/v1/launchpads/pons.md). # Pons Learn how to bundle your launch on Pons. ### Overview Launch a new Pons V2 token on Robinhood through Bundle Fren. Enter your token details during setup, and the token is deployed when you launch the bundle. Pons uses **Burst Bundle** mode: the app deploys your token, waits for your chosen initial buy delay, then sends the bundle buys in rapid succession. Transactions execute independently, so buys are not guaranteed to land in the same block or ahead of other traders. See [Bundle Types Explained](https://docs.bundlefren.com/v1/getting-started/supported-networks#bundle-types-explained). This page explains the Pons settings and links to the shared setup guides where the process is the same. This page explains the Pons settings and links to the shared setup guides where the process is the same. ### 1. Token Details Select **Robinhood** as your network and **Pons** as your launchpad. * **Token Name** — Enter your token's name, up to 40 characters. * **Token Symbol** — Enter a ticker using 1–15 uppercase letters. * **Description** — Add a description of your project, up to 400 characters. * **Token Image** — Upload your token's image. * **Twitter / Telegram** — Optionally add links to your project's social accounts. * **Pair Asset** — Choose from the available pair assets. ETH is selected by default. For the ETH pair, the token graduates once the bonding curve raises 4.2 ETH. * **Deployer Buy** — Enter the ETH amount the deployer will use to buy tokens as part of token creation. Set this to **0** to launch without a deployer buy. * **Deployer Private Key** — Enter the private key of the wallet that will deploy your token. Pons tokens have a fixed total supply of **1,000,000,000** tokens with **18 decimals**. **Advanced** Open **Advanced** to change your token's tax settings: * **Custom Tax Wallet** — Enable this to send taxes to a different wallet, then enter its address. Otherwise, taxes go to the deployer wallet. * **Tax (%)** — Set the tax applied to buys and sells, from **0% to 10%**, with up to two decimal places. The default is **0%**. * **Snipe Tax Exemptions** — Turn this on so the first 32 bundle wallets, or 31 with a Deployer Buy, can skip Pons's opening buy tax. This is off by default. The exemption limit depends on your Deployer Buy: | Deployer Buy | Bundle wallets that can skip the opening buy tax | | ------------------ | ------------------------------------------------ | | 0 ETH | 32 | | Greater than 0 ETH | 31 | Wallets are selected in bundle order, and each wallet address is counted once. The deployer and tax wallet already skip this tax, so they are left out of this selection. **You can still use more than 32 wallets.** The extra wallets will still buy, but may pay the opening buy tax if they buy during the first 3 seconds. For example, with 50 wallets needing an exemption and no Deployer Buy, the first 32 skip this tax. The other 18 still buy. Closing Advanced does not turn off your settings. Open it again to change them. **Initial Buy Delay, Launch Mode and Payment** * **Initial Buy Delay (seconds)** — Set the delay before the bundle wallets buy. The default is **3 seconds**, and the supported range is **0–30 seconds**. This delay applies to the bundle buys; the Deployer Buy happens during token creation. * **Launch Mode** — Pons uses **Burst Bundle** mode. * **Payment Option** — Select from the payment options shown in the app. See [Bundle Fee](https://docs.bundlefren.com/v1/payments/bundle-fee) for an explanation of ETH and wallet-based payments. Pons's opening buy tax starts at **99%** and decreases over the first **3 seconds** after launch. Use a **3-second delay** to wait for this opening tax to end before your bundle wallets buy. The **Tax (%)** you set above still applies, even to wallets with a Snipe Tax Exemption. ### 2. Distributor Setup Add the wallet you will use to send ETH to your bundle wallets. For payment options with an ETH fee, you can pay from the distributor or set up a separate payment wallet. See [Distributor Setup](https://docs.bundlefren.com/v1/bundle-setup/distributor-setup). ### 3. Wallet Setup Pons uses a bonding curve, so you do not enter initial ETH or token liquidity. * **Number of Wallets** — Choose how many wallets will buy, up to **98**. Wallets used to pay the token fee count towards this total. * **Max Buy Per Wallet** — Enter an **ETH amount** for each wallet to buy. * **Randomize Buys** — Let each wallet buy a slightly different amount. Choose how far below the maximum its buy can be. For example, a 0.01 ETH maximum with 5% randomization gives buys between 0.0095 and 0.01 ETH. Calculate the distribution, review the amounts, then generate or import your wallets. If you generate wallets, save their seed phrase and private keys before continuing. See [Generate or Import Wallets](https://docs.bundlefren.com/v1/bundle-setup/generate-or-import-wallets) for the shared wallet steps. ### 4. Funding Wallets Fund your bundle wallets with the ETH amounts shown in the app, including the transaction fees. You can add extra ETH per wallet during distribution if needed. Also ensure your deployer has enough ETH for deployment and any Deployer Buy, and your selected payment wallet has enough for the ETH payment and its transaction fee. See [Funding Wallets](https://docs.bundlefren.com/v1/bundle-setup/funding-wallets). ### 5. Simulate and Launch Review your bundle summary, including the pair asset, Tax, tax wallet, buy amounts, exemptions, initial buy delay and payment option. Run the simulation. If it shows an error, fix it and try again before launching. Once the simulation succeeds, launch your bundle. The app creates your token and sends the buys using Burst Bundle mode. After launch, open the Manage page to review your wallets and manage the token. See [Wallet's Page Overview](https://docs.bundlefren.com/v1/post-launch-management/manage-page-overview) for the shared management features.