Add support for 256 bit JSON numbers (vs. strings), including scientific notation #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR relates to
firefly-common
PR hyperledger/firefly-common#147That PR introduces support for large JSON numbers where previously they would be limited to the size of
float64
2^64-1
. This is particularly useful when dealing with the scale of numeric parameters typical of Ethereum smart contracts. See PR hyperledger/firefly-common#147 for more information.This
firefly-signer
PR does 2 things:firefly-common
to utilize the new large number support1e+25
.