remove strict fee recipient docs (#3551)

## Issue Addressed

Related: #3550

Remove references to the `--strict-fee-recipient` flag in docs. The flag will cause missed proposals prior to the merge transition.



Co-authored-by: realbigsean <sean@sigmaprime.io>
This commit is contained in:
realbigsean
2022-09-08 00:06:25 +00:00
parent 419c53bf24
commit 81d078bfc7
2 changed files with 3 additions and 15 deletions

View File

@@ -55,9 +55,7 @@ Both the gas limit and fee recipient will be passed along as suggestions to conn
in either, it will *not* keep you from proposing a block with the builder. This is because the bounds on gas limit are calculated based
on prior execution blocks, so it should be managed by an execution engine, even if it is external. Depending on the
connected relay, payment to the proposer might be in the form of a transaction within the block to the fee recipient,
so a discrepancy in fee recipient might not indicate that there is something afoot. If you know the relay you are connected to *should*
only create blocks with a `fee_recipient` field matching the one suggested, you can use
the [strict fee recipient](suggested-fee-recipient.md#strict-fee-recipient) flag.
so a discrepancy in fee recipient might not indicate that there is something afoot.
### Set Gas Limit via HTTP