chore(perp): bump revm pin to 20c375ba (perpdex tip + disable DASigners 0x1000) - #28
Merged
MiniFrenchBread merged 1 commit intoAug 3, 2026
Conversation
…e DASigners 0x1000) Pulls in the 14 unconsumed revm perpdex commits (batch orders, D3/#A/#B perf work, write-site balance events) plus revm PR 0gfoundation#7: DASigners (0x1000) is no longer registered as a stateful precompile, so calls to it behave as calls to an empty account. WA0GIBase (0x1002) and PerpDEX (0x1003) are unaffected.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Bumps the 11
[patch.crates-io]revm pins from448c29ceto20c375ba(current revmperpdexHEAD). This brings in:Note: the revm delta includes chain-state/ABI breaking perp changes, so existing perpdex devnet state needs a wipe.
Verification
cargo check -p rethpasses against the pinned rev.cargo test -p revm-precompile304 passed, including a new guard test asserting 0x1000 is unregistered for every spec while 0x1002/0x1003 remain.