BIP49 (SegWit) derivation path about money-tree HOT 10 CLOSED

+1

from money-tree.

The owner of this repo still haven't merged the pull request. We are using in production for over a month, without any errors.

If you need this you can use my version, for now:

gem 'money-tree', git: 'https://github.com/NicosKaralis/money-tree'

from money-tree.

Guys, I've found a solution. ( #30 )

I've added the helpers to_p2wpkh_p2sh and convert_p2wpkh_p2sh so I can finally use the same extended key on my trezor and on my system

If you could, please help me test to see if there is a fringe case or anything that could cause a problem

from money-tree.

Having the same problem here.

If you go to https://iancoleman.github.io/bip39/ , go to the bip32 tab and use a custom derivation path you can see the same problem.

m/49'/0'/0'/0/0 generates the same problematic address, 1JNtziN11HdS4HXAMUJzF511R4Cza7EPqA

You have to check Use SegWit addresses (ie P2WPKH Nested In P2SH to actually see the SegWit enabled addresses (3HnFEPAxBpDfSMXNvKb3EgaBdkN89zc4gF )

So the real question is, what do we need to make money-tree generate segwit addresses?

from money-tree.

Ok good, so the question now is how do we do P2WPKH Nested In P2SH in money-tree? I would prefer if someone who know the specs better to jump in, but in worst case we have to fork the gem and try to find a way forward.

from money-tree.

we also struggle from this

from money-tree.

Yeah, this repo hasn't been updated to support bip49.
PRs welcome; I can't guarantee I'll be able to do this in any timeframe.

from money-tree.

from money-tree.

@krtschmr That depends on what you did. If you used this repo to derive a key and generate an address, then you can probably recover those funds as long as you still have the seed.
Just use this repo to derive the node at the path of the address with the stuck funds and get the private_hex -- you can import that in a traditional bitcoin wallet and send it normally.

from money-tree.

status?

from money-tree.