Thomas Kerin

Are you running master? I think you can pass in your own Base58ExtendedKeySerializer into HierarchicalKeyFactory now, adding support to fromExtended for zpubs/ypubs toExtended sucks, and I really should have made...

I hadn't fully realized the way forward for you at the time, but once you don't use prefixes that conflict, if you want a consistent codepath for serializing xpubs, Zpubs,...

Hey, thanks for the issue. at a glace the code looks good. there's some weird quirks in coinbin (if a p2sh tx is completely unsigned, you need to use the...

Hi @U77bna - I think that was the trick, for P2SH anyway (not sure about P2WSH). Sorry I don't have any more info - it's been years since I've used...

Oh wow. this is interesting, thanks for for the report. Do you have sample code of what you were doing when you got ParserOutOfRange?

Just thinking about it, you shouldn't have to parse a hierarchical key when deriving from a mnemonic? I'll try find time to look into this. It's also polite to give...

I took a quick look - it looks like that project reimplemented the extended key -> base58 encoding themselves, and when the result is passed to bitcoin-php it rejects it...

Ah I see. Hmm, yea it can do bip32! Assuming hdKey is the root key you'd do `$hdKey->derivePath("44'/80'/0'/0'")` These might help https://github.com/Bit-Wasp/bitcoin-php/blob/1.0/examples/bip32.php https://github.com/Bit-Wasp/bitcoin-php/blob/1.0/examples/trezor.bip32.php

Yea I suppose its a difference to older versions. It didn't make much sense to accept absolute paths for non-root nodes. The old code was too flexible, and I'm pretty...

> regarding m/M... m is for xprv, and M is for xpub, yes? source yep! > Do any wallets actually enforce that? In my wanderings, I've seen m used for...