Skip to content

Commit

Permalink
refine wording
Browse files Browse the repository at this point in the history
  • Loading branch information
forcodedancing committed Nov 17, 2023
1 parent 3102c53 commit e6f4c1e
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions BEPs/BEP322.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
- [1. Summary](#1-summary)
- [2. Motivation](#2-motivation)
- [3. Specification](#3-specification)
- [3.1 Trust Model](#31-trust-model)
- [3.1 BSC Trust Model](#31-bsc-trust-model)
- [3.2 Workflow](#32-workflow)
- [3.3 Payment & Economic Considerations](#33-payment--economic-considerations)
- [3.4 APIs](#34-apis)
Expand All @@ -39,25 +39,25 @@ However, on BNB Smart Chain, there is no such specification yet. By
introducing such a specification, it will resolve some problems as well
as bring new benefits for the ecosystem.

- Firstly, currently validators are using different customized
- Improve stability of network: currently validators are using different customized
implementations for MEV with different levels of quality, which
brings instability to the network. With a specification, it will
provide guidelines and standards to follow, minimizing the
instability issues.

- Secondly, validators can only integrate with a single MEV provider
- Improve MEV economy by building MEV market: validators can only integrate with a single MEV provider
now, due to the lack of support on BSC clients. With this
specification, validators can integrate with multiple builders at
the same time.

- Thirdly, this specification will also bring transparency to
- Improve transparency: this specification will also bring transparency to
different stakeholders, including BNB delegators. With the
adoption of builders, it is probable that delegators can earn more
because builders are supposed to submit more profitable blocks.

## 3. Specification

### 3.1 Trust Model
### 3.1 BSC Trust Model

Before we move on to the design of Builder Specification, let's have an
analysis of the BSC trust model and compare it to Ethereum, for it will
Expand All @@ -68,7 +68,7 @@ networks.
validators should delegate a lot of BNB (more than 10 thousand in
general) and maintain a high reputation. Misbehaviour will lead to
reputation damage and un-delegations. Currently, there are about
40 validators with 20M BNB staked, including active and inactive
40 validators (more validators are coming) with 20M BNB staked, including active and inactive
ones. In Ethereum, the barrier to becoming a validator is very
low (i.e., 32 ETH), and there are more than [800 thousand Ethereum
validators](https://www.nasdaq.com/articles/the-most-pressing-issue-on-ethereum-is-validator-size-growth).
Expand Down Expand Up @@ -130,7 +130,7 @@ Builder Specification here for the readers who are familiar with it.
workable for builders to send transactions to validators after
receiving the receipt signature. In case a builder finds a
validator stealing transactions, it can 1) not submit bids to evil
validators anymore, 2) reveal evidence to the public channels for
validators anymore, 2) reveal evidence to the public channels (e.g., chatting groups, github, blogs) for
social influence.

- In Ethereum, the fee settlement between builders and validators is
Expand Down

0 comments on commit e6f4c1e

Please sign in to comment.