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
[Supplier] Implement non-custodial staking #716
[Supplier] Implement non-custodial staking #716
Changes from 11 commits
a18ba42
676c2c4
b44e07b
3d01f53
bb84ab1
b33a013
604224d
79e4c39
473e047
088e675
428104b
20e8ed5
b543120
fdfd9b9
095571a
910c85b
1f26789
98b0446
8060f46
b887a0c
8121719
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.
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.
This is incorrect.
The operator can:
The owner can:
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.
I have added this restriction to simplify the
Supplier
management.Given that:
Changing the operator address mid-session would have the same effect as changing other service configs, which raises the need to delay the update til the next session.
The
OperatorAddress
is theSupplier
identifier, if the owner is allowed to change it, it would need to specify the oldOperatorAddress
so we would know which supplier to update when callingGetSupplier
(we actually have to delete then set theSupplier
entry in theSupplier
KVStore). Adding anold_operator_address
to the staking config file is far from ideal ux wise.Having the owner being able to update the
OwnerAddress
is fine though.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.
Let's make this clearer.
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.
Add one line making it clearer why operator address is immutable.
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.
Per this comment: #716 (comment)
Can you please evaluate if there is any difference with how it works in Morse?
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.
Looking directly into the code, these are the current differences.
Note that from reading the code, ther seems to be no code path that can update the operator address, since the message would contain a new validator address which would not be found when doing
k.GetValidator(ctx, validator.Address)
. I may be missing something though