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.
Fixes #303.
Bytes32
requires exactly 32 bytes), with the exception of integers. They will continue to accept values up to their quantity (e.g.0x1
will matchuint256
).Bytes65
was copied fromBytes512
and the bound was not updated. This has been resolved.uint256
where0x
matched validly. It's been updated to follow the same pattern matching as otheruint
sizes, requiring no leading zeros.BytesMax32
for use with storage keys. They don't quite fall within the domain ofuint256
(especially with the above fix) and they don't always serialize to 32 full bytes. This is the main issue in eth_getStorageAt spec ambiguity #303.