Bundle Launch a Token on Arc: Modelling, Capital and Disclosure

A bundle launch packages deployment, pool creation, initial liquidity and a set of coordinated buys into one atomic Arc transaction. The point is not secrecy — it is ordering: when the pool is created and bought in the same transaction, no bot can see your liquidity and buy ahead of you at a lower price.

The Arc Bundle Launch tool models the whole thing before you sign. This guide covers the four decisions that model actually turns on: how much pool capital, how much bundle capital, how many wallets, and where the LP tokens end up. It finishes with the part most teams under-plan — telling people what you did.

Before you start

• One funded wallet on Arc Mainnet. Chain id 5042, RPC https://rpc.mainnet.arc.io, explorer https://explorer.arc.io. The bundle is a single transaction, so the wallet that signs has to hold the 50 USDC service fee, the gas, the pool capital and the bundle capital at the same time. Add the network with Arc's connect guide if your wallet does not list it.
• A clear view of your token parameters. A bundle launch also deploys the ERC-20, so supply, mint policy, taxes and limits are decided here too. The defaults follow the same shape as the standard launch walkthrough.
• A disclosure plan. Bundle buys are ordinary contract behaviour on Arc, but they are not invisible. Know what you are going to publish before you publish anything else.

Remember that Arc's gas token is USDC in its 18-decimal native form, while pool math uses the 6-decimal ERC-20 interface at 0x3600000000000000000000000000000000000000. Same balance, two interfaces — the tool handles the conversion, but never add the two figures together yourself.

1. Fund one wallet for the whole launch

Total the wallet needs: 50 USDC for the service fee, the pool capital, the bundle capital and a little gas headroom. If those add up to more USDC than you hold, the launch reverts — atomicity cuts both ways.

Gas is the smallest line item and the easiest to get wrong. Arc's fee floor is 20 Gwei — 0.00000002 USDC per gas unit, so 100,000 gas costs 0.002 USDC. The bundle contains a contract deployment, a pair creation, a liquidity add and one swap per wallet, so it costs more than a plain deployment: a forty-buy bundle in the 0.1–0.2 USDC range is the right order of magnitude, and your wallet shows the exact figure before you confirm.

2. Model the launch before you configure it

The model is the most valuable part of the tool, because a bundle launch is hard to reverse. It computes, from constant-product pool math:

• Total capital committed to the launch.
• Opening FDV implied by the pool you are seeding.
• Supply captured by the bundle as a percentage of total supply.
• Average entry price across all bundle buys, which is worse than the opening price because each buy moves the curve.
• Per-wallet allocation, after any maximum allocation per wallet you set.

Change one input at a time and watch what moves: raising pool capital lowers the opening FDV, while raising bundle capital at fixed depth worsens the average entry and captures more supply. Wallet count only splits the total.

The model is a planning estimate. It excludes the 0.30% Uniswap V2 swap fee, gas, and the slippage of anything you execute separately. Treat it as a map, not a receipt.

3. Choose the pool capital and the supply share

These two numbers together are the opening price: price = pool USDC ÷ (supply share × total supply). Everything else in the launch is downstream of them.

A few principles hold regardless of size:

• Depth decides how far price moves per trade. Two pools can open at the same valuation with different depth, and the first 1,000 USDC buy moves the shallow one far further — choosing initial liquidity depth has the arithmetic.
• Place enough supply that the pool is not the constraint. If the pool holds 25% of supply, buyers can in principle buy 25% of supply — that is the discovery you are inviting. Most launches place a third to two thirds in the pool.
• Check the pool against your max wallet limit. If the pair cannot hold its own tokens, every buy reverts. Exempt the pair from tax and from wallet limits.

4. Set the bundle capital and the wallet count

Bundle capital is your own USDC buying your own token at the modelled average price. Be honest about what that is: a position, not a price floor.

How much. There is no correct number, but there is a clearly wrong one: enough bundle capital to walk the price up against your own shallow pool. A bundle that buys 15% of the pool's starting USDC pays dramatically more on its later fills, and the average entry suffers. Deeper pool plus smaller bundle gives a better average.

How many wallets. Up to 40. More wallets produce a flatter holder distribution, which some teams want for presentation, and each one carries gas. A maximum allocation per wallet should be large enough that every wallet receives a usable amount; forty dust wallets are worse than ten real ones.

The fee insight. Uniswap V2 charges 0.30% on every swap, and those fees accrue to the pool's reserves, which belong to the LP tokens. If you keep or lock the LP, you own a proportional share of the fees your own bundle buys paid — not free, but a real offset.

5. Pick the destination for the LP tokens

The launch form can route the LP tokens three ways, and this is the choice traders will inspect hardest.

• Keep them in your wallet. Simplest, and the weakest signal: an unlocked position can be withdrawn whenever the holder chooses, which is precisely what buyers are taught to check.
• Lock them. They go to the Arc Liquidity Locker with a publicly readable unlock date. Twelve months is the common middle ground; the liquidity lock guide covers duration and verification.
• Burn them. The strongest commitment available, because the liquidity can never be withdrawn by anyone. It is also irreversible: no migration to a new pair, no recovering the assets. Only burn if you are certain you will never want the capital back.

Because the LP tokens are forwarded inside the launch transaction, there is no window where unlocked LP sits in a wallet waiting for someone to notice.

6. Disclose the bundle before you launch

Everything a bundle launch does is on the public Arc Explorer: the wallets, the buys and the LP destination. Disclosure is not about whether people find out, but whether they find out from you.

Publish, before or at launch:

• The contract and pool addresses.
• The percentage of supply the bundle captured and how many wallets hold it.
• The LP destination, and the unlock date and locker contract if locked.
• The tax structure and where tax revenue goes.
• Your intention for the bundle position: held, vested, or sold on a schedule.

A disclosed bundle is a launch mechanic. An undisclosed one looks exactly like an insider allocation, and the market will treat it that way once the wallet distribution is noticed. The Arc Token Checker reports ownership, taxes, concentration and liquidity for any token, so assume your buyers will run it.

7. Review, pay and execute the atomic launch

Read the final model output against your notes: opening FDV, bundle percentage, per-wallet allocation, LP destination. Then sign the flat 50 USDC fee and the launch itself.

The whole sequence settles in one transaction, and one confirmation is final on Arc. When the explorer shows it, the token exists, the pool exists with the liquidity you specified, and every bundle wallet holds its allocation. There is no second step to race.

What it costs

Item	Amount	Notes
Arctools service fee	50 USDC flat	One payment per launch
Pool capital	Your choice	Becomes liquidity you own as LP tokens
Bundle capital	Your choice	Spent in the bundle buys, returns as tokens
Gas	Cents	Higher than a plain deploy because of the buys
Arctools locker, if used	50 USDC	Separate service if you lock LP rather than burn

A worked example, with the figures labelled estimates rather than promises. Seed 6,000 USDC of pool capital against 500,000,000 of a 1,000,000,000 supply and bundle 1,500 USDC across twelve wallets. The opening price is 6,000 ÷ 500,000,000, or 0.000012 USDC per token — an implied FDV of 12,000 USDC. The bundle spends 1,500 USDC walking up the curve, so it captures somewhat fewer tokens than 1,500 ÷ 0.000012 at a worse average than the opening price. Total exposure that day: 50 USDC of service fee, 6,000 USDC of liquidity (still yours), 1,500 USDC converted into your own token, plus cents of gas.

Common mistakes

• Funding only the bundle. The pool capital and the fee have to be in the wallet at the same time as the bundle capital.
• Bundling more than the pool can absorb. A bundle that buys a large share of the starting USDC pays a bad average price for the privilege.
• Forty dust wallets. Gas scales with wallet count while the gain is small; fewer, better-funded wallets read more honestly.
• Burning LP by reflex. Burning removes the ability to migrate or withdraw forever. Lock instead if you are not certain.
• Treating the bundle as demand. Buying your own token establishes a starting position and an ordering guarantee. It does not create buyers, and if none arrive you own the position.
• Staying quiet. The checker and the explorer make concentration obvious. Voluntarily publishing it is the difference between a mechanic and a scandal.
• Ignoring the fee floor. Sub-20-Gwei transactions are dropped by Arc's mempool without an error; if a launch seems to vanish, check the fee first.

Where to go next

If the bundle is your opening position, the liquidity lock guide is the natural next read — it is what converts "we own most of the pool" into "and we cannot leave". To keep the pool tradeable as volume arrives, learn to add and remove liquidity on Arc without shifting the price. If you would rather launch without bundling and set your price purely through pool depth, the standard launch walkthrough covers that path end to end.