GET
/
0a9d79d93fb2f4a4b1e04695da2b77a7
/
eth
/
v1
/
events
curl --request GET \
  --url https://beacon-nd-422-757-666.p2pify.com/0a9d79d93fb2f4a4b1e04695da2b77a7/eth/v1/events
"event: contribution_and_proof\ndata: {\"contribution\": \"...\", \"proof\": \"...\"}\n\n"

This method will not work in the interactive section as it receives a continuous stream of data.

You can test it using Postman:

​
Instructions:

  1. Click Run in Postman.
  2. Click Fork collection and follow the steps to set it up in your environment.
  3. Select Get Beacon Chain events.
  4. After the collection is set up, click Send.

Subscribe to the Beacon Chain events and receive a stream of the following data:

  • Event type (event: head): This specifies the type of event being streamed. In this case, it’s a head event, which relates to the latest confirmed block on the Beacon Chain.
  • Data fields:
    • slot: The slot number at which this block was proposed. Slots are time periods during which a block can be proposed.
    • block: The hash of the block that has been accepted as the head of the chain.
    • state: The state root of the Ethereum network after processing this block.
    • epoch_transition: A boolean indicating whether or not this block involved a transition between epochs.
    • previous_duty_dependent_root and current_duty_dependent_root: These roots help in understanding the duties thatvalidators need to perform, which may vary from one epoch to another.
    • execution_optimistic: A boolean indicating the execution mode. If false, it means the block is fully validated; if true, it implies the block is processed in an optimistic mode, where certain validations might be pending.

Get you own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

Query Parameters

​
topics
string
default:head
required

Topics to subscribe to, e.g., 'head'

Response

200
text/event-stream

Successfully subscribed to events

The response is of type string.

Example:

"event: contribution_and_proof\ndata: {\"contribution\": \"...\", \"proof\": \"...\"}\n\n"