chore: HyperEVM, ZkSync & Lens SpokePoolVerifier deployment #1112
Conversation
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
Signed-off-by: Faisal Usmani <[email protected]>
fusmanii
requested review from
bmzig,
mrice32,
nicholaspai and
pxrl
as code owners
Signed-off-by: Faisal Usmani <[email protected]>
fusmanii
changed the title
…isal/spoke-pool-verifer-zksync
Signed-off-by: Faisal Usmani <[email protected]>
grasphoper
approved these changes
Sep 29, 2025
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.
SpokePoolVerifierin all chainsSpokePoolVerifiercontract to both Lens & ZkSyncSpokePoolVerifiercontract to HyperEVMFYI: I deployed EVM version of
SpokePoolVerifierto both Lens & ZkSync but it should be fine since EVM and zkVM contract can call one anotherSample deposit: https://era.zksync.network/tx/0x5ad04b5014d208ed19d4bbbae10f80ecb62b6958a17561167247b0e79b332f2a
Corresponding fill: https://arbiscan.io/tx/0xcf83d0399970609e6dcba61f6ff2a8a453e240d08cef29e933730270eace46b2
Note: I used hardhat deployment as with foundry the create2 address was different