Update Prysm client to pay block fees to validators and Commons Budget as defined in Bosagora whitepaper.

[MichaelKim20]

Ethereum burns transaction fees when creating blocks.
Here's what the White Paper on BOSAGORA says.

Transaction Fee: Transaction fees are adjusted flexibly (see Appendix 3). Congress Nodes receive 70%
of the collected transactions fee in a block, and 30% is sent to the Commons Budget. Transaction fees can be
adjusted through the Congress. 

But I don't think it's going to be easy to calculate this.
So I want to implement all of this as a Common's Budget receiving. And we'll have to revise the white paper.

The Beacon chain has a number of implementations.
We use prysm.
https://github.com/zeroone-boa/prysm

[MichaelKim20]

The link below contains the following:
https://ethereum.org/en/staking/

After The Merge you'll receive unburnt transaction fees for blocks you propose

[omerfirmak]

https://github.com/zeroone-boa/prysm/blob/ebd6d9a0b38c1598b8ec123cc88dd089b86ec41a/validator/client/validator.go#L97
https://github.com/zeroone-boa/prysm/blob/ebd6d9a0b38c1598b8ec123cc88dd089b86ec41a/validator/client/validator.go#L937-L1000

These look relevant @mkykadir

[mkykadir]

Rewarding methods to investigate;

• https://github.com/zeroone-boa/prysm/blob/ebd6d9a0b38c1598b8ec123cc88dd089b86ec41a/beacon-chain/core/altair/attestation.go#L223
• https://github.com/zeroone-boa/prysm/blob/ebd6d9a0b38c1598b8ec123cc88dd089b86ec41a/beacon-chain/core/altair/block.go#L129

[omerfirmak]

https://github.com/zeroone-boa/prysm/blob/ebd6d9a0b38c1598b8ec123cc88dd089b86ec41a/beacon-chain/core/altair/block.go#L129

this one is for the sync committee, see #6

[mkykadir]

this one is for the sync committee, see #6

Are we going to include attestation rewards to validators? These are easy to nullify with following config params;

TimelySourceWeight
TimelyTargetWeight
TimelyHeadWeight

but 0'ing them out will result in 0 propose reward (which also we might want).
Also in beacon chain, currently, all rewards are calculated from "BaseReward" which is calculated with total staked ETH; so rewards are not gathered from TX fees.

Source

There is a "Fee recipient" configuration parameter for validators for future use when Bellatrix (merge) will bring execution engine and TX fees is included in Beacon chain, this address will be used for TX fees. Currently I couldn't find any implementations both on spec and Prysm code that utilizes this address.

[mkykadir]

We investigated this with @omerfirmak in detail;
Here Prysm allows configuration of a Fee Recipient Address to be used after the Merge. This address is transferred to execution layer through Engine API as coinbase address. This address can be utilized to transfer TX fees in execution layer. Currently Geth's Finalize for beacon consensus doesn't implement TxFee rewards but ethash consensus has an accumulateRewards function. Apart from reward calculations (which can be easily configured with config params), we cannot do TX fees on Beacon chain, thus work is needed on execution layer.

[omerfirmak]

Since EIP-1559 burns base fees, all we have to do is override fee recipient address to be the commons budget for all validators.

[mkykadir]

TXFees are transferred to miners here

[mkykadir]

Related PR bosagora/agora-el#6

[mkykadir]

^ Fixes this