allow contractAddress as an opt when initializing sleuth
#7
Conversation
This file contains 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.
Allow passing in
contractAddressmanually as an option when initializing Sleuth.The current implementation assumes a deterministic address for all chains - because it assumes the same deployer address is used with the same nonce (0).
While this was true for all chains so far, our deployment on Mantle used a nonce of 4 (we used a few transactions to get the native token), which led to the contract being deployed on a different address than the usual
0xC6a613FdaC3465D250DF7FF3CC21Bec86Eb8A372.On the client side we'd then make an exception for Mantle and pass in that new address as a flag.