Bump ethereumjs-util from 6.1.0 to 7.0.10

[dependabot-preview]

Bumps ethereumjs-util from 6.1.0 to 7.0.10.

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

v7.0.7 - Maintenance Release

• Removed stateRoot check for Account.isEmpty() to make emptiness check EIP-161 compliant, PR #279
• Added type AddressLike and helper bnToHex(), PR #279
• Added account.raw() which returns a Buffer Array of the raw Buffers for the account in order, PR #279

v7.0.6 - New Account Class

New Account class

This release adds a new Account class intended as a modern replacement for ethereumjs-account. It has a shape of Account(nonce?: BN, balance?: BN, stateRoot?: Buffer, codeHash?: Buffer).

Instantiation

The static factory methods assist in creating an Account object from varying data types: Object: fromAccountData, RLP: fromRlpSerializedAccount, and Array: fromValuesArray.

Methods: isEmpty(): boolean, isContract(): boolean, serialize(): Buffer

Example usage:

import { Account, BN } from 'ethereumjs-util'
const account = new Account(
new BN(0), // nonce, default: 0
new BN(10).pow(new BN(18)), // balance, default: 0
undefined, // stateRoot, default: KECCAK256_RLP (hash of RLP of null)
</tr></table>

... (truncated)

Changelog

Sourced from ethereumjs-util's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog (modification: no type change headlines) and this project adheres to Semantic Versioning.

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

7.0.7 - 2020-10-15

• Removed stateRoot check for Account.isEmpty() to make emptiness check EIP-161 compliant, PR #279
• Added type AddressLike and helper bnToHex(), PR #279
• Added account.raw() which returns a Buffer Array of the raw Buffers for the account in order, PR #279

[7.0.6] - 2020-10-07

New Account class

... (truncated)

Commits

• See full diff 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #381.