Feat/7683/batch filler repayment#200
Merged
Merged
Conversation
Contributor
|
@kss-t1 |
Contributor
y no u unit test? |
evchip
reviewed
Sep 28, 2025
evchip
reviewed
Sep 28, 2025
evchip
reviewed
Sep 28, 2025
evchip
requested changes
Sep 28, 2025
evchip
left a comment
Contributor
There was a problem hiding this comment.
Found a few issues on first pass.
evchip
reviewed
Oct 7, 2025
evchip
approved these changes
Oct 7, 2025
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.
Description
Batch repayments for the 7683 intent fillers to optimize their gas costs.
Proofs of Readin a batch_transferTokenOutcallsAlso introduces generic batch proof verification to
xChainRead.Functionality of processing a PoRs one by one was unchanged.
Motivation and Context
We want to beat bridging prices of our competition, so we want to show best profitability for solvers. Hence the gas optimization.
How Has This Been Tested?
Unit test which confirms correctness and gas savings. In the unit test, a simple Merkle Trie implementation was used to create Merkle Trie.
Types of changes (remove all unchecked types)
Checklist: