bep173: enable text proposal on BNB Smart Chain (#173)

BEP173.md

@@ -0,0 +1,100 @@
+
+# BEP-173: Introduce Text Governance Proposal for BNB Smart Chain
+
+- [BEP-173: Introduce Text Governance Proposal for BNB Smart Chain](https://github.com/bnb-chain/BEPs/pull/173)
+    - [1. Summary](#1-summary)
+    - [2. Status](#2-status)
+    - [3. Motivation](#3-motivation)
+    - [4. Specification](#4-specification)
+        - [4.1 Introduction](#41-introduction)
+        - [4.2 How to draft a text proposal](#42-how-to-draft-a-text-proposal)
+        - [4.3 Governance stage](#43-governance-stage)
+          - [4.3.1 Deposit stage](#431-deposit-stage)
+          - [4.3.2 Voting stage](#432-voting-stage)
+          - [4.3.3 Tallying stage](#433-tallying-stage)
+          - [4.3.4 Execution stage](#434-execution-stage)
+
+
+## 1. Summary
+
+This BEP introduces a text governance proposal for BNB Smart Chain. 
+
+
+## 2. Status
+
+This BEP is a draft.
+
+
+## 3. Motivation
+
+In some scenarios, the community may need a proposal that does not directly cause any changes, like agreeing to a certain strategy, plan, commitment or other statement.
+
+
+## 4. Specification
+
+
+### 4.1 Introduction
+
+Right now, there are many system parameters that control the behavior of the BSC, e.g. slash amount, cross-chain transfer fees. All these parameters can be determined by the BSC Validator Set together through a proposal-vote process based on staking. The process executes on the BC and the new parameter values will be picked up by either the management module on the BC or corresponding system contracts via the cross-chain communication protocol. The proposals can be classified into two groups: 
+
+1. Param Change Proposal if the parameter takes effect on the Beacon Chain; 
+
+2. Cross Param Change Proposal if the parameter takes effect on the BNB Smart Chain.
+
+
+     
+
+This proposal introduces a new kind of proposal to agree on a certain strategy, plan, commitment, future upgrade, or other statements. **Text proposals** are exclusively a signaling mechanism and focal point for future coordination - they do not directly cause any changes on-chain.
+
+
+### 4.2 How to Draft a Text Proposal 
+
+First, the proposer needs to determine which kind of proposal should be used. Be sure to review all the details of a specific proposal type. Aside from recording the proposal outcome on the BNB Beacon Chain, a text proposal has no direct effect on the BNB Chain. 
+
+There are two key components:
+
+
+
+1. Title - the distinguishing name of the proposal.
+2. Description - the body of the proposal that further describes what is being proposed and the details surrounding the proposal.
+
+Here is a simple text proposal example:
+
+    {
+
+        "title": "Redesign the transaction ordering",
+
+        "description": "Transactions with the same gas price are currently ordered by receive time. Since latency becomes critical after the update, nodes have less incentives to include light nodes and nodes located remotely as peers. Nodes are clustered and connected. This causes the nodes to become increasingly centralized and defeats the purpose of decentralization. Do we consider sorting with a noise value added so that order is sorted by T + N(0,sigma)?"
+
+    } 
+
+
+### 4.3 Governance Stage 
+
+
+#### 4.3.1 Deposit Stage
+
+Anyone can submit a text proposal on the BNB Beacon Chain for others to view. The only cost associated with submitting a proposal is the transaction fee which costs as little as 1 BNB. However, over the course of the voting period, a proposal must have at least 2000 BNB deposited to it in order for it to proceed to the voting stage. This period lasts for at most 2 weeks but if the minimum amount of 2000 BNB is reached sooner, the proposal will proceed to the voting stage immediately. Currently, there is no penalty for delegators and validators who do not participate in governance, though there is a risk to individuals who deposit BNB to a proposal if the proposal does not pass the voting stage, in such case the deposited BNB will be distributed to the validator set.
+
+
+#### 4.3.2 Voting Stage
+
+The next stage in the governance process is the voting stage which lasts a customized period. Rather than depositing BNB, validator operators in this governance stage are actually voting Yes, No, or Abstain. If a proposal reaches quorum or the minimum threshold defined by the protocol, it will proceed to the next stage for tallying. 
+
+
+#### 4.3.3 Tallying Stage
+
+After the voting stage, the following conditions will be taken into consideration to determine if it passes or not:
+
+
+
+* Quorum: more than 50% of the total staked tokens at the end of the voting period need to have voted
+* Threshold: More than 50% or a majority of the tokens that participated in the vote, excluding "Abstain" votes must have voted "Yes"
+* Veto: Less than 33.4% of the tokens that participated in the vote, not counting "Abstain" votes, have vetoed the decision "No (With Veto)".
+
+If any of these conditions are not met, the deposit associated with the denied proposal will not be refunded. These funds will be sent to the validator set.
+
+
+#### 4.3.4 Execution Stage
+
+Once a text proposal is passed, it has no direct effect on the BNB Chain. Generic proposals such as a TextProposal must be reviewed by the BNB-Chain developers and the community for decisions on how to manually implement them.

README.md

@@ -31,3 +31,4 @@ Here are the list of subjects of BEPs:
 * [BEP-131](BEP131.md): Introduce candidate validators onto BNB Smart Chain
 * [BEP-151](BEP151.md): Decommission Decentralized Exchange on BNB Beacon Chain
 * [BEP-153](BEP153.md): Introduce native staking onto BNB Smart Chain
+* [BEP-173](BEP173.md): Introduce Text Governance Proposal for BNB Smart Chain