fix : ConfigEngine redeploy for XLayer#1
Open
Kogaroshi wants to merge 2 commits into
Open
Conversation
| vm.createSelectFork(vm.rpcUrl("xLayer")); | ||
| } | ||
|
|
||
| function test_newEngineMatchesLive() public { |
Member
There was a problem hiding this comment.
could you do this fork test against the new deployed version pls
DhairyaSethi
approved these changes
Apr 27, 2026
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
2 participants
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.
Previous ConfigEngine : 0x2eb21BCE2C5D59a67C648BfD2e700AdDB752DD7B
New ConfigEngine : 0x29A9b0a13c81d59f13BA0f39DBDCAA1AB2adc95F
ConfigEngine redeployed with initialy deployed aToken and vToken implementation instead of the newly deployed ones during v3.7 upgrade (due to CREATE/CREATE2 mismatch on XLayer initial deploy and v3.7 upgrade)