FungibleStakedSui Implementation #18759
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
@0xripleys is attempting to deploy a commit to the Mysten Labs Team on Vercel. A member of the Team first needs to authorize it. |
0xripleys
force-pushed
the
fungible_stake_final
branch
from
e1c11a1
to
0337f98
Compare
0xripleys
force-pushed
the
fungible_stake_final
branch
from
84a33b6
to
03371e2
Compare
0xripleys
force-pushed
the
fungible_stake_final
branch
from
6e437b9
to
4b7d8e1
Compare
emmazzz
force-pushed
the
fungible_stake_final
branch
from
4b7d8e1
to
de5c4d5
Compare
|
Thanks a lot @0xripleys for keeping at it, and @emmazzz for reviewing the code! LGTM 🚀 |
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
Implementation for sui-foundation/sips#31
Test plan
Unit tests + random tests for the math
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.