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
QBFT uses the minerbase (coinbase) as part of the consensus algorithm when signing blocks. This is used to verify if a block proposal comes from someone that has permissions to do so and is the current leader.
Currently when gas is enabled gas rewards always go to the address specified in the header.coinbase field ie the validator. We should be able to configure where those rewards go to using a transition
This will send all gas rewards to the account 0x123... Note in this scenario there is no block reward.
If a single transfer transaction is mined at block 10 then the sending account will be deducted 21000 and the miningBeneficiary will be rewarded 21000.
To transition back to the default behaviour of rewarding the validator with the gas you should be able to specify a transition to achieve this:
QBFT uses the
minerbase
(coinbase) as part of the consensus algorithm when signing blocks. This is used to verify if a block proposal comes from someone that has permissions to do so and is the current leader.Currently when gas is enabled gas rewards always go to the address specified in the
header.coinbase
field ie the validator. We should be able to configure where those rewards go to using atransition
This will send all gas rewards to the account
0x123..
. Note in this scenario there is no block reward.If a single transfer transaction is mined at block 10 then the sending account will be deducted 21000 and the miningBeneficiary will be rewarded 21000.
To transition back to the default behaviour of rewarding the validator with the gas you should be able to specify a transition to achieve this:
The text was updated successfully, but these errors were encountered: