feat: implement BEP-333(BNB Chain Fusion) #1003
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
* feat: disable msgs * fix: update dep * fix: check unlock timelock error * feat: implement airdrop approval msg * fix: sign data of AirDropApproval * fix: enforce the eth address to hex format * refactor * fix: remove tokenIndex for airdrop approval * fix comments * fix: reuse codes * fix: enforce recipient address to lower case when signing data to be compatible with the contract * fix: rename airdrop to token-recover * fix: update cosmos-sdk * fix: incorrect behavior for refund swap * fix: comments * fix: lint error * fix: swapIterator
* feat: add Sunset hardfork config * fix: nil pointer when doing ibc method in endblock
* fix: format refound logs and skip skip the processed swap * chore: update cosmos-sdk * chore: update cosmos-sdk * chore: update cosmos-sdk * fix: SetLatestProcessedRefundSwapKey out of loop * chore: update cosmos-sdk * chore: update cosmos-sdk * revert: skip processed swap * chore: update cosmos-sdk * chore: update cosmos-sdk
* feat: add `MsgSideChainStakeMigration` and `StakeMigrationApp` * fix review comments * go mod tidy * update fee param for `MsgSideChainStakeMigration` * update go.mod
* chore: update cosmos-sdk to fix refundStake issue * chore: update cosmos-sdk * chore: update cosmos-sdk
|
11 |
* feat: implement sign-validator-ownership cmd * fix: add 0x prefix to the sig output
|
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## develop #1003 +/- ##
===========================================
- Coverage 49.08% 47.87% -1.22%
===========================================
Files 127 127
Lines 12703 12822 +119
===========================================
- Hits 6235 6138 -97
- Misses 6044 6249 +205
- Partials 424 435 +11 ☔ View full report in Codecov by Sentry. |
* chore: update cosmos-sdk * chore: fix testcase * fix: remove bep159 ut
unclezoro
approved these changes
Feb 26, 2024
4 tasks
unclezoro
added a commit
that referenced
this pull request
Feb 28, 2024
feat: implement BEP-333(BNB Chain Fusion) (#1003)
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
Implement the functions for the
BC-Fusionplan.The Beacon Chain in the
BC-Fusionplan consists of four stages:FirstSunsetFork - Disable Certain Message Types:
In this stage, the system will disable specific message types to prevent users from creating additional assets on the Beacon Chain. The following
Msgswill be disabled:MsgSideChainStakeMigrationwill be enabled to allow users to redelegate tokens to BSC.MsgSideChainSubmitProposalwill be disabled after the SideChain Total Voting Power falls below 5M BNB.SecondSunsetFork - Token Refunding:
During this stage, the system will process token refunds for users who have assets locked on the Beacon Chain. Refunds will be initiated for TimeLock, AtomicSwap, and
Delegationon the side chain.MsgSideChainUndelegateon the Beacon Chain will be disabled to prevent undelegation and ensure system efficiency.FinalSunsetFork - Closure of Cross-Chain Channels:
This marks the final stage of
BC-Fusion. The system will close all cross-chain channels. After theFinalSunsetFork, the system will no longer support cross-chain transactions.Token Migration:
After the
FinalSunsetFork, users may still have assets on the Beacon Chain. The system will support token migration, allowing users to move their assets to BSC. For detailed instructions, please refer to BEP-299.Rationale
For the reasoning behind this plan, refer to BEP-333.
Example
n/a
Notable Changes