--- Log opened Fri Jun 04 00:00:28 2021
01:50 -!- undeath [~undeath@user/undeath] has joined #joinmarket
05:21 -!- undeath [~undeath@user/undeath] has quit [Quit: WeeChat 3.1]
06:08 -!- technonerd [~techno@user/technonerd] has quit [Remote host closed the connection]
06:09 -!- technonerd [~techno@user/technonerd] has joined #joinmarket
09:21 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Remote host closed the connection]
09:22 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #joinmarket
09:36 -!- Evanito[m] [~evanito@2001:470:69fc:105::1ec] has quit [Quit: node-irc says goodbye]
09:36 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has quit [Quit: node-irc says goodbye]
09:38 -!- Evanito[m] [~evanito@2001:470:69fc:105::1ec] has joined #joinmarket
09:42 -!- openoms[m] [~openomsma@2001:470:69fc:105::c2f] has joined #joinmarket
14:55 -!- LittleBoy [~LittleOne@89.46.102.116] has joined #joinmarket
14:56 < LittleBoy> Having issues installing on Windows 10 (directly on Windows). I've added the server=1 line to Bitcoin Core's configutation file and I get this message when trying to install JoinMarket: "Failed to setup joinmarket: JsonRpcConnectionError('RPC connection to Bitcoin Core was not established successfully.') Errors about failed RPC connections usually mean an incorrectly configured instance 
14:56 < LittleBoy> of Bitcoin Core (e.g. it hasn't been started or the rpc ports are not correct in your joinmarket.cfg or your bitcoin.conf file).
14:56 < LittleBoy> Bitcoin Core is fully synced and up to date.
14:56 < LittleBoy> Python 3.9.5 is also installed, included in PATH, and pip as well.
14:57 -!- belcher_ is now known as belcher
14:57 < belcher> try running `netstat -l` on command prompt, it should print out a list of open ports, check that port 8332 is on that list of ports
14:57 < belcher> 8332 is the bitcoin core RPC port, so we're checking that its open
14:58 < LittleBoy> Great, one moment.
14:59 < LittleBoy> Sure it shouldn't be -a or -b?  Get manpages for -l
15:00 < belcher> on linux its -l for listening ports
15:00 < belcher> i guess on windows its different, try netstat /? to read the help
15:00 < LittleBoy> Yep, reading now.
15:03 < LittleBoy> I have 8333 listening, but no 8332.
15:27 < LittleBoy> 8333 looks like it's all BTC Core peers.
15:36 < waxwing> LittleBoy, firewall issues sometimes can be a thing too, although i don't remember offhand. only did this perhaps once, a couple of years ago.
15:36 < waxwing> oh but also you have to change the bitcoin.conf to allow it to serve rpc don't you? maybe check in #bitcoin about that.
15:37 < waxwing> the thing is generally, make sure you can do an RPC call using bitcoin-cli before trying it on joinmarket.
15:45 < belcher> LittleBoy try adding something to the bitcoin.conf file to prove that bitcoin core really has loaded it, for example add connect=0 and check that it really makes bitcoin core not connect to anything
15:46 < LittleBoy> I was following the windows installation documentation at https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/INSTALL.md#installation-on-windows
15:46 < belcher> yes server=1 has to be added to make the rpc server be enabled
15:46 < LittleBoy> In the bitcoin config file, the only thing that I have there is "server=1"
15:47 < LittleBoy> I added it, saved, restared BTC core as well as restarted the machine. Still throwing the above error when I try to install JoinmarketQT-0.8.2.exe
15:47 < JoinMarketRelay> [hackint/nikolai] hello
15:47 < LittleBoy> I'll dig into firewall rules in a moment, good point. BRB, running to store for water.
15:49 < JoinMarketRelay> [hackint/nikolai] belcher: wanted to ask you, what actually happens if transaction making with YG succeeds and replies with 'goodtx' but then the broadcasting node replies with 'absurd high fee' and drops the transaction - do these kind of CJ tries have protection enabled against snooping?
15:49 < waxwing> yeah you guys are right, no need for more than server=1, i was thinking of the case of remote machin RPC calls.
15:50 < belcher> if the "sendrawtransaction" call fails with "absurd high fee" then thats a bug, joinmarket should never create txes with miner fees that high
15:51 < belcher> the protection against snooping with the podle mechanism still happens in that case, if thats what you meant (i didnt entirely understand your second question)
15:56 < JoinMarketRelay> [hackint/nikolai] belcher: yes that was my question thanks for answering
15:56 -!- xyy [~xyy@2001:470:69fc:105::f2d] has joined #joinmarket
15:58 < JoinMarketRelay> [hackint/nikolai] it just happened, a tx with an absurd fee was made, was replied with 'goodtx' and then 'Timed out: transaction with outputs: ((CBitcoinScript([0, x.......... SNIP ......)) not broadcast' the fe was 0.25 btc
15:59 < JoinMarketRelay> [hackint/nikolai] s/fe/fee/
15:59 < waxwing> on mainnet?
15:59 < JoinMarketRelay> [hackint/nikolai] yes
16:00 < waxwing> as a general point in abstract without any concrete data to look at it, any transaction that doesn't go through has no effect on the maker.
16:00 < JoinMarketRelay> [hackint/nikolai] after it wasn't broadcast for a weird [INFO] reason i haven't seen before i tried to broadcast it manually from a node and it replied with an absurd fee.
16:01 < waxwing> but would really need to see actual data, that certainly should not, of course, ever happen with vanilla JM software.
16:01 < waxwing> there are checks that prevent the taker trying to make such a tx.
16:01 < waxwing> we have our own absurd_fee check, independent of bitcoin's own.
16:01 < JoinMarketRelay> [hackint/nikolai] got it. my only concern was if this could maybe enable 3rd parties snooping as it passed some of the checks but it did not pass broadcast check
16:02 < JoinMarketRelay> [hackint/nikolai] i could send you the output if you wish, pgp encrypted of course
16:02 < waxwing> yeah but that's what podle's for. it's the nature of our system that a random adversary could start the negotiation with you and not complete.
16:02 < JoinMarketRelay> [hackint/nikolai] i will have to look into the code when i'll have some days spare :)
16:02 < JoinMarketRelay> [hackint/nikolai] thanks for the help.
16:03 < waxwing> yes if you could send the tx, serialized is easiest i guess. encrypted to one of our gpg keys.
16:03 < waxwing> but up to you. if you do it might be at least of interest. at best i would just be cross checking that what you report is right .. but, i guess it's unlikely you got it wrong.
16:03 < JoinMarketRelay> [hackint/nikolai] give me few minutes to collect the data
16:04 < waxwing> 0.25btc .. it's actually hard to come up with a theory as to how that might happen, they'd have to deliberately edit the absurd_fee limit check in the config.
16:16 < JoinMarketRelay> [hackint/nikolai] http://ix.io/3oMe enc with belcher key
16:17 < JoinMarketRelay> [hackint/nikolai] just happened once more, similar size
16:22 < JoinMarketRelay> [hackint/nikolai] for some reason scriptsig is 'deadbeef' string
16:24 < waxwing> that means the taker is running pre-0.8.2 JM (and post 0.7.0)
16:33 < waxwing> well i was ready to look at it, but OK :) off to bed i guess.
16:41 < JoinMarketRelay> [hackint/nikolai] no rush. you got the msg?
16:43 < JoinMarketRelay> [hackint/nikolai] or should i have encrypted with a different key?
16:43 < JoinMarketRelay> [hackint/nikolai] sleep well, good night
18:42 -!- LittleBoy [~LittleOne@89.46.102.116] has quit []
21:33 -!- belcher_ [~belcher@user/belcher] has joined #joinmarket
21:36 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 244 seconds]
21:56 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Remote host closed the connection]
21:56 -!- openoms [~quassel@gateway/tor-sasl/openoms] has joined #joinmarket
--- Log closed Sat Jun 05 00:00:29 2021