[Snyk] Upgrade @bitauth/libauth from 1.19.1 to 3.0.0

[snyk-io]

Snyk has created this PR to upgrade @bitauth/libauth from 1.19.1 to 3.0.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 15 versions ahead of your current version.

• The recommended version was released on 7 months ago.

Release notes

Package name: @bitauth/libauth

• 3.0.0 - 2024-04-10
  

  Major Changes

  • #127 e5c275f Thanks @ bitjson! - Add support for relative BIP32 derivation

    Relative BIP32 Hierarchical Deterministic (HD) derivation is now supported via the deriveHdPathRelative utility, and the Libauth compiler has been updated to explicitly use relative derivation by default for HdKeys. Absolute derivation has also been enhanced to validate the expected depth of provided HD keys.

    If you application relies on relative derivation but uses deriveHdPath, you'll need to switch to using the new deriveHdPathRelative, as absolute derivation will now fail if provided with a non-zero depth HD key.

    Fixes #49.

  • #127 e5c275f Thanks @ bitjson! - CashAssembly: .signature is now .ecdsa_signature

    All CashAssembly scripts using the .signature operation should instead call .ecdsa_signature or switch to .schnorr_signature.

    Additionally, signing_serialization.token_prefix is now available.

  • #127 e5c275f Thanks @ bitjson! - Unify object parameters and error handling across library

    A number of existing Libauth utilities have been modified to adhere to Libauth's object parameter and error handling conventions:

    • CashAddress utilities:
      • encodeCashAddress/decodeCashAddress
      • lockingBytecodeToCashAddress/cashAddressToLockingBytecode
      • encodeCashAddressFormat/decodeCashAddressFormat
    • BIP32 (HD Key) utilities:
      • crackHdPrivateNodeFromHdPublicNodeAndChildPrivateNode
      • decodeHdKey (decodeHdKeyUnchecked)
      • decodeHdPrivateKey/encodeHdPrivateKey
      • decodeHdPublicKey/encodeHdPrivateKey
      • deriveHdPath
      • deriveHdPathRelative
      • deriveHdPrivateNodeFromSeed
      • deriveHdPrivateNodeIdentifier/deriveHdPublicNodeIdentifier
      • deriveHdPrivateNodeChild/deriveHdPublicNodeChild
      • deriveHdPublicKey
      • deriveHdPublicNode
      • hdKeyVersionIsPrivateKey/hdKeyVersionIsPublicKey
      • hdPrivateKeyToIdentifier/hdPublicKeyToIdentifier
    • BIP39 (Mnemonic Phrase) Utilities:
      • deriveHdPrivateNodeFromBip39Mnemonic
      • deriveSeedFromBip39Mnemonic
      • encodeBip39Mnemonic/decodeBip39Mnemonic
      • generateBip39Mnemonic
    • Key Utilities:
      • generateDeterministicEntropy

    Please see the relevant guide(s) for usage examples:

    • Handling Errors
    • Keys
    • Addresses
    • Wallets & Transaction Creation

  Minor Changes

  • #127 e5c275f Thanks @ bitjson! - Add usage guides and API overview

  • #127 e5c275f Thanks @ bitjson! - Add P2PKH CashAddress utilities

    The following utilities are now available:

    • hdPrivateKeyToP2pkhLockingBytecode
    • hdPrivateKeyToP2pkhCashAddress
    • hdPublicKeyToP2pkhLockingBytecode
    • hdPublicKeyToP2pkhCashAddress
    • privateKeyToP2pkhLockingBytecode
    • privateKeyToP2pkhCashAddress
    • publicKeyToP2pkhLockingBytecode
    • publicKeyToP2pkhCashAddress

    For usage examples, see wallets.md.

  • #127 e5c275f Thanks @ bitjson! - Validate all keys prior to compilation, expose validateCompilationData

    The compiler now validates all compilation data (i.e. validate all public and private keys), prior to compilation, regardless of whether or not the offending public or private key material is used. This is intended to surface software defects (particularly in the software used by counterparties) as early as possible.

  • #127 e5c275f Thanks @ bitjson! - Add support for decodeTransactionOutputs

  Patch Changes

  • #127 e5c275f Thanks @ bitjson! - generateRandomBytes: always verify unique results across two runs

    Fixes #119. Old behavior is available at generateRandomBytesUnchecked.

• 2.1.0 - 2024-02-24
  

  Minor Changes

  • #117 8e032c2 Thanks @ jimtendo! - Add PBKDF2 and BIP39 Support

  Patch Changes

  • #117 51c7ee3 Thanks @ bitjson! - Use @ changesets/cli, remove standard-version
  • #117 7ddad21 Thanks @ bitjson! - Publish with provenance via GitHub Actions
• 2.1.0-beta.1 - 2024-02-23
  

  chore(release): 2.1.0-beta.1

• 2.1.0-beta.0 - 2024-02-23
  

  chore(release): 2.1.0-beta.0

• 2.0.0 - 2024-01-12
  No content.
• 2.0.0-alpha.9 - 2024-01-18
  

  chore(release): 2.0.0-alpha.9

• 2.0.0-alpha.8 - 2023-01-10
  

  chore(release): 2.0.0-alpha.8

• 2.0.0-alpha.7 - 2022-12-08
  

  chore(release): 2.0.0-alpha.7

• 2.0.0-alpha.6 - 2022-08-18
  

  chore(release): 2.0.0-alpha.6

• 2.0.0-alpha.5 - 2022-06-27
  

  chore(release): 2.0.0-alpha.5

• 2.0.0-alpha.4 - 2022-06-16
• 2.0.0-alpha.3 - 2022-05-20
• 2.0.0-alpha.2 - 2022-05-19
• 2.0.0-alpha.1 - 2022-05-19
• 2.0.0-alpha.0 - 2022-05-14
• 1.19.1 - 2022-02-01

from @bitauth/libauth GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs