bsc-api-list.md: update fast finality #648
Merged
Conversation
This file contains hidden or 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
buddh0
reviewed
Jun 3, 2025
| Economic Finality refers to the high cost associated with reverting a block. In proof-of-stake systems that use a slashing mechanism (such as Casper FFG, Tendermint, or BSC Fast Finality), if validators violate the voting rules, part or all of their stake can be forfeited. This economic penalty makes it extremely expensive to undermine finality. Generally, block n achieves economic finality by block n+2, meaning that BSC Fast Finality reduces the confirmation time to two blocks in most cases. This improves the user experience by making transaction confirmation faster and more reliable. | ||
| #### Economic Finality (Fast Finality) | ||
|
|
||
| The **Fast Finality** feature, introduced through **BEP-520**, enables Economic Finality using a slashing mechanism similar to Casper FFG and Tendermint. Key characteristics: |
buddh0
reviewed
Jun 3, 2025
| - **Block n achieves economic finality by block n+2** | ||
| - Transaction finality time: **~3.75 seconds** (reduced from 7.5 seconds) | ||
| - Economic penalties make block reversal extremely expensive | ||
| - Validators violating voting rules forfeit part or all of their staked assets |
buddh0
approved these changes
Jun 3, 2025
NathanBSC
approved these changes
Jun 3, 2025
zzzckck
reviewed
Jun 3, 2025
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the Finality API documentation by clarifying BSC's dual-layer finality model, detailing the Fast Finality upgrade (BEP-126), and specifying parameters for the probabilistic fallback.
- Introduce an overview of Economic (Fast) Finality and Probabilistic Finality
- Add BEP-126 key characteristics, timing, and slashing details
- Document network parameters, finality requirements, and formula for block confirmations
| Economic Finality refers to the high cost associated with reverting a block. In proof-of-stake systems that use a slashing mechanism (such as Casper FFG, Tendermint, or BSC Fast Finality), if validators violate the voting rules, part or all of their stake can be forfeited. This economic penalty makes it extremely expensive to undermine finality. Generally, block n achieves economic finality by block n+2, meaning that BSC Fast Finality reduces the confirmation time to two blocks in most cases. This improves the user experience by making transaction confirmation faster and more reliable. | ||
| #### Economic Finality (Fast Finality) | ||
|
|
||
| The **Fast Finality** feature, introduced through **BEP-126**, enables Economic Finality using a slashing mechanism similar to Casper FFG and Tendermint. Key characteristics: |
There was a problem hiding this comment.
Consider adding a link to the BEP-126 specification to let readers quickly reference the full proposal details.
Copilot uses AI. Check for mistakes.
| - **Block Time**: ~1.5 seconds | ||
|
|
||
| **Finality Requirements:** | ||
| - **>1/2 validator confirmations**: 88 blocks (11 × 8) ≈ **132 seconds** |
There was a problem hiding this comment.
[nitpick] To improve clarity, label this threshold as “Majority (>1/2)” and the next line as “Supermajority (>2/3)” so readers immediately understand the consensus levels.
Copilot uses AI. Check for mistakes.
Co-authored-by: zzzckck <152148891+zzzckck@users.noreply.github.com>
zzzckck
approved these changes
Jun 3, 2025
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.
Improve the doc for Finality API by enhancing clarity, technical accuracy, and overall readability of the finality mechanisms.