Update LiFi input and output settlers - #23
Draft
1kresh wants to merge 1 commit into
Draft
Conversation
1kresh
force-pushed
the
codex/update-lifi-settlers
branch
from
August 12, 2026 00:23
3a5bb69 to
22b04a8
Compare
1kresh
changed the title
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
1 participant
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.
Summary
Why
The LiFi executor deployment needs to target the new input and output settler contracts.
Impact
New deployments made with
DeployLifiExecutorScriptuse the updated settler contracts. Admin, ProxyAdmin owner, and caller configuration remain unchanged and continue to default to the deployment sender.Validation
forge buildforge test --isolate --no-match-path test/ReactorFork.t.sol(121 passed, 0 failed, 1 skipped)The excluded mainnet fork test depends on an external RPC that timed out during earlier verification.