Make VarInt to be restricted to u32 in length #46
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 is a quickfix for LNP-BP/client_side_validation#133 to make the things working before we will find a long-term solution at the type level.
For now, the guarantee that the problem doesn't happen elsewhere will be to test all strict types generated lib ids in all consensus repos against predefined constants (they are already in place) in
wasm32
-run tests.In terms of bitcoin consensus, there are no practical reasons to believe that bitcoin scripts or the number of tx inputs/outputs will ever exceed 4 billions per tx/script; so it Is safe. Anyway, with rust we can't do anything better.