From 98b316771a6626228cf286fead8dc19ab874dc04 Mon Sep 17 00:00:00 2001 From: Duke Leto Date: Sun, 5 Jun 2022 14:49:58 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1556d0d..fe6896d 100644 --- a/README.md +++ b/README.md @@ -64,7 +64,7 @@ consolidation=1 * It's possible that many users request a withdraw within a few seconds of each other which will spike CPU usage and potentially trigger bugs * Hush 3.9.1 should be less likely to have these bugs * It's a good idea to not let too many ztx's that spend funds from the same zaddr be queued at once. - * So it's good to check the output of z_getoperationstatus before queuing a new ztx + * So it's good to check the output of [z_getoperationstatus](https://faq.hush.is/rpc/z_getoperationstatus.html) before queuing a new ztx * If there are 3 or more existing ztx's in the state of "executing", do not add more * Wait until there are 2 or less ztx's in the "executing" state to add more to the queue * To detect users that are mining to your exchange: