Rpc chat

This is a list of the monero-wallet-rpc rpc chat, their inputs and outputs, and examples of each. The program monero-wallet-rpc replaced the rpc interface that was in simplewallet and then monero-wallet-cli. All monero-wallet-rpc methods use the same JSON RPC interface. Note: “atomic units” refer to the smallest fraction of 1 XMR according to the monerod implementation.

The total balance of the current monero-wallet-rpc in session. Unlocked funds are those funds that are sufficiently deep enough in the Monero blockchain to be considered safe to spend. The 95-character hex address string of the monero-wallet-rpc in session. Returns the wallet’s current block height. The current monero-wallet-rpc’s blockchain height. If the wallet has been offline for a long time, it may need to catch up with the daemon. Send monero to a number of recipients.

Amount to send to each destination, in atomic units. Ignored, will be automatically calculated. 64-character hex string to identify a transaction. Return the transaction key after sending. Set a priority for the transaction. Accepted Values are: 0-3 for: default, unimportant, normal, elevated, priority.

If true, the newly created transaction will not be relayed to the monero network. Integer value of the fee charged for the txn. String for the transaction key if get_tx_key is true, otherwise, blank string. Same as transfer, but can split into more than one tx if necessary. Return the transaction keys after sending. Set a priority for the transactions. True to use the new transaction construction algorithm, defaults to false.

The amount of fees paid for every transaction. The tx hashes of every transaction. The tx as hex string for every transaction. The amount transferred for every transaction. The transaction keys for every transaction.

Send all unlocked balance to an address. Get a list of incoming payments using a given payment id. Get a list of incoming payments using a given payment id, or a list of payments ids, from a given height. Either is fine for looking up transactions by a single payment ID. The block height at which to start looking for payments.

Returns a list of transfers. Return a list of incoming transfers to the wallet. OR “unavailable”: only transfers which are already spent. Mostly internal use, can be ignored by most users.

Several incoming transfers may share the same hash if they were in the same transaction. Return the spend or view private key. The view key will be hex encoded, while the mnemonic will be a string of words. Make an integrated address from the wallet address and a payment id. Retrieve the standard address and payment id corresponding to an integrated address. Stops the wallet, storing the current state.

Create a payment URI using the official URI spec. Parse a payment URI to get payment information. Testing out the make_uri function. Set arbitrary string notes for transactions. Get string notes for transactions. Verify a signature on a string. Export a signed set of key images.