Skip to main content
Use thru-cli txn when you need to build or inspect transactions directly instead of using a higher-level command family.

Commands

CommandUse it for
signBuild and sign a transaction, then emit it as base64.
executeBuild, sign, and submit a transaction directly.
make-state-proofGenerate a cryptographic state proof for an account.
getFetch transaction details by signature.
sortSort public keys for transaction account lists.

Important Inputs

  • program
  • instruction_data
  • optional fee/resource fields such as fee, compute_units, state_units, and memory_units
  • ordered --readwrite-accounts and --readonly-accounts

Minimal Patterns

thru-cli txn sign ta...[program] deadbeef
thru-cli txn get ts...[signature] --retry-count 5

Notes

  • Use this family when you already know the raw instruction data and account list you need.
  • Use a higher-level family like token, program, or registrar when it already wraps the transaction-building logic for your task.