BEP-319: Optimize the incentive mechanism of the Fast Finality feature#319
BEP-319: Optimize the incentive mechanism of the Fast Finality feature#319brilliant-lx merged 4 commits intobnb-chain:masterfrom buddh0:bep310-make-rewards-for-fast-finality-governable
Conversation
| This algorithm allocates a portion of the systemReward contract balance increment for each epoch, causing the systemReward contract balance to continuously grow. When it exceeds 100BNB, a reward exceeding 1 BNB is distributed at once, far more than other epochs. | ||
| The new formula is as follows: | ||
| ``` | ||
| if currentSystemRewardBalance > 100BNB |
There was a problem hiding this comment.
What about the case when currentSystemRewardBalance < 100 BNB ?
There was a problem hiding this comment.
It rarely happen
because validator keep depositing and relayers only cost a little
if happens, no reward then.
There was a problem hiding this comment.
Under what conditions will the balance drop below 100BNB and what is estimated likelihood of this happening? I think it would be good to have an analysis of that before going ahead with this BEP, because if the balance drops below 100BNB there will be no finality rewards, and thus no incentive for validators to send their fast finality votes.
There was a problem hiding this comment.
nearly 100%,
only happens when bsc-relayers got some errors sending crosschain messages to bsc
and retry again and again, then a lot of balance of systemReward will need to pay to the relayers.
this rarely happend, in the past year only once as I know
There was a problem hiding this comment.
Is there a reason why the balance is always 100BNB and above? I don't know if it's a good idea to base the logic to fit the historical state of the chain. This makes it hard to test this BEP on other networks like a local devnet or even the testnet.
|
Odpowiadam na te kwestie twierdząco, wyrażając zainteresowanie. Odpowiedź
jest zwięzła i jasna.
pt., 17 lis 2023 o 12:15 buddho ***@***.***> napisał(a):
… ***@***.**** commented on this pull request.
------------------------------
In BEPs/BEP-319.md
<#319 (comment)>:
> +```
+newBurnRatio = (1 - 1/16) * oldBurnRatio = (1 - 1/16) * 10% = 9.375%
+```
+As a result, following the implementation of this BEP, the burn ratio is set to 9.375% directly.
+## 4.2 Balancing Rewards
+Fast Finality rewards are unevenly distributed between epochs. Assuming the current balance of the systemReward contract is currentSystemRewardBalance, and the balance after award distribution in the previous epoch is previousSystemRewardBalance, the totalReward calculation formula is as follows:
+```
+if currentSystemRewardBalance > 100BNB
+ totalReward = currentSystemRewardBalance / 100
+else
+ totalReward = (currentSystemRewardBalance - previousSystemRewardBalance) * 0.5
+```
+This algorithm allocates a portion of the systemReward contract balance increment for each epoch, causing the systemReward contract balance to continuously grow. When it exceeds 100BNB, a reward exceeding 1 BNB is distributed at once, far more than other epochs.
+The new formula is as follows:
+```
+if currentSystemRewardBalance > 100BNB
updated
—
Reply to this email directly, view it on GitHub
<#319 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYCKU675L4FGDPX5RQXTCPTYE5BNPAVCNFSM6AAAAAA7I57MQWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMZWGY3DONBXHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
BEP-319: Optimize the incentive mechanism of the Fast Finality feature
1. Summary
This BEP proposes three optimizations to the incentive mechanism of the Fast Finality feature in BSC.
2. Abstract
The proposal focuses on three key optimizations for the incentive mechanism of the Fast Finality feature:
3. Motivation
The introduction of the Fast Finality feature in BSC significantly reduces the time required for transaction final confirmation. This feature represents a substantial advantage for BSC compared to other EVM-compatible chains. The purpose of this BEP is to solidify and enhance this advantage.
4. Specification
4.1 Governable Rewards
Currently, the reward is approximately 1/16 of the block transaction fees, leading to a lack of incentive for some validators to participate in voting, thereby reducing the stability expectation of the Fast Finality feature. This BEP makes Fast Finality rewards governable, laying the groundwork for future reward enhancements.
4.1.1 Existing Allocation Logic
4.1.2 Allocation Logic Moved to the Contract
4.1.3 Maintain Burn Ratio
The real-time burning mechanism is an essential part of the BNB deflation plan. In this BEP, the goal is to maintain it essentially unchanged.
Before implementing this BEP, a portion of the balance of the SystemRewardContract will be used as a reward for Fast Finality voting at the end of each epoch, resulting in a balance less than 100 BNB. Therefore, in the majority of blocks, validators will deposit 1/16 of the block transaction fees to the SystemRewardContract.
The oldBurnRatio is 10%. The actual proportion of burned transaction fees to block transaction fees can be calculated approximately as follows:
As a result, following the implementation of this BEP, the burn ratio is set to 9.375% directly.
4.2 Balancing Rewards
Fast Finality rewards are unevenly distributed between epochs. Assuming the current balance of the systemReward contract is currentSystemRewardBalance, and the balance after award distribution in the previous epoch is previousSystemRewardBalance, the totalReward calculation formula is as follows:
This algorithm allocates a portion of the systemReward contract balance increment for each epoch, causing the systemReward contract balance to continuously grow. When it exceeds 100BNB, a reward exceeding 1 BNB is distributed at once, far more than other epochs.
The new formula is as follows:
This formula allocates the entire increment of the systemReward contract balance for each epoch, resulting in a more even distribution.
4.3 Extending Submission Deadline for Malicious Voting Evidence
When rule-violating votes occur, the current requirement is to submit evidence within 256 blocks; otherwise, rewards cannot be obtained, and malicious validators are not penalized.
This BEP proposes making the submission deadline governable, initialized to 3 days, for increased operability.
5. License
The content is licensed under CC0.