Feat: generate parameters for checkSignatures by referencing OperatorStateRetriever on-chain (forked in-repo) #460
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
Co-authored-by: Tomás Grüner <[email protected]>
refactor: import path refactor: rename format: forge fmt
ypatil12
merged commit 84fb838
into
Layr-Labs:local/on-chain-check-sigs
2 of 8 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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.
Motivation:
Computation of the parameters needed for signature verification is typically done through the Eigen go or rust services. However, the rust services are not reliable at the current moment and some projects might want to have signature verifications without having to rely on these services.
This PR aims to make the computation of the
NonSignerStakesAndSignatureparameter easier and accessible through implementing it inOperatorStateRetrievercontractModifications:
getNonSignerStakesAndSignaturetoOperatorStateRetrieverResult:
Computing the data necessary for performing signature verification is more accessible