The result you are building

Finished Result:

An execution record and policy that separates base fee, compute-unit limit/price, tips or route fees, slippage and price impact, simulation, inclusion latency, failures, and realized output, then selects bounded fees from transaction value and measured conditions.

Use this guide when

Swaps or bot transactions land late, fail, or cost more than expected.
Priority fee or Jito-style tips appear to erase profit.
You need to compare routes and fee policies under congestion.

Do not use it as a substitute for

Trying to bypass mandatory protocol/network fees or assuming higher tip guarantees profitable execution.
Raising slippage and priority together without measuring whether the trade still has positive after-cost value.

Before you change anything

Collect these items first. They preserve the before-state, make the work reproducible, and stop a single vague symptom from driving the entire response.

Cluster, slot/time, RPC/send path, transaction version, blockhash, signatures, and route.
Simulation logs, compute units consumed, requested limit, micro-lamports per CU, base fee, tips, platform fees, and rent.
Decision quote/time, minimum output, route pools, price impact, actual balances/fills, and confirmation time.
Dropped/expired/simulation/program/account/slippage/compute/RPC failures and retries.
Market value/edge, position size, fee/slippage caps, duplicate protection, and reconciliation.

Stop Before Proceeding:

Stop submission or retry when the signature may have landed, quote/blockhash is stale, worst-case fee plus slippage removes the expected edge, or the transaction exceeds the declared maximum loss/cost.

Understand the system before fixing it

On-chain evidence outranks the interface Wallets and dashboards can be stale, partial, or misleading. Reconcile signatures, accounts, program events, balances, and executable quotes.

Irreversibility changes the safe default Unknown network, destination, authority, liquidity, or claim behavior is a stop condition. Use low-value tests and explicit maximum loss.

Priority pays for scheduling, not economic success Inclusion can improve while price moves against you, route fails, token is unsellable, or fee exceeds the trade's expected value.

Compute limit and compute price interact Priority fee depends on requested/charged mechanics and transaction construction. Overstated limits or blind estimates can increase cost or still fail if instructions change.

Evidence-to-decision map

Start with the row that most closely matches the evidence. The first test isolates a layer; it is not permission to
make every available change.

   Evidence               Likely layer    First decisive check           What the result means

   Fee high, inclusion    Send path/con   Compare leader timing, RPC     Payment alone cannot fix late propagation or stale transaction.
   still slow             gestion         propagation, fee market, and
                                          blockhash age

   Simulation passes,     Market          Compare simulated and          State changed between quote, simulation, and inclusion.
   chain fails slippage   movement        executed slot/quote/reserves

   Compute exceeded       Transaction     Read consumed CU and first     Limit too low or route/account/instruction changed.
                          construction    failing instruction

   Bot green gross,       Execution       Reconcile actual balances,     Costs and failed submissions erase gross edge.
   wallet down            accounting      every fee, failed attempts,
                                          slippage, and inventory

   Retry creates          Ambiguous       Check signature, intent key,   Client timeout was mistaken for non-commit.
   duplicate swap         outcome         and balance deltas before
                                          rebuilding

Step-by-step procedure

Work in order and retain the output from each step. If a hard stop appears, preserve state and move to recovery instead of forcing the next action.

01 Define the economic execution budget Why: A precise boundary prevents a plausible fix from solving the wrong problem.

Do: For each trade/action, set expected value, size, maximum total fee, slippage/impact, latency, failure allowance, and loss. Refuse when no after-cost margin exists.

Read the result: Worst-case authorized execution remains inside the trade's value/risk boundary.