Transaction builder
Simulation and planning
Simulation tests a plan on Solana RPC before anything is signed. It tells you whether the network would accept the transaction.
What simulation does
The plan is sent to Solana RPC as a dry-run. The signature is not verified and the blockhash is replaced by the network, so no wallet signature is needed and nothing is broadcast.
Only attempts that passed Verify are simulated. Transfers can be simulated today.
Before you run it
The dry-run needs a few things to be in place.
- A connected wallet on Devnet with a little SOL for fees.
- A configured token mint in NEXT_PUBLIC_TOKEN_MINT (run pnpm mint:setup).
- A token account for that mint in the connected wallet.
Outcomes
A simulation always ends in one of four outcomes.
- Passed: the network says the transaction would succeed. The compute units used are shown.
- Failed: the network rejected it. This is a valid answer, not an application error.
- Unsupported: simulation cannot run for this case, for example a swap or a missing mint setting.
- Error: the RPC could not be reached, timed out or rate limited. Try again.
Failure reasons
When a dry-run fails, FYAT explains why in plain language.
- Mint not found on this network.
- The wallet has no token account for this mint yet.
- Not enough tokens for the transfer.
- Not enough SOL for fees or for the recipient's token account.
- Any other rejection, with the program logs attached.
Program logs
Logs come from outside the application, so FYAT treats them as untrusted. Only the last 12 lines are kept, each is cut to 200 characters, and they are always rendered as plain text.
Each RPC call times out after 15 seconds.