PostBeaconBlocksV2

Publish a signed block.

Instructs the beacon node to broadcast a newly signed beacon block to the beacon network, to be included in the beacon chain. A success response (20x) indicates that the block passed gossip validation and was successfully broadcast onto the network. The beacon node is also expected to integrate the block into the state, but may broadcast it before doing so, so as to aid timely delivery of the block. Should the block fail full validation, a separate success response code (202) is used to indicate that the block was successfully broadcast but failed integration. After Deneb, this additionally instructs the beacon node to broadcast all given blobs. The broadcast behaviour may be adjusted via the broadcast_validation query parameter.

Path Params
string
required
Defaults to public
.custom-style { color: #048FF4; }

For higher throughput, please create your own API key.

Query Params
string
enum

Level of validation that must be applied to a block before it is broadcast.

Possible values:

  • gossip (default): lightweight gossip checks only
  • consensus: full consensus checks, including validation of all signatures and blocks fields except for the execution payload transactions.
  • consensus_and_equivocation: the same as consensus, with an extra equivocation check immediately before the block is broadcast. If the block is found to be an equivocation it fails validation.

If the block fails the requested level of a validation a 400 status MUST be returned immediately and the block MUST NOT be broadcast to the network.

If validation succeeds, the block must still be fully verified before it is incorporated into the state and a 20x status is returned to the caller.

Allowed:
Body Params

The SignedBeaconBlock object composed of BeaconBlock object (produced by beacon node) and validator signature.

Headers
string
enum
required

Version of the block being submitted.

Allowed:
Responses
200

The block was validated successfully and has been broadcast. It has also been integrated into the beacon node's database.

202

The block failed validation, but was successfully broadcast anyway. It was not integrated into the beacon node's database.

Language
Response
Click Try It! to start a request and see the response here!