You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary or problem description
I'm just curious what the rationale is behind the restriction of integers to max 2^53-1 when serializing to JSON?
Specifically, the restriction became an issue when trying to json-serialize a UInt160 as an integer with StdLib.jsonSerialize(...).
Do you have any solution you want to propose?
Depends on the answers to the above question. What about 2^160-1?
Neo Version
Neo 3
The text was updated successfully, but these errors were encountered:
In some way it comes from RFC 7159, but at the same time given our use case with lots of huge integers this limit is well, too limiting, see #2082 and nspcc-dev/neofs-node#122 also.
Summary or problem description
I'm just curious what the rationale is behind the restriction of integers to max 2^53-1 when serializing to JSON?
Specifically, the restriction became an issue when trying to json-serialize a UInt160 as an integer with
StdLib.jsonSerialize(...)
.Do you have any solution you want to propose?
Depends on the answers to the above question. What about 2^160-1?
Neo Version
The text was updated successfully, but these errors were encountered: