Skip to content

wallet-cli-4.9.6

Choose a tag to compare

View all tags
@lvs0075 lvs0075 released this 01 Jun 03:25
wallet-cli-4.9.6
c9233c1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Notice

Non-mandatory upgrade

New Features

Change

  1. Add --password-stdin to standard CLI for piped master-password input, enabling credential helpers and secret managers (e.g. op read, echo "$pw" | wallet-cli --password-stdin ...) without exporting MASTER_PASSWORD. The flag takes precedence over the env var, reads stdin once with trailing newline stripping, and rejects interactive TTY use without a pipe. (#931)

  2. Add standard CLI Ledger signing for wallet-authenticated commands when the selected wallet is a Ledger keystore: unlock via MASTER_PASSWORD / --password-stdin, sign on-device using the stored BIP44 path (one-time pairing still via REPL importwalletbyledger), suppress legacy Ledger stdout so JSON output stays machine-readable, emit a single stderr confirmation prompt, and return structured ledger_* error codes (ledger_not_connected, ledger_app_not_open, ledger_sign_by_hash_disabled, ledger_unsupported_contract, ledger_already_signing, ledger_user_rejected, ledger_timeout, ledger_sign_failed). (#931)

  3. Add address book alias support to standard CLI: per-network user aliases in Wallet/aliases/<network>.json, built-in network token aliases (e.g. USDT/USDC/USDD/WTRX on mainnet), and commands alias-add, alias-remove, alias-list, and alias-resolve for ACCOUNT and TOKEN entries. Account-position options resolve account aliases; contract/token-position options resolve token aliases; raw Base58Check and hex addresses still work directly. Alias hits are auditable via stderr resolution lines in text mode and meta.resolved in JSON mode; built-in names cannot be overridden. (#931)

Integrity Check

All jar files available in this release are signed via this GPG key:

From the download listings below you should see links to the downloadable jar files as well as sig signature files. To verify the authenticity of any jar file, grab the jar and sig files with the same prefix name and then execute the verification process: GPG signature verification

Assets 4
Loading