feat: add challenger address to validators #103
Merged
Conversation
This file contains 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
forcodedancing
force-pushed
the
add_challenger_val
branch
from
643e968 to
f97a21f
Compare
forcodedancing
force-pushed
the
add_challenger_val
branch
from
7427672 to
30d23ad
Compare
unclezoro
approved these changes
Mar 20, 2023
|
LGTM |
This was referenced Mar 24, 2023
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
This pr will
challenger addressto validators. This address will be used for validators to submit data availability challenge attestations.relayer_bls_keytobls_key, for this key is shared by both relayer and challenger.Rationale
Off-chain
RelayerandChallengerservices currently use the same relayer address for submitting transactions.The nonce issue will be a obstacle for performance and could cause other issues.
Example
NA
Changes
Notable changes: