monero-wallet-cli - Reference¶
Get yourself comfortable with a friendly Monero CLI wallet. It is the most reliable and most complete wallet for Monero. Use stagenet for learning.
Command line wallet¶
The "official" command line wallet for Monero. Available for Linux, macOS and Windows.
Wallet uses your private keys to understand your total balance, transactions history, and to facilitate creating transactions.
However, wallet does not store the blockchain and does not directly participate in the p2p network.
The CLI wallet is the most reliable and most feature complete wallet for Monero.
Depends on the full node¶
Wallet connects to a full node to scan the blockchain for your transaction outputs and to send your transactions out to the network.
The full node can be either local (same computer) or remote.
Normally, you run the full node on the same computer as wallet (or within your home network).
Connection happens over HTTP and uses this API.
Any transaction leaving the wallet is already blinded by all Monero privacy features. This means plain text HTTP communication isn't an issue on its own even if you connect to a remote node.
However, connecting to a remote node has other nuanced trade-offs, which is a topic for a separate article.
./monero-wallet-cli [options] [command]
Go to directory where you unpacked Monero.
Run the full node and wait until it syncs up with the network (may take up to a few days):
In a separate terminal window, run the wallet:
./monero-wallet-cli --stagenet --generate-new-wallet MoneroExampleStagenetWallet
Help and version¶
| ||Enlist available options.|
| ||Show |
|(missing)||By default wallet assumes mainnet.|
| ||Run on stagenet. Remember to run your daemon with |
| ||Run on testnet. Remember to run your daemon with |
| ||Full path to the log file.|
| || |
| ||Soft limit in bytes for the log file (=104850000 by default, which is just under 100MB). Once log file grows past that limit, monero creates the next log file with a UTC timestamp postfix |
In production deployments, you would probably prefer to use established solutions like logrotate instead. In that case, set
| ||Limit on the number of log files (=50 by default). The oldest log files are removed. In production deployments, you would probably prefer to use established solutions like logrotate instead.|
Full node connection¶
Wallet depends on a full node for all non-local operations. The following options define how to connect to
| ||Use |
| ||Use |
| ||Use |
| ||Specify |
| ||Enable commands and behaviors which rely on |
| ||Disable commands and behaviors which rely on |
| ||The newly created transaction will not be relayed to the Monero network. Instead it will be dumped to a file in a raw hexadecimal format. Useful if you want to push the transaction through a gateway like https://xmrchain.net/rawtx. This may be easier to use over Tor than Monero wallet.|
| ||Allow communicating with |
Create new wallet¶
| ||Create a new Monero wallet and save it to |
| ||Concerns encrypting the wallet file. The wallet file is encrypted with ChaCha stream cipher. The encryption key is derived from the user supplied password by hashing the password with CryptoNight. This option defines how many times the CryptoNight hashing will be applied. The default is |
Note this is unrelated to spend key generation.
The more rounds the longer you will wait to open the wallet or send transaction. But also the attacker will have it harder to brute force your wallet password.
Note: You will have to remember and provide the same
Recommendation: Do not change the default value. Instead generate a very strong wallet password with your password manager (256 bits of entropy).
Open existing wallet¶
| ||Open existing wallet. Example: |
This is only for wallet files generated with
| ||Provide wallet password as a parameter instead of interactively. Remember to escape/quote as needed. |
Not recommended because the password will remain in your command history and will also be visible in the process table. For automation prefer
The option also works in combination with
| ||Provide password as a file in stead of interactively. Trailing |
Prefer this over
The option also works in combination with
| ||Restore/generate a special wallet to work with a hardware device like Ledger or Trezor and save it to |
This is a one-time action. Next time you simply open the wallet.
By default the command expects Ledger hardware connected. For Trezor hardware add
It will take up to 25 minutes with default settings. This is because hardware devices are slow to pre-generate subaddresses. To mitigate use low
The local wallet will not have private spend key and will not be able to spend on its own. It serves as a user interface and a bridge for low-power hardware devices. Transaction signing with a private spend key always happens on the hardware device.
See the complete guide to hardware wallet setup.
| ||Restore a view-only version of the wallet to track incoming transactions and save it to |
| ||Restore a wallet from secret spend key and save it to |
| ||Restore a wallet from secret mnemonic seed. Use this to restore from your 25 words backup. |
You will be asked for a password to encrypt the wallet file (once restored). Note this is not a passphrase to mnemonic seed. Mnemonic seeds generated by Monero official wallets are naked.
| ||Only scan for transactions later than specific blockchain height. The default is |
| ||Create a standard wallet from multisig keys. This is useful to combine all multisig secret keys back into the standard wallet (when you no longer need the multisig). The wallet will then have control of the funds. It only supports providing all secret keys even if the multisig scheme allowed for less (only |
| ||Restore a multisig wallet from secret seed that was earlier exported with the |
| ||Full path to the configuration file. Note this should be a separate config than |
| ||Accepts |
The wallet will not check for payments to subaddresses further than
On the other hand the more subaddresses you set to look ahead, the longer it takes to create your wallet, because they must be pre-computed. This is normally not a concern, except for hardware wallets. On the Ledger the default value of
| ||Max number of threads to use for parallel jobs. The default value |
| ||Language for mnemonic seed words. One of |
It might be a good idea to stick to default English which is by far the most popular and well tested. It also avoids potential non-ASCII characters pitfalls or bugs.
| ||If your display freezes, exit blind with ^C, then run again with |
These options are either legacy or rarely useful.
| ||Generate legacy non-deterministic wallet. The view key will not be derived from the spend key. You would also have to backup the .keys. To restore non-deterministic wallet (standard address) use |
| ||Restore legacy non-deterministic wallet by providing both spend and view keys and the standard address.|
| ||Set shared ring database path. No longer worthwhile.|
| ||Has no effect. The |
| ||Provide mnemonic seed as a commandline option for |
| ||You would run |
| ||You would run |
Wallet files are created and seek in current directory. This is rarely what you want. Use
--wallet-file and similar options to control this.
Log files are created in the same directory as
monero-wallet-cli binary. Use
--log-file to specify the location.
Commands are used interactively in the
You can also run a one-off command by providing it as a commandline parameter. This is rarely useful though. For automation prefer
The CLI wallet has built-in help for individual commands - we will not attempt to reproduce that. Instead we focus on grouping commands so you can quickly find what you are looking for. Use
help command_name to learn more.
Help and version¶
help - list all commands
help command_name - show help for individual command
version - show version of the monero-wallet-cli binary
status - show if synced up to the blockchain height
fee - show current fee-per-byte and full node's mempool (the backlog of transactions depending on the priority)
wallet_info - show wallet file path, standard address, type and network
account - total balance; list accounts with respective balances
balance detail - within the current account, list addresses with respective balances
refresh - force refresh the balance and transactions by pulling latest blocks from the full node; this is often useful because auto-refresh only kicks in once in 90 seconds
show_transfers - show all transactions on the current account; optionally provide a filter:
coinbase; optionally provide subaddress index for output selection
show_transfer <txid> - show details of specific transaction
incoming_transfers [available|unavailable] [verbose] [index=<N1>[,<N2>[,...]]] - show the incoming transactions, all or filtered by availability and address index within current account; this will only show confirmed transactions; you will not see transactions awaiting in the mempool
get_tx_note <txid> - get a string note for transaction id
Keys and Passwords¶
Secret mnemonic seed¶
seed - show raw mnemonic seed
encrypted_seed - create mnemonic seed encrypted with the passphrase; you will need to remember or store the passphrase separately; restoring will not be possible without the passphrase
spendkey - show secret spend key and public spend key
viewkey - show secret view key and public view key
password - change wallet password; this password is used to encrypt the local wallet files; it does not change secret keys or backups
check_reserve_proof - prove the balance
check_spend_proof - prove you made the payment
sign <file> ->
verify <filename> <address> <signature> - prove ownership of the address; allows to verify the file was signed by the owner of specific Monero address
hw_reconnect - attempts to reconnect HW wallet
unspent_outputs - show a list of, and a histogram of unspent outputs (indivisible pieces of your total balance)
export_outputs <file> ->
import_outputs <file> - helps with cold spending; export outputs from a view-wallet to the cold-wallet to make it aware of what had been sent to it
mark_output_spent <amount>/<offset> | <filename> [add]
export_key_images <file> ->
import_key_images <file> - used to inform the view-only wallet about outgoing transactions so it can calculate the real balance; normally view-only wallets only learn about incoming transactions, not outgoing
Tx private key¶
These allow to learn and verify transaction's private key
r. This was useful to create a proof of payment but got superseded by
check_tx_key <txid> <txkey> <address>
set_tx_key <txid> <tx_key>
rescan_spent - rescan the blockchain for spent outputs; sometimes, the wallet's idea of what outputs are spent and what outputs are not get out of sync with the blockchain. This can happen if you exit the wallet without saving after sending a tx, or if it crashes. This will look for the key images on the blockchain to make sure it's up to date.
donate <amount> - donate
<amount> to development team
address_book [(add ((<address> [pid <id>])|<integrated address>) [<description possibly with whitespaces>])|(delete <index>)]
set_description [free text note] ->
get_description - manage convenience description of the wallet (the information is local)
save - this now happens automatically
save_bc - this now happens automatically
bc_height - show blockchain height (superseded with
sweep_unmixable - only relevant for very old wallets (<= 2016); send all unmixable outputs to yourself with ring_size 10
locked_sweep_all - see
rescan_bc - rescan the blockchain from scratch, losing any information which can not be recovered from the blockchain itself
TODO: document remaining commands