chore(deps): bump ethereumjs-util from 7.0.7 to 7.0.9 in /packages/contracts

[dependabot]

Bumps ethereumjs-util from 7.0.7 to 7.0.9.

Release notes

Sourced from ethereumjs-util's releases.

v7.0.9 - Large ChainID Support

This release adds support for very high chainId numbers exceeding MAX_SAFE_INTEGER (an example is the chain ID 34180983699157880 used for the ephemeral Yolov3 testnet preparing for the berlin hardfork, but high chain IDs might be used for things like private test networks and the like as well).

Function signatures for methods in address and signature are therefore expanded to allow for a BNLike input type (BN | PrefixedHexString | number | Buffer) for chain ID related parameters.

All function signatures are still taking in a number input for backwards-compatibility reasons. If you use one of the following functions to implement generic use cases in your library where the chain ID is not yet known it is recommended to updated to one of the other input types (with plain Buffer likely be the most future-proof). Note that on some functions this changes the return value as well.

• account: toChecksumAddresss(hexAddress: string, eip1191ChainId?: number): string
  • -> toChecksumAddress = function(hexAddress: string, eip1191ChainId?: BNLike): string
• account: isValidChecksumAddress(hexAddress: string, eip1191ChainId?: number)
  • -> isValidChecksumAddress(hexAddress: string, eip1191ChainId?: BNLike)
• signature: ecsign(msgHash: Buffer, privateKey: Buffer, chainId?: number): ECDSASignature
  • -> ecsign(msgHash: Buffer, privateKey: Buffer, chainId?: number): ECDSASignature (return value stays the same on number input)
  • -> ecsign(msgHash: Buffer, privateKey: Buffer, chainId: BNLike): ECDSASignatureBuffer (changed return value for other type inputs)
• signature: ecrecover(msgHash: Buffer, v: number, r: Buffer, s: Buffer, chainId?: number): Buffer
  • -> ecrecover(msgHash: Buffer, v: BNLike, r: Buffer, s: Buffer, chainId?: BNLike): Buffer
• signature: toRpcSig(v: number, r: Buffer, s: Buffer, chainId?: number): string
  • -> toRpcSig(v: BNLike, r: Buffer, s: Buffer, chainId?: BNLike): string
• signature: isValidSignature(v: number, r: Buffer, s: Buffer, homesteadOrLater: boolean = true, chainId?: number)
  • -> isValidSignature(v: BNLike, r: Buffer, s: Buffer, homesteadOrLater: boolean = true, chainId?: BNLike)

v7.0.8 - Bugfix Release

• New Address.equals(address: Address) function for easier address equality comparions, PR #285
• Fixed a bug in fromRpcSig() in the signature module not working correctly for chain IDs greater than 110, PR #287

Changelog

Sourced from ethereumjs-util's changelog.

7.0.9 - 2021-03-04

This release adds support for very high chainId numbers exceeding MAX_SAFE_INTEGER (an example is the chain ID 34180983699157880 used for the ephemeral Yolov3 testnet preparing for the berlin hardfork, but high chain IDs might be used for things like private test networks and the like as well).

Function signatures for methods in address and signature are therefore expanded to allow for a BNLike input type (BN | PrefixedHexString | number | Buffer) for chain ID related parameters.

All function signatures are still taking in a number input for backwards-compatibility reasons. If you use one of the following functions to implement generic use cases in your library where the chain ID is not yet known it is recommended to updated to one of the other input types (with plain Buffer likely be the most future-proof). Note that on some functions this changes the return value as well.

• account: toChecksumAddresss(hexAddress: string, eip1191ChainId?: number): string
  • -> toChecksumAddress = function(hexAddress: string, eip1191ChainId?: BNLike): string
• account: isValidChecksumAddress(hexAddress: string, eip1191ChainId?: number)
  • -> isValidChecksumAddress(hexAddress: string, eip1191ChainId?: BNLike)
• signature: ecsign(msgHash: Buffer, privateKey: Buffer, chainId?: number): ECDSASignature
  • -> ecsign(msgHash: Buffer, privateKey: Buffer, chainId?: number): ECDSASignature (return value stays the same on number input)
  • -> ecsign(msgHash: Buffer, privateKey: Buffer, chainId: BNLike): ECDSASignatureBuffer (changed return value for other type inputs)
• signature: ecrecover(msgHash: Buffer, v: number, r: Buffer, s: Buffer, chainId?: number): Buffer
  • -> ecrecover(msgHash: Buffer, v: BNLike, r: Buffer, s: Buffer, chainId?: BNLike): Buffer
• signature: toRpcSig(v: number, r: Buffer, s: Buffer, chainId?: number): string
  • -> toRpcSig(v: BNLike, r: Buffer, s: Buffer, chainId?: BNLike): string
• signature: isValidSignature(v: number, r: Buffer, s: Buffer, homesteadOrLater: boolean = true, chainId?: number)
  • -> isValidSignature(v: BNLike, r: Buffer, s: Buffer, homesteadOrLater: boolean = true, chainId?: BNLike)

7.0.8 - 2021-02-01

• New Address.equals(address: Address) function for easier address equality comparions, PR #285
• Fixed a bug in fromRpcSig() in the signature module not working correctly for chain IDs greater than 110, PR #287

Commits

• b100d13 Merge pull request #293 from ethereumjs/new-release
• 9a3298e Bumped version to v7.0.9, added CHANGELOG entry
• 0ac965f Merge pull request #290 from ethereumjs/fix-ecrecover
• 46415c1 dev ex: remove lint from npm run test and add as a separate step to ci
• db4ee77 improve ecsign logic
• 059ce3b add tests for toType
• 243fd47 add toType helper with 0x-prefix and MAX_SAFE_INTEGER checks
• b3ba3ee Added BNLike input type for v and chain IDs in toRpcSig() and isValidSignatur...
• abe0aff Added BNLike input type for chain IDs in toChecksumAddress() and isValidCheck...
• 24279bf Limited ecsign v return value to Buffer on extended input types, additional i...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)