Skip to content
This repository has been archived by the owner on May 13, 2022. It is now read-only.

sendpayment.py -N 1 -m 4 wallet.jmdat 55555 bc1_address always fails. #784

Open
johnblanc opened this issue Jun 17, 2020 · 4 comments
Open

Comments

@johnblanc
Copy link

johnblanc commented Jun 17, 2020

Tried several times today and this kind of payment always fails.

2020-06-17 13:42:51,736 [INFO] Using maximum coinjoin fee limits per maker of 0.1000%, 0.00008071 BTC (8071 sat)
Enter wallet decryption passphrase:
WARNING: Expected bitcoin network miner fees for this coinjoin amount are roughly 15.0%
You might want to modify your tx_fee settings in joinmarket.cfg. Still continue? (y/n):y
2020-06-17 13:46:26,723 [INFO] Listening on port 27183
2020-06-17 13:46:26,738 [INFO] Starting transaction monitor in walletservice
2020-06-17 13:46:26,739 [WARNING] Connection had broken pipe, attempting reconnect.
2020-06-17 13:46:31,996 [INFO] joined: #joinmarket-pit guybrush.hackint.org
2020-06-17 13:46:31,996 [INFO] Could not connect to ALL servers yet, waiting up to 60 more seconds.
2020-06-17 13:46:35,733 [INFO] joined: #joinmarket-pit tor.darkscience.net
2020-06-17 13:46:35,734 [INFO] All IRC servers connected, starting execution.
2020-06-17 13:46:35,735 [INFO] JM daemon setup complete
2020-06-17 13:47:35,783 [INFO] INFO:Received offers from joinmarket pit
2020-06-17 13:47:35,852 [INFO] Chose these orders: {'EDITED': {'cjfee': '0.000004',
'counterparty': 'EDITED',
'maxsize': 15151011,
'minsize': 45197,
'oid': 0,
'ordertype': 'swreloffer',
'txfee': 0}}
2020-06-17 13:47:35,853 [INFO] total cj fee = 0
2020-06-17 13:47:35,867 [INFO] total coinjoin fee = 0.0%
send with these orders? (y/n):y
2020-06-17 13:52:54,313 [INFO] INFO:Preparing bitcoin data..
2020-06-17 13:52:54,979 [WARNING] Connection had broken pipe, attempting reconnect.
2020-06-17 13:52:56,249 [INFO] Using tx fee: 24478 sat/vkB (24.478 sat/vB)
2020-06-17 13:52:56,250 [INFO] total estimated amount spent = 0.00092775 BTC (92775 sat)
2020-06-17 13:52:57,315 [INFO] INFO:Commitment sourced OK
2020-06-17 13:52:57,689 [INFO] Lost IRC connection to: tor.darkscience.net . Should reconnect automatically soon.
2020-06-17 13:52:57,691 [INFO] Attempting to reconnect...
2020-06-17 13:52:57,752 [INFO] Lost IRC connection to: guybrush.hackint.org . Should reconnect automatically soon.
2020-06-17 13:52:57,752 [INFO] Attempting to reconnect...
2020-06-17 13:52:57,753 [WARNING] Couldn't find a route to send privmsg
2020-06-17 13:52:57,753 [WARNING] For counterparty: EDITED
2020-06-17 13:53:05,899 [INFO] joined: #joinmarket-pit tor.darkscience.net
2020-06-17 13:53:06,000 [INFO] joined: #joinmarket-pit guybrush.hackint.org
2020-06-17 13:53:57,784 [INFO] Makers who didnt respond: ['EDITED']
2020-06-17 14:06:27,516 [INFO] STALL MONITOR:
2020-06-17 14:06:27,694 [INFO] Stall detected. Regenerating transactions and retrying.
2020-06-17 14:06:27,694 [INFO] A transaction failed but there are insufficient honest respondants to continue; giving up.
2020-06-17 14:06:27,973 [INFO] Lost IRC connection to: guybrush.hackint.org . Should reconnect automatically soon.
2020-06-17 14:06:28,425 [INFO] Lost IRC connection to: tor.darkscience.net . Should reconnect automatically soon.
done

And that happened like 4 times in a row. Am I doing something wrong or there is an issue here?

@johnblanc
Copy link
Author

13 days later and that is still the case, can't send out with even 1 counterparty
with 0 counterparties works fine though

@AdamISZ
Copy link
Member

AdamISZ commented Jun 30, 2020

Hi,

First, sorry this was not answered. You posted it during a 5 day period when my github pings were being sent to spam by my mail client, and I missed it.

Second, to diagnose this one I'm going to need quite a bit more info from you, it's unfortunately not one of those that's immediately obvious from the console output.

Before that though, a general point - it is very common for new users to want to test joinmarket out with a tiny amount, unfortunately it will almost never work well. It is certainly possible to test with amounts < 100K sats but it is best with a whole list of different things that can go wrong, around fees and around liquidity. Joinmarket has unusually tricky requirements in estimating fees (it has to essentially estimate the fee twice or three times depending on how you look at it), and there is some roughness of necessity in that process - using very small amounts kind of screws that up and it can go wrong various ways. Also, makers (counterparties) tend not to offer very small sizes so you're often left with a tiny number of, or no counterparties, and they may even be misconfigured.
Amounts less than 500K can be problematic. Amounts less than 100K are almost guaranteed to be problematic, or just not work.

The above paragraph is a general comment, and may or may not be relevant to what went wrong here, so moving on to more concrete things:

  1. Your OS/distro
  2. Your joinmarket version; either the version number you downloaded or if you use git, the top commit shown from git log.
  3. You use -N 1; do you have minimum_makers in joinmarket.cfg set to 1 ? In the most recent version JM will immediately quit if you misconfigure this, but iirc that was after 0.6.2(?), if earlier version it won't work but I don't remember what it will show.
  4. You have -m 4 - so you definitely have coins in mixdepth 4? I guess so, iirc the error for 'no coins' is quite explicit.
  5. Post your joinmarket.cfg with only the rpc settings scrubbed (and possibly any IP address if you use it for the blockchain, usually it's just 'localhost' though). The other settings are not dangerous to make public.
  6. Change your debug_log_level to DEBUG in that config and rerun the same coinjoin case and post the console output from that.

The fact that it works OK with counterparties zero doesn't tell us too much; but that, combined with the disconnects shown above suggest to me that it might be something screwy about your connection to IRC (not the last two messages 'Lost IRC...`, they are normal (just a screwy detail of the logging) even for successful runs. I mean the ones in the middle.

@johnblanc
Copy link
Author

  1. qubes os 4
  2. the latest commit in git log seems to be from 23th March
  3. It's set to 4, that might be a problem I guess, I thought the command line parameter overrides this. But it doesn't quit though.
  4. yes for sure, checked

And the amount is pretty small as you mentioned so that might be a problem too, I'll try in the next days with bigger amounts
thank you!

@AdamISZ
Copy link
Member

AdamISZ commented Jun 30, 2020

Oh. I see why this issue got neglected. It's in the wrong repo. It should be opened in /joinmarket-clientserver not /joinmarket

Re: commit, please give exact commit hash to avoid ambiguity.
The PR that merged the early-quit-if-maker-count-less-than-minimum is here: JoinMarket-Org/joinmarket-clientserver#550 which was 30th March, so it was not in master on 23 March. It's possible that you will see evidence of this if you run with debug switched on.

Qubes may present its own challenges with regard to networking. I suggest coming on IRC (#joinmarket on freenode) to ask about it if you find you are not able to get the network connections working. Most people use Tor for the IRC configs but it may need something specific for the socks proxy settings etc I don't know.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants