-
Notifications
You must be signed in to change notification settings - Fork 576
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BEP-151: Decommission Decentralized Exchange on BNB Beacon Chain (#151)
BEP-151: Decommission Decentralized Exchange on BNB Beacon Chain
- Loading branch information
1 parent
6440376
commit dd55e6e
Showing
2 changed files
with
36 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# BEP-151: Decommission Decentralized Exchange on BNB Beacon Chain | ||
|
||
## 1. Summary | ||
This BEP proposes to securely and smoothly decommission the build-in decentralized exchange on BNB Beacon Chain. | ||
|
||
## 2. Abstract | ||
BNB Beacon Chain’s primary focus, its native decentralized application ("dApp") BNB DEX, has demonstrated its low-latency matching with large capacity headroom. With the development of BNB Smart Chain and AMM-based decentralized exchanges running well on it, BNB DEX has less usage and liquidity. After implementing this BEP, the DEX module will be disabled, which will give Beacon Chain more computing power for the future computing and governance focuses. | ||
|
||
## 3. Status | ||
Draft | ||
|
||
## 4. Motivation | ||
BNB Beacon Chain(BC) is a blockchain developed by the BNB Chain community that implements a vision of a decentralized exchange (DEX) for digital assets. The heart of Beacon Chain is a highly performant matching engine built on distributed consensus that aims to replicate the < 1 second trading efficiency of current centralized exchanges. | ||
|
||
Since BNB Smart Chain's(BSC) launch to mainnet in 2020, the AMM based decentralized exchanges gain great success on BSC which even steal the thunder of order-book based DEX on BC. BC and BSC is a dual chain structure, with the evolution of this structure, BC plays more like a Beacon Chain that helps to enhance the security of BSC as a staking and governance layer. It is not suitable for a Beacon Chain to sustain a high-performance DEX any longer, especially when there is another DEX with massive adoption in the same ecosystem. | ||
|
||
Decommissioning the DEX module will reduce the need for system resources significantly for both validators and full nodes. The demand for liquidation can be fulfilled by BNB Smart Chain or the upcoming zkBAS. | ||
|
||
## 5. Specification | ||
After the implementation of this BEP, transactions related to DEX(including `NewOrderMsg`, `ListMsg`, `ListMiniMsg`) will return an error to disable listing new trading pairs or placing any new orders. | ||
All the existing orders will be canceled either by traders or by 3 days timeout(or 30 days for orders in the best 500 price levels, according to [BEP-67](https://github.com/bnb-chain/BEPs/blob/master/BEP67.md)). Thus there will be no more DEX transactions on Beacon Chain. | ||
|
||
### 5.1 Safety | ||
After the implementation of this BEP, there will be no more new orders. | ||
The existing orders which are not matched yet will not be matched anymore. | ||
They can be canceled by the traders directly or by timeout automatically after a period of time, and refunded to the traders. | ||
All the funds are SAFU. | ||
|
||
### 5.2 Impact | ||
Transactions `MsgSubmitProposal` with type of `ProposalTypeListTradingPair` or `ProposalTypeDelistTradingPair` are used for submitting proposals to list new trading pairs or delist trading pairs. | ||
|
||
They might be not useful any longer but still valid after the BEP. It's not encouraged to send these transactions anymore. | ||
|
||
## 6. License | ||
The content is licensed under [CC0](https://creativecommons.org/publicdomain/zero/1.0/). |
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
dd55e6e
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.
0x2A9D4AE3DaF452DF163aD783bAD44c47B7dA7063
dd55e6e
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.
جيد
dd55e6e
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.
??
dd55e6e
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.
0x270e447046190c0f095364b094f8daaba3d2832b
dd55e6e
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.
0x27b7393F51bA51449b423C046d25E0C392332FB3
dd55e6e
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.
0x27b7393F51bA51449b423C046d25E0C392332FB3
dd55e6e
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.
0x27b7393F51bA51449b423C046d25E0C392332FB3