sov-timelock module#2798
Open
theodorebugnet wants to merge 15 commits intodevfrom
Open
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
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
Implements
sov-timelockfor timelock support.Main things to review:
TimelockCapablityintroduced in a previous PR has been simplified, since a single method makes the timelock state machine more ergonomic to use. Changes insov-modules-api/runtime/capabilities/timelock.rsandstf-blueprint/src/sequencer_mode/common.rs.sov-timelockmodule itself, main logic being in lib.rs and call.rs.sov-timelockstores timelocked proposals keyed by(Address, ProposalId). The ProposalId is a domain-separated hash so we can support both Runtime::Decodable callmessages, and separately arbitrary module-owned data; the latter is used insov-timelockto implement a timelock on theModifyCancellationPolicycallmessage.We also track the number of timelocks per user in a separate state item, to enforce the
MAX_PENDING_PROPOSALS_PER_ADDRESSupper bound.CHANGELOG.mdwith a new entry if my PR makes any breaking changes or fixes a bug. If my PR removes a feature or changes its behavior, I provide help for users on how to migrate to the new behavior.Cargo.tomlchanges before opening the PRs. (Are all new dependencies necessary? Is any module dependency leaked into the full-node (hint: it shouldn't)?)Linked Issues
Testing
Describe how these changes were tested. If you've added new features, have you added unit tests?
Docs
Describe where this code is documented. If it changes a documented interface, have the docs been updated?
Rendered docs are available at
https://sovlabs-ci-rustdoc-artifacts.us-east-1.amazonaws.com/<BRANCH_NAME>/index.html