From 5d35bbd9c3eaa6958bc6a4686c74645b6abd43af Mon Sep 17 00:00:00 2001 From: "lightclient@protonmail.com" Date: Mon, 25 Apr 2022 16:58:01 +0200 Subject: [PATCH 1/4] add optional validator registration --- apis/validator/prepare_beacon_proposer.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/apis/validator/prepare_beacon_proposer.yaml b/apis/validator/prepare_beacon_proposer.yaml index e0985d19..78990266 100644 --- a/apis/validator/prepare_beacon_proposer.yaml +++ b/apis/validator/prepare_beacon_proposer.yaml @@ -10,6 +10,10 @@ post: information periodically, for example each epoch, to ensure beacon nodes have correct and timely fee recipient information. + 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. + 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 validator should confirm that it finds the fee recipient within the block @@ -32,6 +36,14 @@ post: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' fee_recipient: $ref: '../../beacon-node-oapi.yaml#/components/schemas/ExecutionAddress' + validator_registration: + type: object + properties: + timestamp: + $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' + signature: + $ref: '../../beacon-node-oapi.yaml#/components/schemas/Signature' + responses: "200": description: | From 0f4c717cf7e91caf256f4c0080a79450862d3a21 Mon Sep 17 00:00:00 2001 From: "lightclient@protonmail.com" Date: Sat, 30 Apr 2022 11:22:30 +0200 Subject: [PATCH 2/4] add gas target to registration --- apis/validator/prepare_beacon_proposer.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/apis/validator/prepare_beacon_proposer.yaml b/apis/validator/prepare_beacon_proposer.yaml index 78990266..015ab5ef 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. + recipient and preferred gas target. 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,6 +41,8 @@ post: properties: timestamp: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' + gas_target: + $ref: '../../beacon-node-oapi.yaml#/components/schemas/Uint64' signature: $ref: '../../beacon-node-oapi.yaml#/components/schemas/Signature' From 4d1ae976f3c20d5cc83443b6afa3d8f7e3378b1e Mon Sep 17 00:00:00 2001 From: "lightclient@protonmail.com" Date: Mon, 2 May 2022 14:43:26 +0200 Subject: [PATCH 3/4] 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' 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 4/4] 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