1 2017-06-09 13:02:26 <kekcoin> Hi, I created an address in `M/44/0/0/0/1`, using bitcoin-ruby, using this public key `xpub661MyMwAqRbcEuoAHNJCfb1hkyJgSekW1TtGfMzFv2dLdLb2ArMoajUYKvNVhJ1KGP9phqP856ephUPsVX9AutKQ3pN8wPWQvKqhwi4YeuT`. There’s already 4 confirmations, but I just can’t find it on electrum or in the blockchain (https://blockchain.info/xpub/xpub661MyMwAqRbcEuoAHNJCfb1hkyJgSekW1TtGfMzFv2dLdLb2ArMoajUYKvNVhJ1KGP9phqP856ephUPsVX9AutKQ3pN8wPWQvKqhwi4
 2 2017-06-09 13:34:40 <arubi> kekcoin, did you manually set up this path?
 3 2017-06-09 13:35:00 <arubi> bip44 has hardened derivation up to the accounts level, then it becomes non hardened
 4 2017-06-09 13:36:56 <arubi> I mean, I can the 1GwL5tatgxetFZCd7Dkivczzp5seXSZj5E address from that path, but it's not standard bip44
 5 2017-06-09 13:39:39 <arubi> you'd normally use m/44'/0'/0'/0'/0/1 and output the xpub at the last hardened 0', that way the watcher can generate all external and internal addresses for that account
 6 2017-06-09 13:41:16 <kekcoin> arubi: Yes, I setup it this way. I used the non-hardened version because I had to import the private key to the server
 7 2017-06-09 13:41:39 <arubi> not sure if I understand your reasoning
 8 2017-06-09 13:41:57 <arubi> why not use the xpub at the last hardened 0' and be bip44 compatible?
 9 2017-06-09 13:41:58 <kekcoin> Then I prefered to use the xpub for increased security
10 2017-06-09 13:42:17 <arubi> this is absolutely no security if you handle both xpubs and private keys
11 2017-06-09 13:42:54 <arubi> if one of the private keys at the lower levels leak, anyone could find the master xpriv
12 2017-06-09 13:42:55 <kekcoin> arubi: oh, then there's something wrong with the lib I'm using, when I try to use the hardened version, it gives me an error: "MoneyTree::Node::PrivatePublicMismatch: MoneyTree::Node::PrivatePublicMismatch "
13 2017-06-09 13:43:20 <arubi> not very descriptive :)
14 2017-06-09 13:44:13 <arubi> I'm betting you're just trying to do public derivation on a hardened path
15 2017-06-09 13:44:34 <kekcoin> https://pastebin.com/xe0FDXFF
16 2017-06-09 13:45:52 <arubi> I don't have any ruby stuff installed so I can't run it
17 2017-06-09 13:47:24 <kekcoin> should I be able to be bip44 compatible using only the xpub?
18 2017-06-09 13:48:05 <arubi> yes.  on the account level
19 2017-06-09 13:48:58 <arubi> so from your xpub's point of view, it only needs to branch to 0 for external addresses, and 1 for change addresses.  (increment a counter one more branch below)
20 2017-06-09 13:53:14 <kekcoin> weird, it'll always give me this error "MoneyTree::Node::PrivatePublicMismatch" when I try to use the hardened version
21 2017-06-09 13:53:39 <arubi> are you trying to do hard derivation with an xpub?
22 2017-06-09 13:53:44 <kekcoin> yes
23 2017-06-09 13:53:49 <arubi> you can't
24 2017-06-09 13:53:53 <arubi> you also don't need to
25 2017-06-09 13:54:16 <kekcoin> I see
26 2017-06-09 13:54:39 <arubi> m/44'/0'/0'/0'/0/1  <-  output the xpub at the third 0' from the left of the 44'
27 2017-06-09 13:55:04 <arubi> with that xpub you can branch to either /0 or /1 for payments\change addresses
28 2017-06-09 13:55:39 <arubi> so .../0/1..n are for payments and ../1/1..n are for change
29 2017-06-09 13:55:45 <kekcoin> the problem now is that I can't list this specific transaction on my electrum watch-only wallet
30 2017-06-09 13:56:00 <arubi> yea, because electrum uses bip44 :)
31 2017-06-09 13:56:53 <arubi> s/from the/to the ^
32 2017-06-09 13:58:45 <kekcoin> then I'm gonna have to use bip32
33 2017-06-09 13:59:12 <arubi> bip32 is the bip for HD.  you are using bip32
34 2017-06-09 13:59:24 <arubi> bip44 is a pathing bip, for using with bip32 HD
35 2017-06-09 13:59:46 <kekcoin> sorry, I did not express myself well
36 2017-06-09 13:59:56 <kekcoin> exactly
37 2017-06-09 14:00:40 <arubi> so yea, you can use just bare bip32, but bip44 helps you manage your payments \ change addresses so they're not together on the same path
38 2017-06-09 14:01:28 <arubi> plus it's supported by multiply wallets as watchonly..  from your POV, just use the last hardened bip44 path for an xpub, and branch from there
39 2017-06-09 14:02:59 <kekcoin> should I change my xpub in the script for an xpriv in order to use bip44?
40 2017-06-09 14:03:13 <arubi> not really no
41 2017-06-09 14:03:20 <arubi> do you have the master xpriv key?
42 2017-06-09 14:03:52 <arubi> the one at m/
43 2017-06-09 14:06:16 <kekcoin> arubi: nope
44 2017-06-09 14:07:13 <arubi> do you have any of the private keys..?
45 2017-06-09 14:07:27 <kekcoin> yes, m/0/0
46 2017-06-09 14:08:45 <arubi> alright, then you can go back to m and get the xpriv
47 2017-06-09 14:09:17 <arubi> I'm just asking so you can get your money back from that address.  this current key is not usable anymore
48 2017-06-09 14:10:37 <arubi> I don't know of any tools that can do that for you.  I can do it if you trust me not to steal your 0.0001 :)
49 2017-06-09 14:12:42 <kekcoin> I could give it to you if help me setup this gateway, if you don't mind
50 2017-06-09 14:13:00 <arubi> iyou mean pay me a dollar for dev work..?
51 2017-06-09 14:13:08 <arubi> $3 rather :)
52 2017-06-09 14:13:12 <kekcoin> In fact, just take some doubts from me haha
53 2017-06-09 14:14:58 <arubi> anyway, pass.  I have my own projects too :)
54 2017-06-09 14:16:52 <kekcoin> Thanks a lot for you time mate, I wish I could pay you that btc as a thank you
55 2017-06-09 14:17:37 <arubi> it's cool.  my advise is not to do anything live until you have it working on testnet
56 2017-06-09 14:20:35 <kekcoin> sounds better ;)
57 2017-06-09 15:04:52 <kekcoin> solved! I just had to pick the xpub at the account level, that is m/44/0/0 -> https://blockchain.info/xpub/xpub6DVjf26AoJYb4CFKKLVyEfxRuZNsYpSdL9aTftukZ5GQrh3G8UJjFKuNkLWjJCryrRxmRRpzaZcKKFJU4eahbweYT8xvMkRZapVKUo2e8S5
58 2017-06-09 15:05:11 <kekcoin> "account level", hehe
59 2017-06-09 15:46:05 <mol> kekcoin!