Simulate and execute

What simulation is

Simulation builds the real bundle. The same create instruction, the same buys in the same order, the same protection rules, checked against the state the chain is in right now. The only thing it does not do is send it.

Because nothing is signed, nothing can go wrong by running it. Run it after every change you make. Run it again a minute later if you have been sitting on the screen, because chain state moves and a result from ten minutes ago is describing a chain that no longer exists.

What the pre-flight checks

• BalancesWhether every funded wallet holds enough for its buy, its share of the fees, and the rent its new accounts will need. This is the most common thing to fail, and the easiest to fix.
• AssemblyWhether the instructions pack into valid transactions and the transactions order into a valid bundle. A launch too large for the packing shows up here rather than at execution.
• FillsWhat each wallet would actually receive against current state, rather than what you asked for. These are not the same number, and the difference is the point of reading the result.
• Price impactHow far your own buys move the price as they execute in sequence. The last wallet in the order pays the most, always.
• SlippageWhether any buy would fill outside the tolerance you set. A buy that would exceed it is flagged before it can fail live.
• Authorities and metadataWhether the create instruction carries the supply, decimals, revocations and metadata you configured. The last chance to catch a typo in something permanent.
• Protection rulesWhether the routing and gate configuration you chose is applied to the bundle being built.

Reading the result

Green is not the same as good

A simulation that passes means the launch would execute. It does not mean the launch is the one you wanted. Read the fills before you read the verdict, because a bundle that lands perfectly while giving your last five wallets almost nothing is a technical success and a practical failure.

The three things to look at

• The spread of fillsCompare the first wallet in the order against the last. If the gap is larger than you expected, your total buy is too large for the liquidity, or your ordering needs changing.
• The total spent against the total you plannedRandomised amounts move this. If it has drifted further than you are comfortable with, narrow the band.
• Anything flaggedA flag is not an opinion. It is the pre-flight saying this specific thing would fail. Fix it and run again rather than executing to see what happens.

What happens when you execute

1. 01

   The cost breakdown appears

   Platform fee, base fee, priority fee and bundle tip, each shown separately, with the total. This is the last screen before a signature is requested.

2. 02

   You sign

   Your wallet opens and asks for approval. Nothing has been sent yet, and declining here costs nothing.

3. 03

   The bundle is submitted

   The assembled bundle goes to the block engine rather than the public path.

4. 04

   The feed reports

   Each stage appears as it happens: assembled, protection applied, submitted, received, landed. If a stage does not report, that is where to look.

5. 05

   The slot confirms

   The launch is complete when the block containing the bundle is confirmed on chain. Nothing before that point is final.

After execution

If it landed

The mint exists, the buys filled, and the record is on chain. Check the fills against what the simulation predicted. They will not match exactly, because the chain moved between the two, and a large divergence is worth understanding before your next launch.

If it did not

Nothing was applied. A bundle does not half execute, so there is no cleanup to do and no half made token to abandon. The fees for a failed attempt are not free, but the position is unchanged. Read the feed, find the stage that did not report, and take it to the troubleshooting page.