Sign in

v1

latestOpenAPI 3.1.02026-07-2612501.4 MB

GetBuilderStatesExpectedWithdrawalsByStateId

Requests that the beacon node identify information about its implementation in a format similar to a HTTP User-Agent field.

get/{apiKey}/eth/v1/builder/states/{stateId}/expected_withdrawals

Path parameters

apiKeystring required
<style> .custom-style { color: #048FF4; } </style>

For higher throughput, please <span class="custom-style"><a href="../docs/quick-start-guide#-creating-your-api-key-on-the-zan-platform" target="_blank">create your own API key</a></span>.

stateIdstring required

State identifier. Can be one of: "head" (canonical head in node's view), "genesis", "finalized", "justified", <slot>, <hex encoded stateRoot with 0x prefix>.

Query parameters

proposal_slotstring
Example:1

The slot that a block is being built for, with the specified state as the parent. Defaults to the slot after the parent state if not specified.

Response

A version string of the running beacon node.

execution_optimisticboolean required

True if the response references an unverified execution payload. Optimistic information may be invalidated at a later time. If the field is not present, assume the False value.

finalizedboolean required

True if the response references the finalized history of the chain, as determined by fork choice. If the field is not present, additional calls are necessary to compare the epoch of the requested information with the finalized checkpoint.

Example response

{
  "data": [
    {
      "index": "1",
      "validator_index": "1",
      "address": "0xAbcF8e0d4e9587369b2301D0790347320302cc09",
      "amount": "1"
    }
  ]
}