CLI › Guides › Devnet Burner

Devnet Burner Quickstart

The fastest way to try the ATF CLI. Switch to devnet, run a simulation, verify the receipt, and send a transaction. All on devnet, fully safe.

Prerequisites

doctor passes with no errors.
An active profile (the default profile works fine for this guide).
Internet access for devnet RPC calls.

Step-by-Step

Run each step directly with npx. No install needed.

First time setup

1. Create a devnet burner profile

Use a separate profile for burner testing so your production config stays clean.

Create burner profile

npx @trucore/atf@1.5.1 profile create devnet-burner --network devnet

2. Select the profile

Switch to the burner profile before enabling burner mode.

Select profile

npx @trucore/atf@1.5.1 profile select devnet-burner

3. Enable burner mode

The burner command switches the active profile to devnet for safe testing. Do not send real funds to devnet addresses.

Enable burner

npx @trucore/atf@1.5.1 burner enable

{
  "ok": true,
  "burner_enabled": true,
  "profile": "devnet-burner",
  "solana_cluster": "devnet",
  "message": "Burner mode enabled on profile \"devnet-burner\" (cluster: devnet)."
}

4. Verify setup

Run doctor to confirm the profile, network, and RPC are configured correctly.

Verify

npx @trucore/atf@1.5.1 doctor --pretty

5. Ping the RPC to confirm connectivity

Ping RPC

npx @trucore/atf@1.5.1 rpc ping

Endpoint: https://api.devnet.solana.com
Latency: 68ms
Status: reachable
Network: devnet

6. Simulate a small swap

Use the swap_small preset to run a quick simulation. Include --verify to enable local receipt verification.

Simulate

npx @trucore/atf@1.5.1 simulate --preset swap_small --verify

Decision: ALLOWED
Request ID: req_burner_001
Content hash (server):  0x9e2f...d4a7
Content hash (local):   0x9e2f...d4a7
Status: Integrity verified

7. Verify the receipt separately (optional)

If you want to double-check, verify the receipt as a standalone step.

Verify receipt

npx @trucore/atf@1.5.1 receipts verify --receipt last

8. Sign and send the transaction

On devnet, you can safely sign and send. The burner wallet is disposable, so there is no risk.

Send transaction

npx @trucore/atf@1.5.1 tx send --receipt last

Transaction submitted.
Signature: 3mVx...pQ8r
Network: devnet

9. Check the transaction status

Check status

npx @trucore/atf@1.5.1 tx status --sig 3mVx...pQ8r

Transaction: 3mVx...pQ8r
Status: confirmed
Confirmations: 31
Slot: 284,291,088
Block time: 2026-02-27T19:15:33Z

Use Again Later

If you have already created the devnet-burner profile, skip straight to these commands on repeat runs.

1. Select the profile

npx @trucore/atf@1.5.1 profile select devnet-burner

2. Enable burner mode

npx @trucore/atf@1.5.1 burner enable

3. Verify if needed

npx @trucore/atf@1.5.1 doctor --pretty

Already created this profile?

If you see Profile "devnet-burner" already exists., skip profile creation and use the commands above.

Burner Wallet Lifecycle

The burner wallet exists only in the profile config on your machine. It is not stored server-side. When you delete the profile or generate a new burner, the old wallet is gone. Treat it as fully disposable.

Receipts from burner sessions are still valid and verifiable. You can re-verify them at any time using receipts verify, even after the burner wallet has been discarded.

Troubleshooting

Symptom	Likely cause	Fix
Profile "devnet-burner" already exists.	The profile was created on a previous run.	Skip `profile create` and run `profile select devnet-burner` instead.
Burner command fails	Profile issues or network flag missing.	Pass `--network devnet` explicitly.
Simulation blocked	Policy limits exceeded for the preset.	Try a smaller preset or adjust parameters.
Send fails with insufficient balance	Burner wallet has no SOL.	Fund the wallet via devnet faucet or manual transfer.