--- Day changed Tue Aug 06 2019 00:39 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #joinmarket 01:42 < belcher_> harding: yeah i thought of that, and it made worse by schnorr where multisig just looks like a single sig 01:43 < belcher_> although that still requires people who rent out TXOs to put their money into some fancy multisig scheme, so it should improve the renting TXO situation 01:52 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 01:53 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Client Quit] 01:55 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 01:57 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Client Quit] 02:06 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 02:08 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Quit: leaving] 02:08 < belcher_> limiting the number of TXOs in a proof will probably be required just to keep bandwidth/data usage down 02:21 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 02:23 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Quit: WeeChat 2.5] 02:27 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 02:28 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Client Quit] 02:30 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 02:52 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Ping timeout: 248 seconds] 02:52 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has joined #joinmarket 03:14 -!- undeath [~undeath@hashcat/team/undeath] has joined #joinmarket 03:38 -!- eulersphi_ [~eulersphi@91.98.214.112] has joined #joinmarket 03:39 -!- eulersphi_ [~eulersphi@91.98.214.112] has quit [Client Quit] 03:41 -!- eulersphi [~bidel@static.99.162.63.178.clients.your-server.de] has quit [Quit: leaving] 03:45 -!- eulersphi [~eulersphi@91.98.214.112] has joined #joinmarket 03:57 < waxwing> undeath, what function does this line perform? https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/jmclient/jmclient/blockchaininterface.py#L500 03:57 < waxwing> since you're just going to quit on the next line, and nothing is persisted? 04:08 -!- eulersphi [~eulersphi@91.98.214.112] has quit [Quit: Leaving] 04:08 -!- eulersphi [~eulersphi@91.98.214.112] has joined #joinmarket 04:21 < waxwing> on the topic, i am leaning increasingly towards this point of view: when i added the fast option in 2016 or whenever it was, i was a bit less aggressive than i should have been. 04:21 < waxwing> this is clearly not just faster, but in a broad class of situations more reliable, too, and should have been made the default. it handles start up fine too. 04:22 < waxwing> the other mode is only needed for that painful recovery scenario. so if that becomes "recovery" mode only and non-default, we can make it more aggressive in terms of scanning forwards/gap limit, with the understanding that people will not usually be using it. 04:22 < waxwing> (oh and we should add a note about how the rescan can be date-limited too, detail) 04:32 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 245 seconds] 04:33 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 04:34 < undeath> waxwing: that line just makes sure the wallet is in a clean state. If the exception is caught in other code or the wallet is saved regardless you would end up with a messy state. 04:34 -!- eulersphi is now known as eulersphi_ 04:34 -!- eulersphi_ is now known as eulersphi 04:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 04:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 04:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 04:46 < waxwing> undeath, i don't understand what you mean. the next line raises and quits. it's not persisted. 04:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #joinmarket 04:47 < undeath> it only raises. exceptions could be caught in later code 04:47 < undeath> err, calling code 04:48 < waxwing> ah, good point. sure, that makes sense. 07:39 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 07:40 -!- MaxSan [~four@45.162.228.171] has quit [Quit: Leaving.] 07:50 -!- deafboy [quasselcor@cicolina.org] has joined #joinmarket 07:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection timed out] 07:57 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 07:57 -!- nixbitcoin [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has joined #joinmarket 08:00 -!- nixbitcoin [~nixbitcoi@gateway/tor-sasl/nixbitcoin] has quit [Client Quit] 08:05 < belcher> im having trouble running sendpayment against my own makers on regtest on miniircd, it seems something stalls and a message never gets to the taker so eventually the timeout routine runs, see https://pastebin.com/B7M8zpjG and scroll to line 128 08:06 < belcher> im having a bit of trouble following the code, it seems this is line is called but with accepted=False https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/dac7a26ccdb5de0e0a311124c2b330b7f8cc111a/jmdaemon/jmdaemon/daemon_protocol.py#L603 08:07 < belcher> my aim is to just do one coinjoin with myself on regtest 08:39 < waxwing> belcher, just a sec 08:40 < waxwing> undeath, damn you always answer so fast :) well i put a slightly more detailed answer but we don't conflict. setting up on LAN is a bit of a pain with bitcoind 08:40 < undeath> :) 08:40 < undeath> … especially if you have no idea how your system works 08:41 < waxwing> belcher, if necessary we'll get to more details, but there is a scenario on regtest where with the settings as on the current codebase, it times out too fast. let me dig it up for you. 08:42 < waxwing> belcher, try setting this to 15 instead of 5: https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/dac7a26ccdb5de0e0a311124c2b330b7f8cc111a/scripts/cli_options.py#L213 08:46 -!- MaxSan [~four@45.162.228.171] has joined #joinmarket 08:47 < belcher> trying now 08:48 < belcher> works 08:48 < belcher> now the transaction gets made 08:48 < belcher> :) 08:48 < belcher> its a bit strange IMO, because everything is running on localhost even minircd, so theres no network delay, how does any delay get up to 5 seconds? 09:05 < waxwing> belcher, i think it's throttling 09:05 < belcher> ah, yes 09:05 < waxwing> well yeah must be right. i'll throw in a commit for that before i forget. 09:05 < waxwing> wont' affect anyone else. 09:05 < waxwing> can i ask if you're using ygrunner? it would really speed things up for you :) 09:05 < waxwing> depending on what you're testing 09:06 < waxwing> pytest --btcconf=/../bitcoin.conf --btcroot=/.../bin/ --btcpwd=123456abcdef --nirc=2 test/ygrunner.py -s for example will give you a wallet all set up to use and starts everything bitcoin,irc, yieldgenerators 09:12 < belcher> im not using that, i tried earlier (like a week ago) but couldnt get it to work so just went with manually running a few yg's 09:12 < waxwing> belcher, just let me know. it's a real shame that that work gets wasted, especially because it could save people a lot of time. 09:13 < belcher> ok, ill try it again 09:34 -!- MaxSan [~four@45.162.228.171] has quit [Quit: Leaving.] 09:37 < belcher> waxwing this is an error that happens when i run pytest ygrunner.py https://pastebin.com/GqWKGpW6 09:37 < belcher> maybe the most interesting is line 52 where it seems to be connecting to localhost:8332 instead of localhost:18332 (because its regtest) 09:40 < waxwing> huh. is this all on one machine? 09:41 < belcher> yes 09:41 < waxwing> but i mean, yeah, wrong port 09:42 < waxwing> how does that happen, something must be set up different for you. my bitcoin conf only has rpcuser and rpcpassword settings 09:42 < waxwing> nothing else 09:42 < waxwing> and your joinmarket config is with regtest settings right? 09:42 < waxwing> ah, did you put the joinmarket.cfg in the root or in scripts? 09:42 < belcher> im using my regular bitcoin.conf which has a section [regtest] which has a different rpcuser/pass 09:42 < waxwing> run this command from the root and put the testing config in the root 09:42 < waxwing> oh. maybe that's different somehow. 09:43 < belcher> i have a joinmarket.cfg in both places 09:43 < belcher> the one in root has 8332 09:43 < waxwing> just make a new bitcoin.conf specially for this and put the rpcuser and pass in it, only. nothing else needed. 09:43 < waxwing> right it'll use the local one in root and you should (can?) run this from root 09:43 < belcher> now it seems to be working, once i changed the joinmarket.cfg in root 09:44 < belcher> lots of "sendtoaddress" and "generatetoaddress" RPCs 09:44 < waxwing> correct and then you'll see the hex seed for the Taker wallet and the three maker wallets, copy paste the former for your new wallet. 09:44 < waxwing> if at some point in future you want a different number of ygs, it's easy to configure in test/ygrunner.py 09:45 < belcher> so ygrunner keeps the yield generators running and you can run sendpayment or tumbler whenever to test against them? 09:45 < waxwing> yeah 09:46 < waxwing> for help with checking things you can always open the localhost irc servers on your IRC client and see things happening there 09:46 < waxwing> just bear in mind each yg has 8 btc, with 2 btc in mixdepth 0 and 6 in mixdepth 1, by default, to start. so if you wanted to test tumbler say you have to think about what settings are actually likely to work. a bit fiddly but i mean, it's flexible. 09:47 < waxwing> but it's useful for sanity checking wallet-tool and sendpayment behaviour, you can test pretty much any feature that way. 09:48 < belcher> ty 09:48 < waxwing> also worth mentioning, you can actually create a more real-style wallet with `generate` and use the file. obviously the hex thing is the same old hack as you originally put in and represents a bit of a shortcut, so if you were actually testing wallet behaviour it doesnt cover everything 09:49 < waxwing> but this way you actually have some coins to play with at the start, rather than having to mess around with mining the coins and then moving them around yourself 09:51 < belcher> that is useful 09:52 < belcher> its doing a lot of "generatetoaddress" so ill leave it be for a while (i assume it has to do 101 of them) 09:52 < waxwing> wait, it's still doing that/ 09:52 < waxwing> ? 09:52 < waxwing> it should take like 30 seconds or so 09:52 < belcher> the calls happen about 10 seconds apart 09:53 < waxwing> well no about 3 seconds 09:53 < waxwing> oh lol, yes 09:53 < waxwing> that's the tick-forward-chain 09:53 < waxwing> it's just simulating blockchain progressing 09:53 < waxwing> you should have seen the JM daemon setup complete message three times, a few seconds after it started 09:54 < belcher> yes 09:54 < belcher> that was several minutes ago 09:54 < belcher> ah so it will do this forever in order to simulate blocks being mined? 09:54 < waxwing> yeah 09:54 < belcher> ah interesting ok 09:54 < waxwing> it's basically a sped-up bitcoin blockchain 09:54 < belcher> right and thats how the pytest process never ends 09:54 < waxwing> you remember the demo in Malta? that was a whole tumbler in like 5 minutes based on that idea, using this setup. 09:55 < waxwing> yeah using pytest is a bit of a hack it just mean swe can reuse all the infrastructure for the test suite 09:55 < belcher> nope, because my demo was right after yours and i was still preparing it 09:55 < belcher> thats cool 09:55 < belcher> this is a lot easier you're right 09:55 < waxwing> well if you watch my vid now you can easily reproduce it :) 09:56 < belcher> cool 09:57 < belcher> i see now in docs/TESTING.md that ygrunner is explained 11:18 -!- reallll [~belcher@unaffiliated/belcher] has joined #joinmarket 11:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 11:49 -!- reallll is now known as belcher 12:22 < zfk> is the jm wallet encrypted in such a way that its safe to store on a VPS if you use a sufficiently strong password? 12:24 < undeath> yes 12:24 < undeath> it's using aes-256 with a strong argon2 password hash, all metadata encrypted 12:25 < undeath> just keep in mind that everything is of course in ram while jm is running 12:59 < zfk> thx 13:28 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 14:47 -!- davex_ [~user@45.74.60.149] has joined #joinmarket 14:47 -!- davex__ [~user@45.74.60.130] has quit [Ping timeout: 245 seconds] 14:57 -!- undeath [~undeath@hashcat/team/undeath] has quit [Quit: WeeChat 2.4] 17:34 -!- CgRelayBot [~CgRelayBo@p5DE4AC41.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 17:36 -!- AgoraRelay [~jmrelayfn@p5DE4AC41.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 17:45 -!- AgoraRelay [~jmrelayfn@p5DE4AB52.dip0.t-ipconnect.de] has joined #joinmarket 17:48 -!- CgRelayBot [~CgRelayBo@p5DE4AB52.dip0.t-ipconnect.de] has joined #joinmarket 19:25 -!- Wabbly [~goofball@anon-49-145.vpn.ipredator.se] has joined #joinmarket 19:26 < Wabbly> anyone using Wasabi? 20:52 -!- Wabbly [~goofball@anon-49-145.vpn.ipredator.se] has quit [Quit: Leaving] 21:05 -!- Cory [Cory@unaffiliated/cory] has quit [Ping timeout: 268 seconds] 21:11 -!- Pasha [Cory@unaffiliated/cory] has joined #joinmarket 21:14 -!- Pasha is now known as Cory 21:26 -!- eulersphi_ [~eulersphi@91.99.193.111] has joined #joinmarket 21:27 -!- eulersphi_ is now known as Guest21940 21:30 -!- eulersphi [~eulersphi@91.98.214.112] has quit [Ping timeout: 272 seconds] 22:00 -!- Guest21940 is now known as eulersphi