Repository navigation
fix(trust): range-restrict solidityMappingSlot_injective (unrestricted form is inconsistent) #2460
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
7ce0be9
WIP: range-restrict solidityMappingSlot_injective
Th0rgal b3087ea
WIP: propagate range hypotheses to storage coherence callers
Th0rgal 60ffaed
WIP: range hypotheses through MappingCoherentAllKeys
Th0rgal c60c7b2
WIP: OwnedCounter range certificate, regenerate PrintAxioms
Th0rgal c62b601
WIP: document range-restricted mapping-slot axiom
Th0rgal 313317b
docs: range restriction and MappingBasesInRange in AXIOMS / TRUST_ASS…
Th0rgal 53f8ac3
chore: property manifest, exclusions and doc counts for mappingBasesI…
Th0rgal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even with these bounds, the axiom remains mathematically inconsistent: its domain contains
2^256 × 2^256 = 2^512(base, key)pairs, whilesolidityMappingSlot_lt_evmModulusproves that every result lies in a set of only2^256slots. The finite pigeonhole principle therefore guarantees two distinct bounded pairs with equal outputs, contradicting this axiom and allowingFalseto be derived. To restore soundness, collision assumptions must be limited to the finite pairs actually used (for example via explicit non-alias certificates), rather than universally quantifying over every bounded pair.Useful? React with 👍 / 👎.