dApps staking v3 - part 1#155
Conversation
| }, | ||
| )?; | ||
|
|
||
| // TODO: might require some modification later on, like additional checks to ensure contract can be unregistered. |
There was a problem hiding this comment.
what are the scenarios in which contract can't be unregistered?
There was a problem hiding this comment.
What should be avoided is unregistering a contract while leaving storage items behind, forever.
So later on, when PR progresses more, this TODO is a reminder to revisit the issue (I don't have a clear solution for this yet).
shaunxw
left a comment
There was a problem hiding this comment.
Looks good in general!
I wonder why we are using DispatchResultWithPostInfo as the return type though there is no post info?
Thanks! For the |
|
All functionality intended for this PR has been implemented, and it's ready for final review 🙏 |
shaunxw
left a comment
There was a problem hiding this comment.
Looks good overall! Just some small issues.
Co-authored-by: Shaun Wang <spxwang@gmail.com>
Minimum allowed line rate is |
|
@shaunxw thanks for the approval! I was thinking, instead of merging it directly, to keep this in a 'live' branch. This would keep the review of PRs light(er), while also providing one big overview in the end, before everything is merged. |
|
Love this idea. It definitely helps with the review process. |
Pull Request Summary
First PR that will introduce part of dApps staking v3 functionality.
Overall implementation will be broken down into multiple PRs to make it easier for reviewers.
Part 1
After receiving first review, will amend the comments and implement extensive unit tests.
Check list