Have a look at the KeyChainGroupStructure class. You can define the paths for P2PKH and P2WPKH chains there, and then pass it into the various method variants that use a KeyChainGroupStructure. It's kind of a replacement for the single path you could provide before 0.15.
By default, bitcoinj is using m/0H/[0,1] for P2PKH [external,internal] and m/1H/[0,1] for P2WPKH [external,internal]. Bitcoinj has skipped P2SH-P2WPKH, so I recommend using P2WPKH for modern wallets and keep P2PKH as a fallback for compatibility. The BIPs you mentioned don't fit well with the assumptions bitcoinj makes. For example, bitcoinj only supports Bitcoin so the coin_type field is of limited use. Also, the Wallet class doesn't have the notion of "accounts" (by design). On 07/04/2019 22.57, parm.sing...@gmail.com wrote: > Hi, > > We are using bip 44 for address generation. Are we going to have > multiple derivation schemes and keep the same seed but change purpose > field to 49 for P2WPKH-nested-in-P2SH and 84 for P2WPKH? > > what is the migration path for bitcoinj? I have seen samurai wallet and > other using bip 49 and 84. https://github.com/Samourai-Wallet/ExtLibJ > > Thanks. > > -- > You received this message because you are subscribed to the Google > Groups "bitcoinj" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to bitcoinj+unsubscr...@googlegroups.com > <mailto:bitcoinj+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoinj+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
