Provide beacon node with proposals for the given validators
Prepares the beacon node for potential proposers by supplying the information required when proposing blocks for the given validators. The information supplied for each validator index will persist through the epoch in which the call is submitted and for a further two epochs after that, or until the beacon node restarts. It is expected that validator clients will send this information periodically, for example, at each epoch, to ensure beacon nodes have correct and timely fee recipient information.
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 acceptable before signing it.
Also note that requests containing currently inactive or unknown validator indices will be accepted, as they may become active at a later epoch.
Parameters
POST JSON Body
Name | Required | Type | Detail |
---|---|---|---|
| ✅ | Array[Object] | JSON Object containing validator_index , fee_recipient . Please see the example |
Result
Returns the HTTP Status Code 200 when the publish is successful
Example
Request
curl -X POST <your-endpoint>/eth/v1/validator/prepare_beacon_proposer \
--header 'Content-Type: application/json' \
--data-raw '[
{
"validator_index": "1",
"fee_recipient": "0xabcf8e0d4e9587369b2301d0790347320302cc09"
}
]'
Return
On success
<empty> with HTTP Code 200