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"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"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.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.Topics to subscribe to, e.g., 'head'
Successfully subscribed to events
The response is of type string.
"event: contribution_and_proof\ndata: {\"contribution\": \"...\", \"proof\": \"...\"}\n\n"
Was this page helpful?