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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(executor): added MsgUpsertSequencer consensus message #1120
base: main
Are you sure you want to change the base?
feat(executor): added MsgUpsertSequencer consensus message #1120
Changes from all commits
ca7a5a4
e382846
c6639e7
336e3ca
9209ab6
d08e81b
45164f1
adb695c
f24ea2f
0fa4c8d
4b061ec
038a2a3
130d86c
102fa8e
dc2cafe
9f507a4
d55070b
ef2a708
f357f7d
08965fc
0f93728
ae84159
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 11 in block/produce.go
GitHub Actions / Analyze
Check failure on line 11 in block/produce.go
GitHub Actions / build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the initial
RewardAddress
, thesettlementAddr
is used. Do we need to include both in the consensus message? Is there a scenario where this message can carry two distinct addresses, one Operator and the other Reward address?Do I understand this correctly, to have a reward address different from the settlement addr, the custom reward address can be set on the rdk manually, in which case the
RewardAddrBytes
will not override it?I realize keeping the reward address in the Hub was decided against, but if we recognize the Hub's
x/sequencer
record to be the source of truth for the sequencer, then we could maybe consider that besides the settlement address, the (custom) reward address could also originate from the Hub's sequencer record. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding your last point. Yes, you are right. That's what we finally decided to do with Omri. We'll enrich the
rotation_started
event with all the information needed for the sequencer, ieRewardAddr
andWhitelistedRelayers
so far. And the hub will be the source of truth.Good point, probably we don't. But as i said above, this will be change anyway soon.
Currently,
RewardAddrBytes
overwrites the manually set value. Again, this will change once we accept that the Hub is the source of truce.