-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[sui-system] Allow inactive StakedSui objects to be withdrawn immediately #18265
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@0xripleys is attempting to deploy a commit to the Mysten Labs Team on Vercel. A member of the Team first needs to authorize it. |
d72ee6a
to
b804e27
Compare
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.
Thanks for the PR! I will help with updating the snapshot files before merging it.
…tely (MystenLabs#18265) ## Description Allow inactive StakedSui objects to be withdrawn immediately Implementation for sui-foundation/sips#33 ## Test plan Wrote unit test to make sure the the functionality worked as expected. --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK: --------- Co-authored-by: Emma Zhong <[email protected]>
Description
Allow inactive StakedSui objects to be withdrawn immediately
Implementation for sui-foundation/sips#33
Test plan
Wrote unit test to make sure the the functionality worked as expected.
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.