You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: Reward validators by time passed
Layer: Consensus
Abstract
In order to make a chain consensus agnostic, there is way to reward them by the time passed, not by how many blocks they have validated. Therefore, whenever each block is created, it should save the timestamp and check the diff between last time the block was validated. If there is minimum threshold archieved (5 sec, for example) it should reward next validator from the array list to issue 1 reward (POA).
Smart contract should handle the state the order of last rewarded validator.
Rationale
In order to try different consensus algorithms, such as honeybadger BTF, we have to come up with different way to archive validator's incentive.
The text was updated successfully, but these errors were encountered:
Title
Abstract
In order to make a chain consensus agnostic, there is way to reward them by the time passed, not by how many blocks they have validated. Therefore, whenever each block is created, it should save the timestamp and check the diff between last time the block was validated. If there is minimum threshold archieved (5 sec, for example) it should reward next validator from the array list to issue 1 reward (POA).
Smart contract should handle the state the order of last rewarded validator.
Rationale
In order to try different consensus algorithms, such as honeybadger BTF, we have to come up with different way to archive validator's incentive.
The text was updated successfully, but these errors were encountered: