--- Day changed Wed May 02 2018 00:51 < adlai> can't you squeeze a teeny extra bit of entropy by spinning the coin on edge, and accounting for the chance that your angular impulse is sufficiently balanced? 00:53 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 240 seconds] 01:10 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 01:12 < waxwing> adlai, coins are good for generating IOTA private keys; they use ternary so "on edge" = -1. Or something. 01:37 * adlai keeps pretending that iota is a purely academic project that happens to be namesquatted on exchanges by some practical jokers... much easier to get along with the folks writing papers this way 03:18 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket 03:29 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket 03:58 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has joined #joinmarket 04:00 -!- quitobro_ [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket 04:03 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has quit [Ping timeout: 256 seconds] 04:03 -!- quitobro_ is now known as quitobro 04:14 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 260 seconds] 04:17 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 248 seconds] 04:21 -!- lnostdal [~lnostdal@77.70.119.51] has joined #joinmarket 05:07 < quitobro> morning guys. does anyone have handy a past `obwatch` command they’ve run successfully they could paste in here? 05:07 < quitobro> i’m doing something wrong, that much i know... 05:08 < quitobro> seems like that script maintains its own version of joinmarket.cfg 05:10 < quitobro> also for `sendpayment` i regularly stall out on the last part, “Got sig_deserialized” and have to retry. has anyone seen this as well? 05:13 < waxwing> quitobro, the obwatcher script, rather strangely, uses the joinmarket.cfg from the parent directory (scripts). i'm sorry for it being a bit shitty but it wasn't a priority as you can imagine. 05:13 < waxwing> actually i'll try right now to run it as a sanity check. usually i just run the one on jm.me 05:13 < quitobro> waxwing: the one on jm.me is just a JM daemon running the same obwatch script right? 05:14 < waxwing> re 'got sig deserialized', i don't even remember where that comes up in the debug output, no, i haven't heard of that error cropping up. 05:14 < waxwing> yes it's the same with a very minor tweak to the html front end of it. 05:15 < quitobro> ok, would you accept a PR which changes obwatch to use the same joinmarket.cfg as all the other stuff in scripts/ ? 05:15 < waxwing> quitobro, ok it seems to work fine here. 05:15 < waxwing> it does use the same joinmarket.cfg 05:16 < waxwing> it basically searches up a directory iirc (can check if you like). perhaps you encountered an error because you tried to run it from scripts? i.e. python scripts/obwatcher.py ? 05:17 < quitobro> no i’m running it from whtin scripts dir, just like sendpayment and yield-generator scripts 05:17 < quitobro> and it craps out on bad RPC creds 05:17 < quitobro> i think it has a default configuration in the script iirc 05:17 < waxwing> it's not in that directory, though 05:17 < waxwing> it's in scripts/obwatch 05:18 < waxwing> all of this can and should be fixed, as i did in coinswapcs, to put all config and logs in ~/.joinmarket home directory. i think the scaffolding's already there, because i put it in to do that project (which uses this as a dependency) 05:19 < waxwing> all this kind of stuff is silly in that regard, but i didn't want to change anything about how the command line worked from how it worked for original joinmarket. probably wrongly. 05:20 < quitobro> waxwing: so i should run obwatch from its subdir or from the project top level dir? 05:21 < waxwing> from within obwatch, in its own directory 05:25 < waxwing> when i said 'it's shitty' i didn't mean it doesn't work, i just mean specifically that confusion above about directories, which is entirely fixable, and i've even already fixed it, for coinswapcs, you can see how the fix is used here: https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/jmclient/jmclient/configure.py#L307-L312 05:26 < waxwing> just pass config_dir as some home directory like APPDATA/joinmarket or similar, and you're good to go 05:26 < waxwing> sorry config_path 05:27 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has quit [Ping timeout: 240 seconds] 05:30 -!- puddinpop [~puddinpop@unaffiliated/puddinpop] has joined #joinmarket 05:33 < waxwing> quitobro, is it ok? 05:34 < quitobro> waxwing: i’m trying where i remove the ‘..’ argument passed to `load_program_config` here: https://github.com/mecampbellsoup/joinmarket-clientserver/blob/5cdc379158d48474f8ee1e590607400da5087058/scripts/obwatch/ob-watcher.py#L426 05:35 < waxwing> quitobro, argh .. you don't need to change anything :( 05:35 < waxwing> just run it from within obwatch/ 05:35 < quitobro> yea either way i realize 05:36 < quitobro> i just prefer not to `cd` around 05:36 < quitobro> heh 05:37 < waxwing> ok i get it :) well at least you know the situ. now. 05:37 < waxwing> so about the other thing, https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/7860fe1a36b0e63113f63154babfab6ec037730b/jmclient/jmclient/taker.py#L482 05:37 < quitobro> now i’m getting an annoying python error, probably need to reinstall my venv? 05:37 < waxwing> this was a forgotten debug printout. but more relevantly, are you definitely not seeing anything *after* that message? 05:37 < waxwing> quitobro, what annoying python error? did you install with --develop? 05:38 < quitobro> https://gist.github.com/mecampbellsoup/06527fc1febf3a9d89d36eb1946712d1 05:38 < quitobro> i did yea 05:38 < quitobro> i have egglnk files 05:38 < quitobro> i see nothing until it reports “STALL DETECTE" 05:40 < waxwing> i have no idea about that os.sep error. perhaps it's a python version thing. is that 2.7.14 i'm seeing in your output? 05:40 < quitobro> yea 05:40 < quitobro> yea i think i just need to fix the python thing and it’s not related 05:41 < waxwing> that's not *necessarily* an error your side. if you didn't get all signatures. what was your -N setting and have you changed minimum_makers? are you able to do any joins, or do all fail exactly the same way? 05:41 < waxwing> (now talking about stall detected case again) 05:41 < quitobro> they fail intermittently, was just able to succeed 05:41 < waxwing> hmm, we perhaps have some non-cooperative makers i guess. but see Q above on numbers ^, in particular do you allow complete with subset and are you using minimum_makers = 2? 05:42 < quitobro> my -N defaults to 2, min_makers 05:42 < waxwing> timeouts are at least possible if you use very large numbers and/or one maker has a big lag on their connection 05:43 < quitobro> okay perhaps the maker with the lowest fee was timing out a lot 05:43 < quitobro> waxwing: so that print statemenet should be a logger.log instead right? 05:44 < quitobro> that’s what you mean by ‘forgotten'? 05:44 < waxwing> right that's a feasible scenario. one of the more robust ways to use the system is to do say -N 5 or 6 but with min_makers 2 it *usually* can get through even if 1 or 2 makers in the pit are unresponsive. 05:44 < waxwing> yes that's what i meant by forgotten, prob don't need that line or at least use log.debug not print 05:45 < waxwing> also when using the tumbler mode, it will retry after stall, making vaguely intelligent alterations and ignoring unresponsive makers the following time. 05:51 < quitobro> waxwing: if i specify -N 5 but have 5 or 6 in joinmarket.cfg for min_makers, doesn’t the - N flag override that min_makers config value? 05:55 < waxwing> well basically if you have min_makers < N then any number of counterparties between N and min_makers is ok 05:56 < waxwing> if you set N less than min_makers then the tx cannot go through 05:56 < waxwing> but you wouldn't generally do that. hopefully nobody is choosing N=1, although it's technically possible to do that, it's of dubious value as a coinjoin. 05:57 < waxwing> N is what you want, min_makers is the minimum you're prepared to accept. Also, you can set the latter to 0, in which case you allow no tolerance at all (N and only N is acceptable) 06:29 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 06:49 -!- Giszmo [~leo@ip-70-237-219-201.nextelmovil.cl] has joined #joinmarket 06:54 -!- Giszmo [~leo@ip-70-237-219-201.nextelmovil.cl] has quit [Ping timeout: 255 seconds] 07:01 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Quit: quitobro] 07:06 < waxwing> really liking undeath's code (see #99) 07:08 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #joinmarket 07:15 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has joined #joinmarket 07:18 < belcher> yes 07:18 < belcher> looked at it just now 07:19 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has joined #joinmarket 07:24 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has quit [Ping timeout: 264 seconds] 07:25 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket 07:26 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 260 seconds] 07:36 < waxwing> also TIL you can take github.com/.../pull/99 and stick '.patch' at the end of the url and download the patch :) useful for chucking a patch on top of master in a branch and testing without messing anything up. 07:38 < belcher> oh great i just screwed up a git rebase on my first core PR, slightly embarrassing 07:38 < waxwing> heh. gotta love git. 07:40 < belcher> anything with git push --force is just problem hah 07:41 < belcher> ah here we go, just made it worse... ill stop now 07:42 < belcher> i think i did git pull upstream or something before rebasing, so that mustve pulled in other's commits 07:42 < waxwing> nuke it from orbit? 07:42 < waxwing> don't ask me :) 07:43 < belcher> i know im just complaining here hah 07:43 < belcher> "Allow edits from maintainers" is enabled so hopefully it will be easily to help me 07:45 < viasil> maybe try git fetch upstream; git rebase -i upstream/master? 07:47 < belcher> i wont try anything else just yet in case it makes it worse 07:47 -!- Giszmo [~leo@ip-227-237-219-201.nextelmovil.cl] has joined #joinmarket 07:47 < viasil> i could take a look if you point me to it and see if i can send the commands to fix 07:47 < belcher> https://github.com/bitcoin/bitcoin/pull/13152 07:49 < viasil> Ok, will take a sec, but looking at 07:59 < viasil> https://pastebin.com/a25AN7Zs 07:59 < viasil> This should do it. To verify, just test it by first pushing to a new/test branch 08:00 < viasil> That new/test branch should be exactly 1 commit ahead 08:14 < belcher> so by that you mean "git push origin new-test-branch" ? 08:14 < viasil> git push origin cleanup:new-test-branch 08:15 < viasil> (from local branch cleanup, to remore branch new-test-branch) 08:15 < belcher> ok 08:15 < viasil> remote 08:15 < viasil> OH WAIT! 08:15 < viasil> git push belcher cleanup:new-test-branch 08:15 < belcher> could you write a pastebin for all the steps for testing 08:15 < viasil> sorry, missed that. in the example i sent, origin is bitcoin/bitcoin.git 08:16 < belcher> i assume its just replacing the new test branch from 2018-04-rpc-getaddress but not sure 08:16 < viasil> Yes, just replace the last line with git push belcher cleanup:new-test-branch 08:16 < belcher> ah ok 08:20 -!- d3spwn [53a19dc8@gateway/web/freenode/ip.83.161.157.200] has joined #joinmarket 08:20 -!- Giszmo [~leo@ip-227-237-219-201.nextelmovil.cl] has quit [Ping timeout: 256 seconds] 08:29 < belcher> viasil here we go, that looks as expected what you said https://github.com/chris-belcher/bitcoin/commits/new-test-branch 08:29 < belcher> 1 commit ahead of master 08:29 < belcher> then ill do git push belcher cleanup:2018-04-rpc-getaddress -f 08:29 < viasil> Yes, I believe that's what you wanted 08:30 < belcher> could you briefly explain what your commands did 08:30 < viasil> Yes, and that will update the existing PR 08:30 < viasil> sure 08:30 < belcher> then ill read the git manual and try to figure it out as well 08:30 < viasil> In short, life in git is MUCH easier if you never use git pull, but unfortunately that's the most common command 08:31 < belcher> btw that worked on the PR 08:31 < viasil> Git can of course have many remotes, so hopefully that part is understood (git remote add). You can add as many remotes as you want 08:31 < viasil> nice! 08:31 < viasil> In short, git pull = git fetch; git merge 08:32 < viasil> This causes troubles for upstream rebasing, since merges often guarantee that your timeline/history won't match theirs, assuming the remote repo is moving 08:32 < viasil> The thing to try is git fetch; git rebase instead, which always uses the remote timeline and places your changes on top of theirs 08:33 < viasil> git reset --hard just evens up your local working tree with the specific branch 08:33 < viasil> So we started with your 2018-04-rpc-getaddress as the cleanup branch 08:33 < belcher> ok i see 08:33 < viasil> git checkout -b BRANCH just creates the new BRANCH 08:34 < belcher> so what must have happened was i did git pull and then rebase, and it put my commits on top of the new ones that had been merged in that time 08:34 < viasil> The rebase said take all of origin (bitcoin) and bring it over, then take our commits and add them on top 08:34 < viasil> yes, exactly 08:35 < viasil> So in my example, as the bitcoin repo moves, to keep your PR up to date, you can do: git fetch origin; git rebase origin/master; git push belcher branch:2018-04-rpc-getaddress -f 08:35 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #joinmarket 08:36 < belcher> ok 08:36 < belcher> in my regular cloned directory, i actually cloned /chris-belcher/bitcoin 08:36 < belcher> so origin would be that, not /bitcoin/bitcoin, which i configured to be "upstream" 08:37 < viasil> Yeah, that's the better way to do it (and what I tend to do) 08:37 < viasil> I just sent commands as a third part in this case ;-) 08:37 < viasil> party 08:37 < belcher> so i guess id do git fetch upstream; git rebase upstream/master; git push belcher branch:2018-04-rpc-getaddress -f ? 08:38 < viasil> yes, the only thing to foolproof it is to first do git reset --hard belcher/2018-04-rpc-getaddress first 08:38 < belcher> what exactly does that do? wont that delete any changes i made 08:38 < viasil> So start with existing pull request, rebase against upstream/master, push updated timeline 08:39 < belcher> ok 08:39 < viasil> Yes, it modifies the local working tree. So before that, create a new/tmp branch like "git checkout -b tmp" 08:39 < viasil> I tend to commit whatever i'm doing and then switch branches to do unrelated things like that 08:40 < viasil> You can always edit your commit later (rebase -i) 08:40 < belcher> ok 08:40 < belcher> yep 08:41 < belcher> thanks for the help 08:41 < belcher> ill read a bit more 08:41 < viasil> no problem, getting comfortable with git is a process ;-) 08:42 < viasil> it's quite complicated, but very powerful/cool 08:43 < viasil> took me years to get to where i am, and there's plenty i don't know about it 08:43 < viasil> A real git guru could show how to do that pastebin in probably much fewer lines :-) 08:44 < belcher> hehe 09:19 < waxwing> Unless anyone has any issues with it, i'm going to merge #99 and then add onto it the code needed for taker support. been doing some sendpayment and tumbler tests, it (the taker side) seems to work fairly easily. the toggle is the `segwit` setting in `POLICY`. 09:20 < waxwing> only small details is i can't be bothered to make it work for the GUI, there's a few fiddly things with wallet handling there. 09:23 < belcher> iv got no issues 09:54 < waxwing> i've got 99 PRs but a BCH ain't one 09:55 < arubi> hehe, don't worry, they'll merge it and credit you as a contributor in their readmes 10:05 -!- quitobro_ [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has joined #joinmarket 10:08 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Ping timeout: 248 seconds] 10:08 -!- quitobro_ is now known as quitobro 10:21 < arubi> I'm so excited about sighash_noinput.. not sure who was following #lightning-dev when I asked if they'd rather include the pubkey being signed for in the sighash, which roasbeef said it's not gonna happen, so basically if noinput is happening we're actually getting crude covenants in bitcoin 10:24 < arubi> ie the simplest example would be sending to a scriptpubkey " checksig" where the the sighash type is noinput_single, signing only for a single output which is back to the same scriptpubkey 10:25 < arubi> so you'll basically need a second input in there (and change) for fees, but this is basically a covenant.. fun :) 10:44 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 10:58 < belcher> #lightning-dev on freenode arubi ? iv been on there all day and i havent seen what you said 10:58 < arubi> belcher, ah it was yesterday really, like 22 hours ago or something 10:58 < belcher> ah 11:40 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 248 seconds] 11:50 -!- quitobro_ [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket 11:53 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has quit [Ping timeout: 264 seconds] 11:53 -!- quitobro_ is now known as quitobro 12:04 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Read error: Connection reset by peer] 12:08 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 12:15 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket 12:23 -!- GitHub105 [GitHub105@gateway/service/github.com/x-trkdxbbqbkdlwrby] has joined #joinmarket 12:23 < GitHub105> [joinmarket-clientserver] AdamISZ pushed 4 new commits to master: https://git.io/vpzQp 12:23 < GitHub105> joinmarket-clientserver/master 715985d undeath: add support for non-segwit maker 12:23 < GitHub105> joinmarket-clientserver/master d2196ad undeath: fix maker crash when verifying transaction with p2sh output in non-sw mode 12:23 < GitHub105> joinmarket-clientserver/master 605eebe undeath: add test cases for maker::verify_unsigned_tx 12:23 -!- GitHub105 [GitHub105@gateway/service/github.com/x-trkdxbbqbkdlwrby] has left #joinmarket [] 12:24 -!- GitHub148 [GitHub148@gateway/service/github.com/x-oqimrmetwhguzhsc] has joined #joinmarket 12:24 < GitHub148> [joinmarket-clientserver] AdamISZ closed pull request #99: add support for non-segwit maker (master...non-segwit-maker) https://git.io/vd6Ee 12:24 -!- GitHub148 [GitHub148@gateway/service/github.com/x-oqimrmetwhguzhsc] has left #joinmarket [] 12:42 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 12:48 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 13:11 -!- madacool [~Thunderbi@181.56.216.44] has joined #joinmarket 13:11 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 248 seconds] 13:11 -!- madacool is now known as madacol 13:14 < waxwing> hmm talking about git, never did figure out how to make a PR when you've moved the repo 13:14 < arubi> explain? 13:17 < waxwing> if you relocate it from your own account to another account (joinmarket-org in this case), the link is maintained, i can't push a branch on my repo separately 13:17 < waxwing> and of course i also can't create another fork (it already exists) 13:19 < belcher> waxwing did you get a bitcoin wiki account in the end? 13:20 < arubi> so JoinMarket-Org/joinmarket-clientserver.git and AdamISZ/joinmarket-clientserver.git are the same remote? that's pretty weird 13:20 < waxwing> belcher, yes 13:20 < waxwing> arubi, yes that's how it works. belcher had the same issue on the original repo 13:21 -!- madacool [~Thunderbi@181.56.216.44] has joined #joinmarket 13:22 < arubi> huh. we do see wumpus\sipa open PRs against bitcoin/bitcoin.git, so it should be possible? 13:22 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 256 seconds] 13:22 -!- madacool is now known as madacol 13:23 < arubi> unless somebody else owns the actual repo.. I wonder what's going on there. interesting actually 13:27 < waxwing> arubi, it's only in the case where you owned a repo and you chose to move it to another account. 13:28 < waxwing> in my case the repo joinmarket-clientserver was moved from AdamISZ to joinmarket-org 13:28 < arubi> so you're saying that whenever anything is pushed to adamisz, it's automatically also pushed to joinmarket-org? 13:29 < waxwing> yeah it functions like a link now 13:29 < waxwing> they're the same remote 13:29 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 248 seconds] 13:29 < waxwing> it's some github shenanigans where the idea is, people who had already got links to the former get automatically redirected to the latter. so it's very useful, generally. 13:29 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 13:30 < waxwing> but i don't know how to PR against it like the normal way. perhaps it can be done on the website somehow, shrug. 13:31 < belcher> for me it ends up that i push the branches to /joinmarket-org/joinmarket and then open a PR from there 13:31 < belcher> but yes that ends up cluttering up the joinmarket repos with my own branches 13:32 < waxwing> belcher, ah right i see. so you open the PR from the branch on the same repo. of course. 13:32 < belcher> yeah 13:32 < waxwing> yeah ive just done that (opened it as another branch) so yeah i can PR there. thanks. 13:32 < belcher> oh i thought you already knew hah 13:32 < belcher> but were just looking for a way to do it from /AdamISZ/ instead of /joinmarket-org/ 13:33 < belcher> for me i dont think /chris-belcher/joinmarket even exists, it just redirects to /joinmarket-org/joinmarket 13:34 < arubi> yea that's the thing, if it did exist as a separate entity then clean PRs would be easy. I can see the usefulness you're mentioning waxwing but still it's weird that it acts this way :) 13:35 -!- GitHub160 [GitHub160@gateway/service/github.com/x-psaokvhpeltyznvc] has joined #joinmarket 13:35 < GitHub160> [joinmarket-clientserver] AdamISZ opened pull request #137: Add support for taker using a non-segwit wallet (master...taker-non-sw) https://git.io/vpzpy 13:35 -!- GitHub160 [GitHub160@gateway/service/github.com/x-psaokvhpeltyznvc] has left #joinmarket [] 13:36 -!- madacool [~Thunderbi@181.56.216.44] has joined #joinmarket 13:36 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 248 seconds] 13:36 -!- madacool is now known as madacol 13:37 < waxwing> belcher, well i think it should still exist, if you go to it on the website. 13:38 < belcher> it does exist it just redirects 13:38 < belcher> well i suppose that counts as existing 13:39 < waxwing> ah no, you're right, it does redirect, same here. i forgot you can't go to it any more. i was just confused because i still have these ones in my local remotes. 13:39 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 13:39 < waxwing> "local remotes" uhh you know what i mean :) 13:40 < belcher> regarding making -clientserver work for segwit=false, have you thought about how that might make the non-segwit pit continue to be used and so we'd have two active pits for longer 13:40 < waxwing> yeah this is really nbd. just *slightly* annoying having the branches on the main repo. 13:40 < belcher> then again, its actually probably a good idea because at least it gets people to upgrade to -clientserver 13:40 < waxwing> belcher, sure. i don't see a problem with it, or rather, i think that's just the way it is. 13:40 < arubi> you could just delete those after merging. a bit of work but it'll clean them up 13:41 < belcher> yes actually.. its good, everyone upgrades to -clientserver, which has default segwit=true, and after some time all the newbs end up the segwit pit 13:41 < waxwing> arubi, yes i do delete. only 3 right now (including master, and that one). the other is py3, which i was unable to finish. 13:41 < belcher> right now if people follow the link from the r/joinmarket sidebar they end up using non-cs which is probably why the non-segwit pit is still active 13:41 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 13:42 < arubi> that - and some folks probably still need to send to p2pkh addresses 13:42 < belcher> i still have the opinion that that doesnt matter 13:42 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 13:43 < waxwing> belcher, can we add a big note at the start of the readme to redirect people? 13:43 < belcher> a note on /joinmarket/ ? yes good idea 13:43 < waxwing> we're going to do this merge soon by the looks of it. slight worry though that it might be a bit of a git(hub)-pain. hopefully not. 13:43 < belcher> thought if we'll move jm-cs to jm soon then it wont matter 13:43 < belcher> oh yes 13:43 < waxwing> i actually meant the readme of the repo 13:44 < waxwing> i *guess* people have to land on that, wherever they come from. mostly. 13:44 < belcher> also iv been thinking that having a develop branch separate from master is a bit pointless 13:45 < belcher> but thats a separate thing, one at a time 13:46 < waxwing> yeah, it's interesting. for jm-cs just went with master and releases, partly based on feedback from people here, who expected it to work like that. 13:46 < belcher> bitcoin core also just uses master 13:46 < waxwing> i kinda like the develop thing, but maybe it's a more relevant debate to have for bigger projects. 13:46 < belcher> develop seems to be useful if people regularly clone master instead of downloading releases 13:46 < waxwing> yes that seems to be the model that everyone here was expecting. not sure there's a 100% argument either way. 13:47 < waxwing> i tend to agree, i was convinced by that argument originally. 13:47 < belcher> btw i came up with a scheme for signing github releases 13:47 < belcher> those zip files 13:47 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 13:48 < waxwing> oh; that's annoying, but i guess that must be right, the zips themselves are not signed by anything. 13:48 < waxwing> zip is more relevant if we had any windows users, but i tend to think most give up because the install is such a pain. if it even works today. 13:48 < waxwing> hmm i guess occasionally non-windows users will use the zip, too 13:51 < belcher> i prefer zips or tars for stuff, seems like downloading a release would be more stable 13:51 < belcher> i always get zips or tars when downloading electrum on a live OS for example 13:51 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 13:52 < waxwing> yeah 13:53 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 13:55 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 240 seconds] 14:04 -!- madacool [~Thunderbi@181.56.216.44] has joined #joinmarket 14:05 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 14:05 -!- madacool is now known as madacol 14:07 < belcher> heres the procedure for signing github releases https://github.com/chris-belcher/electrum-personal-server/issues/10#issuecomment-386121030 14:07 < belcher> basically you clone master, use --show-signatures to check all the signatures are valid, then git reset to the release tag, then export the entire repo to a new directory without the .git files, then download the release zips and compare the two (they should be identical) 14:08 < waxwing> thing i'm wondering is, if someone is going to verify sigs on the zip/tar, they could just clone the repo and check the sigs on the code, what with it being non-binary. seems like less work (and the infrastructure's there already). maybe. 14:09 < belcher> if they cloned they'd get master, which may be less stable because its an unreleased work in progress 14:10 < belcher> they could do `git reset --hard v0.1.1` themselves i suppose 14:10 < belcher> downloading the .zip and the .zip.asc then verifying might be easier for some 14:10 < waxwing> belcher, yeah but you can checkout a tag and the tag is signed 14:11 < waxwing> well it shows up as signed on the website, daddy github told me it's safe :) 14:12 < arubi> you can extract the tar somewhere and run `GIT_DIR= git status` from within the extracted tar dir, it should say "working in clean tree" 14:12 < belcher> this also works https://xkcd.com/1181/ 14:13 < arubi> (assuming the git stuff is set to the same branch as the release) 14:15 < waxwing> belcher, lol love that one 14:15 < waxwing> arubi, huh interesting. and what does working in clean tree mean here, exactly, that all the hashes verify i guess? 14:15 -!- Giszmo [~leo@ip-54-237-219-201.nextelmovil.cl] has joined #joinmarket 14:16 < belcher> a few years ago i had an idea for a browser plugin that would auto-verify any PGP magic bytes it saw, and also auto-sign any forum posts you made 14:16 < arubi> right, files are the same exactly as in git 14:16 < belcher> so people using a forum could sign and verify every post, it would be secure against the forum owner editing their posts 14:17 < arubi> hopefully there aren't any remote execution stuff against pgp --verify being fed a signature and odd message :P 14:17 < belcher> hmm yes i didnt think of that 14:19 -!- madacool [~Thunderbi@181.56.216.44] has joined #joinmarket 14:19 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 14:19 -!- madacool is now known as madacol 14:23 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 14:24 < waxwing> sometimes see people using cheeky sub-1satoshi/byte fees .. and still getting through in next couple of blocks. 14:24 < waxwing> kinda wish they wouldn't though, don't be a cheapskate 14:24 < arubi> hehe, it's payback for asicboost :) 14:25 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 14:25 < belcher> electrum has a coded lower-bound of 1 sat/b :( 14:25 < belcher> fun fact that back when joinmarket had a hardcoded miner fee of 10000 satoshi, that worked out to around 4 sat/b 14:25 < belcher> so now we're paying less in bitcoin terms than back in 2015 14:26 < arubi> not bad 14:39 < belcher> hey so have a look at this https://github.com/chris-belcher/electrum-personal-server/releases/tag/v0.1.1 14:39 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 14:39 < belcher> you can get the zip and tar, and the signatures for those are right there too 14:40 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 14:40 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 14:48 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 14:48 < arubi> yep, verifies fine for me. false@email.com hah? :D 14:51 < belcher> what do you mean, thats my real email...? 14:52 < belcher> :P 14:52 < arubi> yea, I'm admin@gmail.com :) 14:52 -!- dx25 [~dx25@97.119.180.105] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 14:52 < belcher> its actually belcher@riseup.net but i know one day they could easily throw me off and i dont feel like updating my pgp key when that happens 14:53 < belcher> you can always send me a reddit pm or bitcointalk pm or put it on a pastebin and send via irc 14:53 < arubi> yep. makes sense. 15:45 -!- dx25 [~dx25@97.119.180.105] has joined #joinmarket 16:28 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 240 seconds] 16:31 -!- quitobro_ [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has joined #joinmarket 16:33 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Ping timeout: 248 seconds] 16:33 -!- quitobro_ is now known as quitobro 17:30 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 17:40 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 17:42 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 17:48 -!- madacol [~Thunderbi@181.56.216.44] has quit [Read error: Connection reset by peer] 17:50 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 18:34 -!- quitobro_ [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket 18:36 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has quit [Ping timeout: 264 seconds] 18:36 -!- quitobro_ is now known as quitobro 18:46 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 248 seconds] 19:15 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 19:35 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 260 seconds] 19:40 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 20:11 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 256 seconds] 20:30 -!- madacol [~Thunderbi@181.56.216.44] has joined #joinmarket 20:53 -!- Giszmo [~leo@ip-54-237-219-201.nextelmovil.cl] has quit [Read error: Connection reset by peer] 21:01 -!- AgoraRelay [~jmrelayfn@p5DE4A334.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds] 21:06 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Quit: quitobro] 21:10 -!- AgoraRelay [~jmrelayfn@p5DE4A5B6.dip0.t-ipconnect.de] has joined #joinmarket 21:13 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #joinmarket 22:19 -!- madacol [~Thunderbi@181.56.216.44] has quit [Ping timeout: 240 seconds] 23:13 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 268 seconds] 23:26 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket 23:58 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 240 seconds]