Transaction simulation: useful evidence with a state boundary

Solana's simulateTransaction RPC method evaluates a transaction against a selected state and returns information about that simulation. A wallet preview built from it is an aid to interpretation. The result should not be treated as proof that every later execution will have identical conditions.

Record the conditions Identify the transaction being simulated, the chosen commitment and relevant options. Check whether the final submitted request matches the previewed request. A substituted recipient or changed instruction is a different transaction, even when the interface retains the same confirmation screen.

Consider state changes Balances, account configuration and market conditions may change between preview and execution. The question is which assumptions the operation depends on and which constraints are enforced by the transaction itself. A minimum output condition is different from a projected output displayed only by the frontend.

Report the mismatch precisely For a finding, preserve the preview, final request and execution record. Explain whether the issue was a misleading display, a changed request or a state-dependent outcome. Keeping those categories separate helps identify the actual defect and prevents a useful simulation tool from being blamed for guarantees it never provided.