From 4d1ae976f3c20d5cc83443b6afa3d8f7e3378b1e Mon Sep 17 00:00:00 2001 From: "lightclient@protonmail.com" Date: Mon, 2 May 2022 14:43:26 +0200 Subject: [PATCH] use gas limit instead of gas target --- apis/validator/prepare_beacon_proposer.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apis/validator/prepare_beacon_proposer.yaml b/apis/validator/prepare_beacon_proposer.yaml index 015ab5ef..03abe81b 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 gas target. + recipient and preferred target 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 @@ -41,7 +41,7 @@ post: properties: timestamp: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' - gas_target: + gas_limit: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' signature: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Signature'