> For the complete documentation index, see [llms.txt](https://arrowbundler.gitbook.io/arrowbundler-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arrowbundler.gitbook.io/arrowbundler-docs/arrow-bundler-for-the-ponsfamily-launchpad.md). # Arrow — bundler for the PonsFamily launchpad #### The opening decides everything The first seconds of a launch are where supply is cheapest and where the tone gets set for everyone who arrives later. Taking a position there is the difference between owning your token and buying it back at a price the market already moved. Arrow puts you there — properly, and from one screen. *** #### What you get **Your dev buy lands in the same block the token is created.** It executes inside the launch transaction itself. Nothing trades before it. **Up to 32 wallets follow immediately.** Every one of them named on the launch's exemption list, buying while the opening tax is still steep for everyone else. Zero for you. Six percent and change for anyone outside. **Everything is prepared before the launch is sent.** The curve address is known in advance and every buy is signed ahead of time, so the moment your token exists, your wallets are already moving. **634 milliseconds** from launch to the last buy. Measured on mainnet. *** #### Then you run it One page holds the whole project. * **Live price and market cap**, in dollars and ETH * **A chart** built from the token's own trades, from the first block onward * **Every wallet at a glance** — holdings, spent, current value, profit and loss * **Buy more** in set amounts, from one wallet or all of them * **Sell 5, 10, 25, 50 or 100 percent** from any wallet, or everything at once * **Sweep the ETH back** to your dev wallet in a click No scripts. No command line. No browser extensions. *** #### Wallets that stay yours Generate a dev wallet and a bundle of 5 to 32 in one click. Fund them all from a single balance. Keep several dev wallets if you run several projects, and choose which one launches. Private keys are exportable from a button next to every wallet, whenever you want them. *** #### Creator fees, collected Your share of every trade on your token accrues automatically. Arrow shows what is ready and claims it to your wallet in one click — no contract calls, no explorer archaeology. *** #### After graduation, nothing changes When your launch graduates to Uniswap v4, the page carries on exactly as before. Same wallets, same balances, same buttons, same chart. Trades simply route to the pool. Most tools stop at the launch. Arrow runs the whole life of the token. *** #### Pricing **One percent. Charged once.** Taken when you fund your bundle. No subscription, no per-launch fee, no cut of what you sell, no percentage of your profit. *** #### Start in five minutes 1. Sign up with an email 2. Generate your wallets 3. Send ETH to your dev wallet 4. Fund the bundle 5. Launch [arrowbundler.com](https://arrowbundler.com/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://arrowbundler.gitbook.io/arrowbundler-docs/arrow-bundler-for-the-ponsfamily-launchpad.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.