@metamask/key-tree
Advanced tools
Changelog
[7.0.0]
slip10:
) path type (#124)
bip32:
can no longer be used to derive ed25519 keysed25519
(#122)
0x000..000
would be rejected when using ed25519, but all private keys are valid for ed25519Changelog
[6.2.0]
bip39:...
format, and as Uint8Array
in the format used by @metamask/scure-bip39
, in all functions that accept secret recovery phrases.Changelog
[6.1.0]
@scure/bip39
to MetaMask fork version @metamask/scure-bip39
(#101)
@metamask/scure-bip39
fork accepts secret recovery phrases in Uint8Array
format making it possible to use more secure patterns of passing secret recovery phrases around. This change is non-breaking however, as the mnemonicToSeed
function used in this package still accepts secret recovery phrases in string format.Changelog
[6.0.0]
Buffer
with Bytes
or Uint8Array
(#84)
[...]Buffer
fields have been replaced with [...]Bytes
, e.g., BIP44Node.privateKeyBuffer
is now BIP44Node.privateKeyBytes
.BIP44Node.privateKey
.Buffer
s now return Uint8Array
s instead.Changelog
[4.0.0]
xpub
) and private (xprv
) keys (#58)SLIP10Node
class (#43, #37, #53)
@noble/*
suite of cryptography packages.change
and address_index
using BIP44CoinTypeNode
(#37)SLIP10Node
(or child class) object from derivation functions..from(...)
method. This is because some cryptographic dependencies are async.