realbigsean 904dd62524 Strict fee recipient (#3363) ... ## Issue Addressed Resolves #3267 Resolves #3156 ## Proposed Changes - Move the log for fee recipient checks from proposer cache insertion into block proposal so we are directly checking what we get from the EE - Only log when there is a discrepancy with the local EE, not when using the builder API. In the `builder-api` branch there is an `info` log when there is a discrepancy, I think it is more likely there will be a difference in fee recipient with the builder api because proposer payments might be made via a transaction in the block. Not really sure what patterns will become commong. - Upgrade the log from a `warn` to an `error` - not actually sure which we want, but I think this is worth an error because the local EE with default transaction ordering I think should pretty much always use the provided fee recipient - add a `strict-fee-recipient` flag to the VC so we only sign blocks with matching fee recipients. Falls back from the builder API to the local API if there is a discrepancy . Co-authored-by: realbigsean <sean@sigmaprime.io>		2022-07-26 02:17:24 +00:00
..
environment	Decrease proposer boost to 40% (#3201)	2022-05-23 03:52:31 +00:00
src	Add lighthouse db command (#3129)	2022-04-01 00:58:59 +00:00
tests	Strict fee recipient (#3363)	2022-07-26 02:17:24 +00:00
Cargo.toml	v2.4.0 (#3360)	2022-07-21 22:02:36 +00:00