Arc Bundle Launch Explained: Atomic Launches, Economics and Disclosure

An Arc Bundle Launch packages contract deployment, Uniswap pool creation, initial liquidity and a set of coordinated buys from up to 40 wallets into a single atomic Arc transaction. Because everything lands together, no external bot can observe your pool and buy ahead of your bundled wallets: the first price a third party can trade at is the price your configuration produced. The trade-off is that you are deliberately buying your own token at launch, and that has to be disclosed.

Here is the full picture — what the mechanism actually does, what it costs, when bundling is the right call and when it is not, and how to talk about it without looking like you are hiding something.

What Arc Bundle Launch actually executes

One transaction performs a fixed sequence:

1. Deploy the token contract with the supply, decimals, tax and limit configuration you set.
2. Create the Uniswap pair on Arc Mainnet and seed it with the initial liquidity you specified.
3. Execute the bundled buys across your chosen wallet set, up to 40 recipients, each with an optional per-wallet maximum allocation.
4. Handle the resulting LP tokens — optionally forwarding them to the Arc Liquidity Locker or burning them so traders can verify the pool cannot be pulled.

Because it is one transaction, it is all-or-nothing. There is no intermediate state where the pool exists but the buys have not happened yet, and therefore no block in which a sniper bot can see your reserves and act on them.

Why atomicity is the whole point

A conventional launch is two or more transactions: deploy the token, then create the pool and add liquidity. On a chain with a public mempool that sequence leaks. Anyone watching sees the liquidity transaction coming and can submit a buy in the same block at the pre-liquidity price. The bundle removes the window rather than trying to win the race.

This matters less on Arc than it does on chains with an aggressive MEV market — Arc's fee market has a 20 Gwei floor and no bidding war for inclusion order — but the window it removes is real, and on a chain that finalises in under a second there is no reorg to undo a bad first block. A pool that is created and bought atomically simply has no first block for anyone else to occupy.

What the launch model calculates

The configuration screen models the launch before you sign, using constant-product pool math: total capital deployed, initial FDV, the share of supply your bundle captures, the average entry price of the bundled wallets, and what each wallet receives. Treat the output as a planning estimate. It excludes DEX fees, gas costs and the fact that post-launch buying can move the price further.

When a bundle launch is the right tool

Bundling is not a cheat code, and it is not appropriate for every token. It makes sense when:

• You are launching a token whose opening price is part of the product. If your pitch includes a chart, your opening chart is the first piece of evidence you produce.
• You are starting with genuine pool capital and want to protect the entry. Leaving the first buys to bots means the earliest holders are professionals who will sell into your community.
• You want a controlled initial distribution. Spreading the bundled allocation across many wallets with a per-wallet cap avoids a single address holding an obvious early block.
• You intend to lock or burn the LP immediately. The bundle can forward LP tokens straight into a locker, so the "unlocked liquidity" warning never has a window in which it is true.

It is the wrong tool when:

• Your bundle capital is your only capital. Buying your own token with money that would otherwise fund development is a bad trade, and it shows in the pool depth.
• You want a purely organic opening. Some communities prefer a naked liquidity add and will accept snipers as the cost. That is a valid preference; just do not bundle and then describe it as organic.
• You are bundling to create the appearance of demand you do not have. This is the line between launch mechanics and market manipulation, and the onchain record does not let you cross it quietly.

The economics, with numbers

The launch model works in pool shares rather than promises. Suppose you deploy 1,000,000,000 tokens, seed 20% of supply into a V2 pair against 50,000 USDC, and hold 5% of supply for the bundled buy.

Variable	Value
Total supply	1,000,000,000
Pool capital	50,000 USDC
Supply placed in pool	20% (200,000,000 tokens)
Implied opening price	$0.00025
Implied FDV at open	$250,000
Bundle capital	5,000 USDC
Bundle tokens received	~18,181,818 tokens (~1.8% of supply)
Bundle average entry	$0.000275

The bundled buys do not fill at the opening price. Every buy walks up the constant-product curve, so that same 5,000 USDC into a 50,000 USDC pool lifts the marginal price from $0.00025 to about $0.0003 — roughly a 20% move — and the bundle's average entry lands at $0.000275, a 10% premium to the open. That is the honest way to read the model: the difference between the opening price and your average entry is the cost of taking an allocation in the first block.

Two consequences follow. First, more bundle capital relative to pool capital means a worse average entry and a worse starting chart. Second, pool depth is the variable that does the most work: 50,000 USDC of liquidity absorbs a 5,000 USDC bundle gently, while 5,000 USDC of liquidity absorbs it violently.

Costs on top: the flat 50 USDC Arctools service fee, plus network gas. Arc's fee market enforces a 20 Gwei minimum maxFeePerGas, and below that the mempool drops your transaction silently. At the floor, 1,000 gas costs 0.00000002 USDC, so a 3,000,000-gas bundle transaction costs about 0.06 USDC. The fee mechanics are documented in Arc's gas and fees reference.

Disclosure: how to describe a bundle honestly

The mechanism is ordinary contract behaviour — many buys from one transaction is what a router does. What makes the difference between a fair launch and a bad one is whether you say what you did.

A disclosure that works looks like this:

Launch configuration: 1,000,000,000 supply, 20% seeded into a Uniswap V2 pool against 50,000 USDC at an opening FDV of $250,000. 5% of supply was purchased at launch by 40 wallets at an average entry of $0.000275. LP tokens are locked for 12 months at 0x…. Contract, transaction and lock are all on the Arc Explorer.

That paragraph gives a buyer everything: the price they are being asked to accept, the fact that you bought early, and the mechanism to verify all of it. What it does not do is pretend the bundling did not happen — and since the transaction is public, pretending would fail within minutes.

Three things to avoid:

• Describing a bundle as "fair launch." It is not one. Fair launches generally mean no early allocation at all.
• Bundling with wallets you later claim are unrelated buyers. Every bundled wallet is visible in one transaction. The claim is trivially falsifiable.
• Bundling and then unloading into your own community. The bundling is not the problem; selling the allocation into the buyers it attracted is.

Verifying a bundle launch as a buyer

If you are on the other side of one of these launches, the checks are mechanical:

1. Open the launch transaction on the Arc Explorer and count the recipients. A launch with 40 output transfers is a bundle.
2. Read the pool's reserves and compare the pool value to the bundled spend. A bundle larger than the pool is a chart waiting to reverse.
3. Check who holds the LP tokens. If they are not in a locker contract with a public unlock timestamp, the pool can be withdrawn at any moment — the single largest risk in any launch, bundling or not.
4. Run the contract through the Arc Token Checker to see whether supply, taxes and ownership can still be changed.
5. Watch the bundled wallets for a while. A bundle that holds is a launch strategy; a bundle that distributes into every rally is an exit plan.

Where bundling fits

A bundle launch is the answer to "how do I start with a price I chose rather than a price a bot chose". It is not a substitute for pool depth, a product, or disclosure. Pair it with the Arc Liquidity Locker so the pool is verifiably committed, and read the Arc Mainnet launch checklist for the full sequence before you deploy.

Arctools charges a flat 50 USDC per bundle launch, paid in USDC on Arc, and holds no tokens in your project. It is not affiliated with Circle or the Arc Foundation.