What are legitimate BIP32 model bytes in descriptors & optionally available key origin defaults?

on

|

views

and

comments


BIP49 & BIP84 outlined totally different BIP32 model bytes in order that serialized xpubs begin with ypub/zpub/upub/vpub.

This led to some incompatibility up to now with wallets and libraries that used (or did not) these model bytes.

  • Do descriptors lastly eliminate totally different model bytes?

  • For instance, is wpkh([d34db33f/84'/0'/0']zpub...) not legitimate? (word the zpub string)

  • Additionally, since key origin info is optionally available in descriptors, are there default derivation paths or are they alleged to be undefined?

    For instance, in an prolonged descriptor with out optionally available key origin comparable to this one: wpkh(xpub...), can we assume its derivation path begins from 84'/...?

    Or for wsh(pkh(xpub...)) is it 49'/...? Or ought to we not assume that?

Share this
Tags

Must-read

Waymo raises $16bn to gas international robotaxi enlargement | Know-how

Self-driving automobile firm Waymo on Monday stated it raised $16bn in a funding spherical that valued the Alphabet subsidiary at $126bn.Waymo co-chief executives...

Self-driving taxis are coming to London – ought to we be anxious? | Jack Stilgoe

At the top of the nineteenth century, the world’s main cities had an issue. The streets had been flooded with manure, the unintended...

US regulators open inquiry into Waymo self-driving automobile that struck youngster in California | Expertise

The US’s federal transportation regulator stated Thursday it had opened an investigation after a Waymo self-driving car struck a toddler close to an...

Recent articles

More like this

LEAVE A REPLY

Please enter your comment!
Please enter your name here