joinmarket-clientserver
joinmarket-clientserver copied to clipboard
JoinMarket-Org
Tumbler Error: NotEnoughFundsException / Advanced options in JM schedule generator
I am using the Joinmarket Qt on the RaspiBlitz.
I have tried several times to run the tumbler (Coinjoin/Multiple Join) and always got the following behavior, which in my opinion could indicate a problematic setting in the script.
In the schedule generator advanced options the "Min coinjoin amount" has the default value of 1.000.000. As it was suggested in the docs I did not change this or any other of the defaults. The following tumbler run aborted with the error message: "Unable to select sufficient coins: NotEnoughFundsException('Not enough funds.106XXXX vs. 104XXX.')"
During the process to come around this issue I reduced the Min cj amount in future runs to 100.000. But still then at some point the same error occurred.
It seems to me that the parameter "Min coinjoin amount" is not checked by the script, if it makes sense in relation to the funds, contained in the different mix depths of the wallet.
I had one case where the starting values of the wallet were:
md 0: 0.001XXXXX md 1: 0 md 2: 0.008XXXXX md 3: 0 md 4: 0
The generated schedule was:
2,0,7,INTERNAL,12.51,16,0 0,0,7,INTERNAL,24.67,16,0 1,0.9XXXXXXXXXXXXXXX,8,INTERNAL,10.03,16,0 1,0,6,INTERNAL,15.06,16,0 2,0.8XXXXXXXXXXXXXXX,9,INTERNAL,44.99,4,0 2,0,7,XXXXXXXXX,1.29,16,0 3,0,8,XXXXXXXXX,13.2,16,0
The first and the second cj went through correctly. But then:
2021-07-28 06:10:23,141 [INFO] Waiting for: 24.67 minutes. 2021-07-28 06:10:54,570 [INFO] STALL MONITOR: 2021-07-28 06:10:54,572 [INFO] Tx was already pushed; ignoring 2021-07-28 06:45:03,799 [INFO] JM daemon setup complete 2021-07-28 06:46:03,847 [INFO] Coinjoin amount too low, bringing up to: 0.00100000 BTC (100000 sat) 2021-07-28 06:46:03,849 [INFO] Choosing a destination from mixdepth: 2 2021-07-28 06:46:03,961 [INFO] Chose destination address: ************************************ 2021-07-28 06:46:04,041 [INFO] rel/abs average fee = 2.75e-05 / 2.75 2021-07-28 06:46:04,087 [INFO] Using bitcoin network feerate for 3 block confirmation target (randomized for privacy): 2530 sat/vkB (2.5 sat/vB) 2021-07-28 06:46:04,089 [INFO] total estimated amount spent = 0.0010XXXX BTC (10XXXX sat) 2021-07-28 07:05:03,614 [INFO] STALL MONITOR: 2021-07-28 07:05:03,616 [INFO] Stall detected. Retrying transaction if possible ... 2021-07-28 07:05:03,621 [INFO] Schedule entry: [1, 0.9XXXXXXXXXXXXXXX, 8, INTERNAL, 10.03, 16, 0] failed after timeout, trying again 2021-07-28 07:25:03,741 [INFO] STALL MONITOR: 2021-07-28 07:25:03,749 [INFO] No stall detected, continuing 2021-07-28 08:32:31,037 [INFO] Lost IRC connection to: guybrush.hackint.org . Should reconnect automatically soon. 2021-07-28 08:32:39,527 [INFO] joined: #joinmarket-pit guybrush.hackint.org 2021-07-28 08:57:56,262 [INFO] Taker not continuing after receipt of orderbook qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20512, resource id: 50872375, major code: 40 (TranslateCoords), minor code: 0 2021-07-28 08:57:56,445 [INFO] JM daemon setup complete 2021-07-28 08:58:56,585 [INFO] Taker not continuing after receipt of orderbook
I would have expected the script to check the user parameter mincj amount and build the schedule accordingly. Also verifying if the values put in by the user (min cj amount: 100.000 in my case) can be used at all with the actual amounts in the wallet.
I am getting the same error of " NotEnoughFundsException " whenever I try to do a tumble. The current tumble I am trying and my last one failed because of this error. Yesterday the tumble I tried got this error message, I restarted the tumble script with the --restart flag and declaring the tumble script file but it did not make any difference. When I deleted the tumble schedule file to do a second tumble with a fresh start I get the same thing. It is after the first coinjoin where the tumble halts with this error.
I think I figured this out. I think "NotEnoughFundsException" happens when I try to tumble starting from a different mixdepth than 0. If I move funds to mixdepth 0 then tumble I have not had issues yet.