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 from84'/...?Or for
wsh(pkh(xpub...))is it49'/...? Or ought to we not assume that?
