From 5d35bbd9c3eaa6958bc6a4686c74645b6abd43af Mon Sep 17 00:00:00 2001 From: "lightclient@protonmail.com" Date: Mon, 25 Apr 2022 16:58:01 +0200 Subject: [PATCH] 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: |