@metamask/key-tree - npm Package Versions

[9.1.2]

Changed

• Bump @metamask/utils from ^8.3.0 to ^9.0.0 (#181)

[9.1.1]

Fixed

• Fix ESM imports (#177)

[9.1.0]

Added

• Add support for Cardano key derivation according to CIP3-Icarus (#158, #170, #171, #172)
• Export getBIP44CoinTypeToAddressPathTuple function (#173)

Changed

• Replace @noble/ed25519 and @noble/secp256k1 with @noble/curves (#154)
• Bump several MetaMask dependencies (#151, #165, #167)

[9.0.0]

Changed

• BREAKING: Disallow importing from ./dist paths (#147)
• Export mnemonicPhraseToBytes and createBip39KeyFromSeed (#149)

Fixed

• Add support for Node.js with ESM (#147)
• Remove postinstall script (#146)
  • This caused installation to fail.

[8.0.0]

Changed

• BREAKING: Build the package as both CJS and ESM (#140)
  • Distribution files have been moved from dist to dist/cjs (and dist/esm). If you are explicitly importing from dist, you have to update the import.
• Bump @metamask/utils to 6.2.0 (#140)

[7.1.1]

Fixed

• Fix isValidBIP32PathSegment to correctly check if BIP-32 path segment is <= 2^31-1 (#134)

[7.1.0]

Added

• Add isValidBIP32PathSegment function (#131)

Changed

• Bump @metamask/utils to 6.0.1 (#132)

[7.0.0]

Added

• BREAKING: Add SLIP-10 (slip10:) path type (#124)
  • bip32: can no longer be used to derive ed25519 keys

Changed

• Handle errors when resulting public or private key is invalid (#120)
  • Rather than throwing an error, a new key will be derived instead, as per the SLIP-10 or BIP-32 specification
• Improve extended key validation (#121)
• Validate that master private key and seed are within bounds (#118)
• Allow zero private key for ed25519 (#122)
  • Previously a zero private key 0x000..000 would be rejected when using ed25519, but all private keys are valid for ed25519

[6.2.1]

Fixed

• Add missing curve parameter (#110)
  • This fixes a bug introduced in 6.2.0, when using the ed25519 curve.

[6.2.0]

Added

• Accept BIP-39 secret recovery phrase as Uint8Array (#107)
  • Secret recovery phrases are now accepted both as a string in the bip39:... format, and as Uint8Array in the format used by @metamask/scure-bip39, in all functions that accept secret recovery phrases.