Reference
CLI reference
The sle binary ships as a single subcommand — simulate. Four flags cover every supported mode: devnet, mainnet, custom RPC, offline, human output, JSON output.
Invocation
sle --helpsle 0.1.0 Solana Transaction Legibility & Simulation Engine USAGE: sle <COMMAND> COMMANDS: simulate Simulate a base64-encoded versioned transaction and print a legibility report. help Print this message or the help of the given subcommand. OPTIONS: -V, --version Print version info -h, --help Print help
sle simulate
sle simulate --helpSimulate a base64-encoded versioned transaction and print a legibility report. USAGE: sle simulate [OPTIONS] --tx <BASE64> OPTIONS: --tx <BASE64> Base64-encoded serialized VersionedTransaction. Required. --rpc <ENDPOINT> RPC endpoint to use. Accepts one of the named aliases "devnet" or "mainnet" / "mainnet-beta", or any fully-qualified https:// URL. [default: devnet] --offline Skip RPC simulation entirely. Runs the decoder and classifier against the transaction's static structure only. No network access required. Useful for auditing a tx before it touches any RPC, and for programs that may not be deployed on the current cluster. --json Emit raw JSON (LegibilityReport) instead of the human-readable terminal format. Stable shape, safe to pipe into jq or downstream tooling. -h, --help Print help
Examples
Simulate against public devnet
devnet · human output$ sle simulate --tx "$BASE64_TX" --rpc devnet
Simulate against mainnet-beta
mainnet · human output$ sle simulate --tx "$BASE64_TX" --rpc mainnet
Offline — no network, structure-only
offline · human output$ sle simulate --tx "$BASE64_TX" --offline
Offline + JSON — pipeline mode
offline · json · jq$ sle simulate --tx "$BASE64_TX" --offline --json | jq '.overall_risk' "Critical" $ sle simulate --tx "$BASE64_TX" --offline --json \ | jq '.instructions[] | {program: .program_name, risk: .risk}'
Exit codes
| code | meaning |
|---|---|
| 0 | Report built successfully. The report may still contain a CRITICAL verdict — the exit code reflects only whether the pipeline itself succeeded. |
| 1 | Runtime error: base64 decode failure, bincode deserialize failure, or RPC error in non-offline mode. |
| 2 | Argument parsing error (missing --tx, invalid flag combination, etc.). Emitted by clap. |