feat: Deduplicate localize method for Step.sol
#12
+40
−11
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
Upstream cannon directly embeds
PreimageKeyLib
methods to its step contract. By including library functions(which only holds internal methods), bytecodes oflocalize
method will be stored in step contract and called byJUMP
instruction.In asterisc's case, this change is nontrivial because entire
Step
method is implemented in yul. Previous PRs relied on duplication of implementation inside of STF code.I found a workaround; define wrapper method which calls
localize
method from the library. The compiler thinks this method is not used by anywhere when it is not declared as public method, so explicitly mark as public. After that, delegatecall the method, to preservemsg.sender
.However after finding this approach, It feels like it is overly complicated. Should we allow duplications and copy-paste
localize
implementation, by closing this PR?Is there any better method while deduplication?
Tests
EVM mode tests will cover this diff.
Additional context
Current dependencies on/for this PR:
Step.sol
#12 (this PR)