Skip to content

Commit

Permalink
chores: update some wording
Browse files Browse the repository at this point in the history
  • Loading branch information
zzzckck committed Feb 20, 2025
1 parent 10981f9 commit e1c0cba
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 23 deletions.
10 changes: 5 additions & 5 deletions BEPs/BEP-520.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,11 +89,11 @@ func (p *Parlia) isBlockDelayMinedOnPurpose(header, parent *types.Header) {
```

### 4.2 Parameter Changes
As mentioned above, phase one and phase two are highly relevant, their parameter changes will be put in one table for easy comparison.
As mentioned above, phase one and phase two are highly relevant, their parameter changes will be put in one table for easy comparison. But the parameters of phase two here is only for reference, as it could be changed in the future when phase two is finally delivered.

#### 4.2.1 Change table
A multitude of system parameters are configured based on the assumption that the default block interval is 3 seconds. Consequently, when the block interval is altered, these parameters must be adjusted accordingly:
|parameter |type |current value | phase one(1.5s) | phase two(0.75s)|
|parameter |type |origin(3s) | phase one(1.5s) | phase two(0.75s)|
|--------|--------|--------|--------|--------|
|Epoch |client parameter |200 |1000 |2000|
|GasLimit |client parameter |140M |60M |30M|
Expand Down Expand Up @@ -146,10 +146,10 @@ The [Quarterly Auto-Burn](https://www.bnbburn.info/) mechanism also requires adj
where T represents the number of seconds in the corresponding quarter.

### 6.4 Block Finality
This BEP will not change the fast finality mechanism, but short block interval could bring challenges fast finality, as votes need to be propagated in a shorter time. When fast finality works properly, after this BEP, the average transaction finality time would be reduced from 7.5 seconds to 3.75 seconds.
This BEP will not change the fast finality mechanism, but short block interval could bring some challenges to fast finality, as votes need to be propagated in a shorter time. When fast finality works properly, with this BEP, the average transaction finality time would be reduced from 7.5 seconds to 3.75 seconds.
But if fast finality failed, with TurnLength 16 and ValidatorSize 21, for natural block finality, it will be:
- (>1/2 validator confirm): 176(11*16) blocks, that is 264 seconds
- (>2/3 validator confirm): 240(15*16) blocks, that is 360 seconds
- (with >1/2 validator confirmations): 176(11*16) blocks, that is 264 seconds
- (with >2/3 validator confirmations): 240(15*16) blocks, that is 360 seconds

## 7. License
The content is licensed under [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
28 changes: 11 additions & 17 deletions BEPs/BEP-524.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,20 @@
<pre>
BEP: 524
Title: Short Block Interval Phase 2: 0.75 seconds
Title: Short Block Interval Phase Two: 0.75 seconds
Status: Draft
Type: Standards
Created: 2025-02-10
Created: 2025-02-18
Description: To shorten the block interval from 1.5 seconds to 0.75 seconds.
</pre>

# BEP-524: Short Block Interval Phase 2: 0.75 seconds
- [BEP-524: Short Block Interval Phase 2: 0.75 seconds](#bep-524-short-block-interval-phase-2-075-seconds)
# BEP-524: Short Block Interval Phase Two: 0.75 seconds
- [BEP-524: Short Block Interval Phase Two: 0.75 seconds](#bep-524-short-block-interval-phase-two-075-seconds)
- [1. Summary](#1-summary)
- [2. Abstract](#2-abstract)
- [3. Motivation](#3-motivation)
- [4. Specification](#4-specification)
- [4.1 Parameter Changes](#41-parameter-changes)
- [4.2.1 Change table](#421-change-table)
- [4.2 Parameters Changes](#42-parameters-changes)
- [5. Rational](#5-rational)
- [6. Backward Compatibility](#6-backward-compatibility)
- [6.1 MEV](#61-mev)
Expand All @@ -31,16 +30,17 @@ Shorten the block interval from 1.5 seconds to 0.75 seconds to enable faster tra
BEP-520 is the phase one to reduce the block interval from 3 seconds to 1.5 seconds. And this BEP is the phase two, which would reduce it further to 0.75 seconds.

## 3. Motivation
Faster transaction confirmation is a critical and long term goal, with 0.75 seconds block interval, it could meet the requirement of some time sensitive application.
Faster transaction confirmation is a critical and long term goal, with 0.75 seconds block interval, it could meet the requirement of some time sensitive applications.

## 4. Specification
The overall design specification has been covered in BEP-520, so only the parameter changes will be covered in this section.
The overall design specification is similar to BEP-520, so only the parameter changes will be covered in this section.

### 4.1 Parameter Changes
As mentioned above, phase one and phase two are highly relevant, their parameter changes will be put in one table for easy comparison.

#### 4.2.1 Change table
A multitude of system parameters are configured based on the assumption of the default block interval. Consequently, when the block interval is altered, these parameters must be adjusted accordingly:
|parameter |type |current value | phase one(1.5s) | phase two(0.75s)|
|parameter |type | origin(3s) | phase one(1.5s) | phase two(0.75s)|
|--------|--------|--------|--------|--------|
|Epoch |client parameter |200 |1000 |2000|
|GasLimit |client parameter |140M |60M |30M|
Expand All @@ -55,8 +55,6 @@ A multitude of system parameters are configured based on the assumption of the d
|BSCValidatorSet.felonyThreshold |contract parameter |$felonyThreshold |$felonyThreshold × 2 |$felonyThreshold × 4|
|BSCValidatorSet.felonySlashScope |contract parameter |$felonySlashScope |$felonySlashScope × 2 |$felonySlashScope × 4|
|BSCValidatorSet.TurnLength |contract parameter |4 |16 |32|
### 4.2 Parameters Changes


## 5. Rational
Refer BEP-520
Expand All @@ -66,17 +64,13 @@ Refer BEP-520
After phase two, the block interval will be reduced to 0.75 seconds, a single validator will produce 32 consecutive blocks per turn, keeping the total block production time at 24 seconds (0.75 × 32). However, the shorter block time significantly reduces the collaboration window for searchers, builders, and validators, impacting the current process and requiring adjustments.

### 6.2 Layer 2 Solutions
NA
TBD

### 6.3 Quarterly Auto-Burn
The [Quarterly Auto-Burn](https://www.bnbburn.info/) mechanism also requires adjustment,The block count in the formula is replaced with time, resulting in the new formula:
<div align="center">
<img src=./assets/bep-520/5-3.png width=60% />
</div>
where T represents the number of seconds in the corresponding quarter.
TBD

### 6.4 Block Finality
NA
TBD

## 7. License
The content is licensed under [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,8 @@ Here is the list of subjects of BEPs:
| [BEP-441](./BEPs/BEP-441.md) | Implement EIP-7702: Set EOA account code | Standards | Review |
| [BEP-466](./BEPs/BEP-466.md) | Make the block header format compatible with EIP-7685 | Standards | Review |
| [BEP-496](./BEPs/BEP-496.md) | Implement EIP-7623: Increase calldata cost | Standards | Review |
| [BEP-520](./BEPs/BEP-520.md) | Short Block Interval | Standards | Draft |
| [BEP-520](./BEPs/BEP-520.md) | Short Block Interval Phase One: 1.5 seconds | Standards | Draft |
| [BEP-524](./BEPs/BEP-524.md) | Short Block Interval Phase Two: 0.75 seconds | Standards | Draft |


# BNB Chain Upgrades
Expand Down

0 comments on commit e1c0cba

Please sign in to comment.