--- Day changed Wed Mar 07 2018
00:51 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 264 seconds]     
00:52 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #joinmarket     
00:52 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host]     
00:52 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #joinmarket     
02:27 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has quit [Ping timeout: 268 seconds]     
02:41 -!- kunla [~kunla@bl10-85-39.dsl.telepac.pt] has joined #joinmarket     
02:44 -!- azizLIGHT [~azizLIGHT@unaffiliated/azizlight] has joined #joinmarket     
03:18 -!- kunla [~kunla@bl10-85-39.dsl.telepac.pt] has quit [Ping timeout: 264 seconds]     
03:27 -!- kunla [~kunla@83.223.241.247] has joined #joinmarket     
04:22 -!- beIcher [~user@unaffiliated/belcher] has joined #joinmarket     
04:24 -!- belcher_ [~user@unaffiliated/belcher] has quit [Ping timeout: 264 seconds]     
04:31 -!- belcher [~belcher@unaffiliated/belcher] has joined #joinmarket     
05:22 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket     
05:24 < quitobro> waxwing: i tried using `wallet-tool.py` with `-p` flag to dump private keys. i’m trying to import them into another fork of BTC wallet to claim an airdrop. however it doesn’t seem to be working as expected. is this the correct way to get the private keys associated with internal JM addresses at which coins are stored in the JM wallet?
05:26 < waxwing> well, it might depend on all sorts of things. for example, what the airdrop is, when the coins moved, which address type (p2pkh or p2sh/p2wpkh as per segwit version), what kind of wallet you imported into etc etc.
05:26 < waxwing> quitobro, ^
05:27 < quitobro> waxwing: importing into BTCP electrum
05:28 < waxwing> yes, know nothing about that one unfortunately (or perhaps fortunately, who knows). you might be able to get more info in #bitcoin-forks possibly.
05:30 < quitobro> waxwing: that said, the output from `wallet-tool.py -p` should be an exhaustive list of internal and exeternal private keys (recently used…?) by the JM wallet, right?
05:30 < quitobro> or am i missing something?
05:32 < waxwing> it'll display all keys for whatever wallet-tool addresses are displayed; there is also an option to display a key for a specific HD path (ie one address), -H iirc, which is a "noscan" method, i.e. it doesn't require syncing the wallet.
05:32 < waxwing> so by default it'll show keys for exactly the set of things that get displayed, which is basically the recently used ones, yeah
05:33 < waxwing> there's also a displayall option which'll show everything back to the start (probably unwise if you have a huge/old wallet)
05:33 < waxwing> whatever you do, be very careful, messing with private keys. consider moving all the coins out first.
05:33 < quitobro> waxwing: okay good suggestion. where is the ‘master’ HD private key at the top of the hierarchy?
05:34 < waxwing> which version? segwit or old version?
05:34 < quitobro> SW     
05:34 < waxwing> ok. you have options there. you can import into trezor, ledger, samourai or electrum directly.
05:34 < waxwing> because its BIP49
05:35 < waxwing> to get the master key, basically just get the seed which is an encoding of it. iirc it's "showseed" method.
05:35 < quitobro> ok great, thanks waxwing 
05:36 < waxwing> but also, if it's SW version, note that coins on that p2sh address will of course not show up if you take a mainnet private key and load it into other wallets, *if* they are assuming a non-segwit p2pkh address.
05:36 < waxwing> (i.e. a '1' address)
05:43 < quitobro> waxwing: do you mean BIP39 by any chance?
05:44 < quitobro> electrum prompting me about the wallet derivation, defaulting to m/44’/183’/0’ and offering three derivation methodologies: legacy BIP44, p2sh-segwit BIP49, and native-segwit BIP84. going to select BIP 49 :)
05:44 < waxwing> it's BIP39 for the seed phrase, and BIP49 for the HD path (thats the segwit version of BIP44)
05:44 < waxwing> yes that's it
05:45 < waxwing> one thing to bear in mind is, it's limited in electrum (not really with trezor): it only does one account (the 0 mixdepth)
05:45 < waxwing> iirc you can manually set up 5 wallets for each mixdepth (=account) using 0,..4 in the path
05:46 < quitobro> yea looks like i will have to create additional wallets
05:46 < waxwing> not exactly smooth, even if it works. you may also have to manually set a gap limit. JM wallets are unusual in that they often have large-ish gaps.
05:46 < waxwing> yeah i only tried it briefly to check that it worked for one mixdepth, with a smallish wallet. i *believe* you can do the above ^ though if you need to.
05:47 < waxwing> electrum used to support multiple accounts but they removed it, which was annoying. has to be different wallets now.
05:48 < quitobro> by the above u mean changing the last value in the HD path to others in the range {0 .. 4}’ right?
05:48 < waxwing> hang on let me check the path
05:49 < waxwing> m / purpose' / coin_type' / account' / change / address_index
05:49 < waxwing> so it's the third index that changes 0..4 (with ' for hardening)
05:49 < quitobro> right the 0’ in the original example u gave?
05:50 < waxwing> change m/49'/0'/0'/0 to m/49'/0'/1'/0 (that's external (last zero), first mixdepth (0')
05:51 < waxwing> well in electrum it'd be m/49'/0'/0' iirc (thats the whole account/mixdepth including change/non-change)
05:52 < quitobro> ok so when i import the seed the wallet fills in: m/49'/183'/0'
05:52 < quitobro> it’s detecting it’s the 183th account from the seed i take it?
05:52 < waxwing> no that 183 is wrong, that's the purpose field. see BIP49
05:52 < quitobro> ah ok
05:53 < waxwing> you can enter the path by hand but i think if you chose BIP49 it would do it right
05:53 < waxwing> sorry that's coin type not purpose
05:53 < quitobro> when i choose BIP49 it deafults to the one with 183 in it (m/49'/183'/0')
05:53 < quitobro> going to try m/49’/0’/0’
05:54 < waxwing> see here https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki#registered-coin-types
05:54 < waxwing> yes that's right
05:54 < quitobro> hey, got some balance!
05:54 < quitobro> nice!
05:54 < waxwing> ok i guess we'd have to ask electrum what 183 is
05:54 < quitobro> so now repeat for 0..4
05:54 < quitobro> e.g. m/49’/0’/1’ ?
05:54 < waxwing> doesn't surprise me that thomasv found a way to change it
05:54 < waxwing> yes     
05:54 < waxwing> etc     
05:54 < quitobro> great, thanks waxwing !
05:55 < waxwing> and for privacy we could do this with belcher 's electrum personal server once it's up and running
05:55 < waxwing> if it doesn't report the full balance you may look into changing the gap limit setting
05:56 < quitobro> ok     
05:58 < waxwing> the advice about moving coins before messing with forks still very much applies of course. so although this is a cool/fun thing to be able to do, it doesn't change that much.
05:59 < waxwing> i'd tend to just do sweeps, 1 per mixdepth, direct from joinmarket and then collect the list of private keys; but i guess whatever strategy you take it's not simple, and also has dangers.
06:00 < waxwing> (and i guess it should be said, if it's only because it's cool/fun that's not a good reason since there's a privacy loss even importing, because electrum servers see your queries)
07:14 -!- q-biq [q-biq@unaffiiliated/q-biq] has quit [Remote host closed the connection]     
07:21 -!- q-biq [q-biq@153.92.126.244] has joined #joinmarket     
07:21 -!- q-biq [q-biq@153.92.126.244] has quit [Changing host]     
07:21 -!- q-biq [q-biq@unaffiiliated/q-biq] has joined #joinmarket     
08:56 -!- kunla [~kunla@83.223.241.247] has quit [Ping timeout: 256 seconds]     
09:26 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #joinmarket     
11:21 -!- kunla [~kunla@81.193.53.189] has joined #joinmarket     
11:51 -!- quitobro_ [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket     
11:52 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Read error: Connection reset by peer]     
11:52 -!- quitobro_ is now known as quitobro     
12:17 -!- kunla [~kunla@81.193.53.189] has quit [Ping timeout: 260 seconds]     
12:20 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has joined #joinmarket     
12:47 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has quit [Ping timeout: 245 seconds]     
12:51 -!- kunla [~kunla@81.193.53.189] has joined #joinmarket     
13:09 -!- kunla [~kunla@81.193.53.189] has quit [Ping timeout: 260 seconds]     
13:12 -!- kunla [~kunla@81.193.53.189] has joined #joinmarket     
16:09 -!- kunla [~kunla@81.193.53.189] has quit [Ping timeout: 256 seconds]     
16:57 < Anduck> waxwing: https://anduck.net/bitcoin/fees/ now on new server, shouldnt lag anymore
16:57 < Anduck> still fixing some minor issues
17:13 -!- takamatsu [~takamatsu@unaffiliated/takamatsu] has quit [Ping timeout: 256 seconds]     
18:08 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]     
20:02 < quitobro> waxwing: what did you mean by this? “i'd tend to just do sweeps, 1 per mixdepth, direct from joinmarket and then collect the list of private keys; but i guess whatever strategy you take it's not simple, and also has dangers.”
20:03 < quitobro> what is the sweep operation you’re referring to?
20:03 < quitobro> or do you just mean, sweep the coins out before trying any of this PK dump stuff
20:03 < quitobro> and *then*, subsequently, dump the list of JM private keys (via the `wallet-tool.py -p` flag, right?)
20:04 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has left #joinmarket []     
20:04 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #joinmarket     
20:44 -!- Relay-Free-Agora [~jmrelayfn@p5DE4A135.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]     
20:56 -!- Relay-Free-Agora [~jmrelayfn@p5DE4A799.dip0.t-ipconnect.de] has joined #joinmarket     
22:13 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Quit: quitobro]