Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integer size restriction in StdLib.jsonSerialize #2498

Open
csmuller opened this issue Jun 7, 2021 · 1 comment
Open

Integer size restriction in StdLib.jsonSerialize #2498

csmuller opened this issue Jun 7, 2021 · 1 comment
Labels
discussion Initial issue state - proposed but not yet accepted

Comments

@csmuller
Copy link

csmuller commented Jun 7, 2021

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
@csmuller csmuller added the discussion Initial issue state - proposed but not yet accepted label Jun 7, 2021
@roman-khimov
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Initial issue state - proposed but not yet accepted
Projects
None yet
Development

No branches or pull requests

2 participants