wallet-cli tx

Build, send, broadcast, co-sign, and inspect transactions.

Synopsis

wallet-cli tx COMMAND

Subcommands

Command	Description	Networks
tx send	Send the native coin or a token with human --amount	TRON, EVM
tx broadcast	Broadcast a presigned transaction	TRON, EVM
tx status	Show confirmation status of a transaction	TRON, EVM
tx info	Show full transaction detail + receipt	TRON, EVM
tx sign	Sign a transaction built elsewhere	TRON, EVM
tx approvals	Show collected signatures on a multi-sig transaction	TRON only
tx multisig	Multi-sig collaboration via the TronLink service (list / create / co-sign / watch)	TRON only

The transaction hex these commands exchange is protocol.Transaction protobuf on TRON and RLP (0x02…) on EVM. Fee flags differ by family too — --fee-limit / --permission-id / --expiration on TRON, --gas-limit / --max-fee / --priority-fee / --nonce on EVM — and each set is refused on the other family with invalid_option.

The transaction lifecycle

build ──sign──> submit ──receipt──> confirmed
  │                │                     │
  └ --dry-run      └ default return      └ tx status: confirmed/failed
    stops here       point ("submitted")   (pending/not_found while in flight)

tx send covers build+sign+submit in one step (with --dry-run / --sign-only stopping earlier); tx broadcast submits what was signed elsewhere; tx status / tx info observe the outcome. confirmed means included and receipted, not finalized. Submission is not confirmation — scripts must follow machine-interface → Script safety.

Multi-sig co-signing

TRON only. An EVM transaction carries exactly one signature, so there is no threshold to reach and no co-signing path; tx sign there simply signs, and tx approvals / tx multisig are not bound to EVM at all.

For TRON accounts that require more than one signature, there are two co-signing paths:

• On-chain — tx sign / tx approvals / tx broadcast: the initiator produces a partially signed hex with --sign-only, each signer appends theirs with tx sign (passing the hex along), and once the threshold is reached anyone broadcasts it. Self-sufficient, no service needed.
• Service — tx multisig: the TronLink multi-sig service holds the transaction, accumulates signatures, and pushes notifications. Opening a collection is the initiator's own first signature, and the service broadcasts once the threshold is met. Optional convenience layer; needs credentials.

Either way, tx approvals answers "is it ready yet?", and tx broadcast refuses to submit a transaction that has not reached its threshold — an incomplete collection never reaches the node.

See permission for the account permission structure that co-signing is built on.

See also

account history · Networks & fees · Scripting guide

---