hexlify is padding the number with 0s

[mohamedmansour]

Hello I have a number:

const block = 66812
const blockInHex = utils.hexlify(blockNumber)

blockInHex becomes 0x0104fc, while it should be 0x104fc by adding that extra 0, Geth's hexutil.Uint64 errors out

Error: invalid argument 0: json: cannot unmarshal hex number with leading zero digits into Go value of type hexutil.Uint64
        at web3.js:6357:37(47)
        at web3.js:5091:62(37)
        at <eval>:1:13(5)

How do we strip out leading 0's from hex?

mohamedmansour/ethereum-burn-stats#7

[mohamedmansour]

To mitigate, I am resorting to non ethers hex by converting to number and running using 0x${blockNumber.toString(16)}

[ricmoo]

While block numbers cannot be negative, keep in mind this is generally not adequate to convert values to QUANTITY values, since this will create invalid strings for negative numbers. See the hexValue function mentioned in the other answer. :)

[ricmoo]

The utils.hexValue(hexString) method will serialize as a QUANTITY, which has. I leading 0’s except that 0 is 0x0. This should be what you want.

The safest way to handle this is hexValue(BigNumber.from(v).toHexString()). This will handle all sorts of edge cases for you. :)

[ricmoo]

(hexlify will always return a hex representation of a series of bytes, so it is always of even length, which is why it has a leading 0)

[yuanoook]

I had an issue with hardhat hardhat_mine with ethers.utils.hexlify

InvalidArgumentsError: Errors encountered in param 1: Invalid value "0x01" supplied to : QUANTITY | undefined.

ethers.utils.hexStripZeros solved my problem.