Repository navigation
Conversation
because robinhood chain was complaining about it for some reason
bh2smith
reviewed
Oct 27, 2026
bh2smith
left a comment
There was a problem hiding this comment.
Looks good
cf mainnet deployment.
https://etherscan.io/address/0x04501b9b1D52e67f6862d157E00D13419D2D6E95#code
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.
it turns out the canonical ethflow deployment is at the 2nd nonce
1rather than0. So for a canonical deployment on a fresh chain, it is necessary to first burn the nonce.local build simulation:
Consideations
This doesn't work well for our current staging env which uses nonce 0, so probably the easiest way there is to transition ethflow to use nonce 1 there. Just requires deploying the new contract on every chain.