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.
Added contract integration and necessary environment variables. Going to refactor off-chain logic to submit data for pod activation (with EigenLayer's required verifyWithdrawalCredentials proof). Will likely also change general validator activation logic.
Validator activation in Casimir, which registers a validator with an SSV cluster to start payment and operations, should always precede validator activation on Beacon. Since EigenLayer requires a proof of a validator that has already been processed on Beacon, we'll use our oracle to watch for and activate validators in the
pending
Beacon state. This should also coincide with the validator's balance being detectable on Beacon, which should fix another existing issue in the Functions handlers that occurs when validators are deposited but their state is not yet detectable.