Can be an issue here as Json should only technically be able to safely represent integers up to 9007199254740991; then it would be float rounded

The Number.MAX_SAFE_INTEGER static data property represents the maximum safe integer in JavaScript (2^53 – 1).

Can be an issue here as Json should only technically be able to safely represent integers up to 9007199254740991; then it would be float rounded

The Number.MAX_SAFE_INTEGER static data property represents the maximum safe integer in JavaScript (2^53 – 1).

@benaadams why is that. I can understand that this is a deviation from the standard, but why cant it safely be transmitted that way and then decentralized with a deviation from the standard?

Javascript support is not really important here at all

txPoolContentWithMinTip

Any reason its not being passed as quoted hex which is standard for all large numbers?

txPoolContentWithMinTip

Any reason its not being passed as quoted hex which is standard for all large numbers?

Taiko did it this way

Can be an issue here as Json should only technically be able to safely represent integers up to 9007199254740991; then it would be float rounded

The Number.MAX_SAFE_INTEGER static data property represents the maximum safe integer in JavaScript (2^53 – 1).

JSON standard states the numbers can be of any precision, only constrained by implementation. Standard library handles up to max ulong, I'm trying to cover uint256 range additionally.