From 87422d9c08cfbe16c83c4b3a5c1319da08a21739 Mon Sep 17 00:00:00 2001 From: Duke Leto Date: Sun, 5 Jun 2022 14:37:44 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index be1a0f5..5266683 100644 --- a/README.md +++ b/README.md @@ -82,7 +82,8 @@ consolidation=1 * This means you do not need to hardcode a zaddr in the "from" part of a z_sendmany and/or move funds around from various zaddrs * To use this feature, use a single lowercase "z" as the "from" in z_sendmany, such as: `z_sendmany "z" ...` * When using this, funds will be spent from any zaddr that has enough funds - * Note that a single zaddr must have enough funds to make the transaction, funds from multiple zaddrs cannot be used. + * Note that to use `z_sendmany` a single zaddr must have enough funds to make the transaction, funds from multiple zaddrs cannot be used. `z_mergetoaddress` can be used to spend funds from multiple zaddrs at one time. + * Sometimes there are unconfirmed transactions waiting to be relayed to the network. The wallet will resend them periodically but this can be forced with the [https://faq.hush.is/rpc/resendwallettransactions.html](resendwallettransactions) RPC # How Shielded Addresses (zaddrs) Are Different