From 3c892623ea4f9f99da10080f1a86d8ccaaccde10 Mon Sep 17 00:00:00 2001 From: lightclient <14004106+lightclient@users.noreply.github.com> Date: Thu, 5 May 2022 16:58:41 +0200 Subject: [PATCH] less confusing wording Co-authored-by: Alex Stokes --- apis/validator/prepare_beacon_proposer.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apis/validator/prepare_beacon_proposer.yaml b/apis/validator/prepare_beacon_proposer.yaml index 03abe81b..178c2c6c 100644 --- a/apis/validator/prepare_beacon_proposer.yaml +++ b/apis/validator/prepare_beacon_proposer.yaml @@ -12,7 +12,7 @@ post: Optionally the validator may also include a signed validator registration which will be used by the Builder API to verify a validator's latest fee - recipient and preferred target gas limit. + recipient and preferred gas limit. Note that there is no guarantee that the beacon node will use the supplied fee recipient when creating a block proposal, so on receipt of a proposed block the