fix: use PlutusBytes to encode BigUInt/BigNInt #216
Merged
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.
Currently, BigU/NInt is encoded with
Bytes
which is just a wrapper around minicbor Bytes. But it should be usingPlutusBytes
, which supports this "if the bytestring is longer than 64 bytes then break up the bytestring into bytestrings of length 64 and put them into an indefinite byte string" pattern.