BigNumber.toHexString() has a 0 prefix, padding to even length

[HikariShine]

Note: Not all sections may be relevant, but please be as thorough while remaining concise as possible. Remove this Notice and any sections that don't feel pertinent.

If you are unsure if something is a bug, start a thread in the "discussions" tab above..

Describe the bug
ethers.utils.parseEther("0.10000000000000025").toHexString()

the result is 0x016345785d8a00fa, seems like padding to even length.

but when i use await provider.send("debug_traceCall", tx) to send tx manual, it caused

{"code":-32602,"message":"invalid argument 0: json: cannot unmarshal hex number with leading zero digits into Go struct field CallArgs.value of type *hexutil.Big"}

I think the return value of bigNumber.toHexString is no need to padding to even length, or is there some method to remove the 0 prefix?

[ricmoo]

The .toHexString returns a bytes representation, which is always even lengthed, and is by design, as it simplifies most interaction with other components which require a valid BytesLike.

The JSON-RPC protocols use "quantity" values, which is what the utils.hexValue function does; when talking to any protocol which requires a quantity value that method should be used.

[ricmoo]

(Note; the logic is a bit more complex than just trimming off the extra 0 though, since 0x0 Is a valid quantity. ;))

[HikariShine]

very good, thanks~