monero-wallet-cli commands, and this document goes through all the Oxen and Monero CLI commands available within oxen-wallet-cli.oxen-wallet-cli has multiple commands to conduct different operations on the Oxen Blockchain. Typing help and pressing Enter after loading your wallet will bring up the commands that can be used.Primary account with index 0. If at any time you wish to create an additional account use the command:exit to save your session.Note: Restoring your wallet from your seed will not restore your accounts as the index of your subaddress data is stored on your computer within your wallet file. All the funds stored in your additional accounts will be shown in your Primary account if you need to restore your wallet from scratch.
<index> with the index number associated with the account you wish to relabel, and replacing <label text with white spaces allowed> with the new label you would like to name the specified account.account label 0 My Account we have changed the label connected to our Primary address from “Primary account” to “My Account”.oxen-wallet-cli allows you to group accounts by tagging or untagging them.balance or balance detailbalance will generated a simple output showing your balance and unlocked balance of the specific account you are in. For example:balance detail will generate a more detailed output, showing the account number, first few characters of the address, balance, unlocked balance, Outputs and the Label of the account. For example:account command.4f4b371a0da8858bbeab8a40ff37de1f6ff33e64a616e5ced8239062570b7542 is known to be fake and if this txid is seen within a RingCT transaction the network can assume it is fake, therefore an actor has a better chance of deducing the real transaction within the RingCT.get_reserve_proof command to generate our proof.(all|<amount>) with a 1000, otherwise replace it with the amount you need to prove you have reserved. If you want to put an extra layer of encryption over the file replace [<message>] with a password.oxen_reserve_proof will be saved in your Oxen folder, where your daemon and wallet keys are. Keep in mind every time you run the get_reserve_proof command it will overwrite youroxen_reserve_proof file.oxen_reserve_proof file through https://transfer.sh/ by running the command within the folder of your signature file:<message> if you encrypted the file.oxen_reserve_proof file in our Oxen folder.oxen_reserve_proof file in your Oxen folder request the individual sending the file to you to use https://transfer.sh/, once they send you the link to their oxen_reserve_proof you can use the following command to download it.<link> with the link to download the oxen_reserve_proof.oxen_reserve_proof is in our folder we can run the following command:<address> is the address of the wallet where the command get_reserve_proof was ran. <signature_file> is the file that was received from the individual sending you the reserve proof, normally generated as oxen_reserve_proof and <message> is the key set by the individual who sent you the reserve proof.get_spend_proof command.get_spend_proof command to generate our proof.<txid> with the txid of our transfer out and replacing <message> if we want to add a password to the proof. If all went well the terminal will output the following text:oxen_spend_proof will be saved in your Oxen folder, where your daemon and wallet keys are. Keep in mind every time you run the get_spend_proof command it will overwrite your oxen_spend_proof file.oxen_spend_proof file through the transfer.sh link.<message> if you encrypted the file.oxen_spend_proof file in our Oxen folder and the txid associated with the transaction being proved.oxen_spend_proof file in your Oxen folder request the individual sending the file to you to use https://transfer.sh/, once they send you the link to their oxen_spend_proof you can use the following command to download it.<link> with the link to download the oxen_spend_proof.oxen_spend_proof is in our folder we can run the following command:<txid> is the txid associated with the transaction that is being proved. <signature_file> is the file that was received from the individual sending you the spend proof, normally generated as oxen_spend_proof and <message> is the key set by the individual who sent you the spend proof.Good signature message that should be a good proof that the txid you are checking was generated from the sender. Keep in mind however that this can potentially not always be the case, considering someone could get access to someone else's computer thus having access to this file.get_tx_proof command to generate our proof.<txid> with the txid of our transfer out, <address> with the receiver's address, and replacing <message> if we want to add a password to the proof. If all went well the terminal will output the following text:oxen_tx_proof will be saved in your Oxen folder, where your daemon and wallet keys are. Keep in mind every time you run the get_tx_proof command it will overwrite your oxen_tx_proof file.oxen_tx_proof file through https://transfer.sh/ by running the command within the folder of your signature file:oxen_tx_proof file through the transfer.sh link.<message> if you encrypted the file.oxen_tx_proof file in our Oxen folder, the receiver's address and the txid associated with the transaction being proved.oxen_tx_proof file in your Oxen folder request the individual sending the file to you to use https://transfer.sh/, once they send you the link to their oxen_tx_proof you can use the following command to download it.<link> with the link to download the oxen_tx_proof.oxen_tx_proof is in our folder we can run the following command:<txid> is the txid associated with the transaction that is being proved, <address> is the receiver’s address and <signature_file> is the file that was received from the individual sending you the tx proof, normally generated as oxen_tx_proof and <message> is the key set by the individual who sent you the tx proof.Good signature message that should be a good proof that the txid you are checking was generated from the sender. Keep in mind however that this can potentially not always be the case, considering someone could get access to someone else's computer thus having access to this file.<txid> is the transaction id associated with the transfer out you are proving is yours.<tx key> with the <txid> and <receiving address> to the individual who will run the validation, thus this will prove you generated the transaction.<tx key>, <txid> and <receiving address> from a specific transaction we can use the following command to prove they are all associated:oxen-wallet-cli allows you to add notes to specific txid’s, however this note does not get stored on the blockchain, rather it is stored on client side, on the device that generates the tx_note.<txid> and the <message> you want to add to the txid. For instance, if you want to add a note to a txid that is connected to your wallet run the following command to show your transactions in/out with their <txid>’s:<txid> run the following command:<txid> is the transaction id associated to the transaction you are adding the [free text note] too. Your command will look similar to the following example:<txid> is the transaction id that has the note connected to it. For example, if we run the command on the previous <txid> mentioned, the terminal will display the following text:show_transfers command, each transaction that has a note connected to it will display the text to the right of each transfer.Passwords do not match! Please try again or Error: invalid password.encrypted_seed allows your to add an additional password, or encryption layer, to your 25 word mnemonic seed. Encrypting your seed will stop others from recovering access to your wallet if they somehow gain access to your 25 word mnemonic seed as they will not have the passphrase that decrypts them. This means, your passphrase should not be written or saved in the same location as your encrypted 25 word mnemonic seed phrase.