@metamask/eth-sig-util - npm Package Versions

[5.0.1]

Fixed

• Fix issue introduced in v5.0.0 where the method encodeField encoded fields typed as bytes and passed as hexstrings were encoded differently than previous versions (#271, #274)

[5.0.0] [DEPRECATED]

Changed

• BREAKING: Removed support for Node v12 in favor of v14 (#137)
• Replace heavy crypto packages for lighter noble implementations via upgrading ethereumjs-util to latest (now called @ethereumjs/util) (#260)
• Migrate to Yarn 3 (#264)

[4.0.1]

Fixed

• Fix mistake in TYPED_MESSAGE_SCHEMA (#243)
  • The schema changed in v4 in a way that accidentally disallowed "reference types" (i.e. custom types) apart from the primary type. Reference types are now once again allowed.

[4.0.0]

Added

• BREAKING: Add subpath exports (#214, #211)
  • This is breaking because it prevents the import of modules that are not exposed as subpath exports.
• Add salt to the EIP-712 domain type (#176)
• Add additional unit tests (#146, #164, #167, #169, #172, #177, #180, #170, #171, #178, #173, #182, #184, #185, #187)
• Improve documentation (#157, #177, #174, #180, #178, #181, #186, #212, #207, #213)

Changed

• BREAKING: Consolidate signTypedData and recoverTypedSignature functions (#156)
  • The functions signTypedDataLegacy, signTypedData, and signTypedData_v4 have been replaced with a single signTypedData function with a version parameter. The version parameter determines which type of signature you get.
    • If you used signTypedDataLegacy, switch to signTypedData with the version V1.
    • If you used signTypedData, switch to signTypedData with the version V3.
    • If you used signTypedData_v4, switch to signTypedData with the version V4.
  • The functions recoverTypedSignatureLegacy, recoverTypedSignature, and recoverTypedSignature_v4 have been replaced with a single recoverTypedSignature function.
    • If you used recoverTypedSignatureLegacy, switch to recoverTypedMessage with the version V1.
    • If you used recoverTypedMessage, switch to recoverTypedMessage with the version V3.
    • If you used recoverTypedSignature_v4, switch to recoverTypedMessage with the version V4.
• BREAKING: Rename TypedDataUtils.sign to TypedDataUtils.eip712Hash (#104)
  • This function never actually signed anything. It just created a hash that was later signed. The new name better reflects what the function does.
• BREAKING: Move package under @metamask npm organization (#162)
  • Update your require and import statements to import @metamask/eth-sig-util rather than eth-sig-util.
• BREAKING: Simplify function type signatures (#198)
  • This is only a breaking change for TypeScript projects that were importing types used by the function signatures. The types should be far simpler now.
  • The TypedData has been updated to be more restrictive (it only allows valid typed data now), and it was renamed to TypedDataV1
• BREAKING: Replace MsgParams parameters with "options" parameters (#204)
  • This affects the following functions:
    • personalSign
    • recoverPersonalSignature
    • extractPublicKey
    • encrypt
    • encryptSafely
    • decrypt
    • decryptSafely
    • signTypedData
    • recoverTypedSignature
  • All parameters are passed in as a single "options" object now, instead of the MsgParams type that was used for most of these functions previously. Read each function signature carefully to ensure you are correctly passing in parameters.
  • personalSign example:
    • Previously it was called like this: personalSign(privateKey, { data })
    • Now it is called like this: personalSign({ privateKey, data })
• BREAKING: Rename Version type to SignTypedDataVersion (#218)
• BREAKING: Rename EIP712TypedData type to TypedDataV1Field (#218)
• Add signTypedData version validation (#201)
• Add validation to check that parameters aren't nullish (#205)
• Enable inline sourcemaps (#159)
• Update ethereumjs-util to v6 (#138, #195)
• Allow TypedDataUtils functions to be called unbound (#152)
• Update minimum tweetnacl-util version (#155)
• Add Solidity types to JSON schema for signTypedData (#189)
• Replace README API docs with generated docs (#213)