> For the complete documentation index, see [llms.txt](https://corpus-core.gitbook.io/specification-colibri-stateless/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://corpus-core.gitbook.io/specification-colibri-stateless/specifications/op-stack/block-proof.md).

# Block Proof

The Block Proof verifies that a block is valid and part of the OP-Stack chain. In OP-Stack, blocks are verified using preconfirmations (sequencer-signed execution payloads) rather than consensus layer signatures like in Ethereum mainnet.

This Proof is used for the following RPC-Methods:

* [eth\_getBlockByHash](https://www.alchemy.com/docs/node/op-mainnet/op-mainnet-api-endpoints/eth-get-block-by-hash)
* [eth\_getBlockByNumber](https://www.alchemy.com/docs/node/op-mainnet/op-mainnet-api-endpoints/eth-get-block-by-number)
* [eth\_blockNumber](https://www.alchemy.com/docs/node/op-mainnet/op-mainnet-api-endpoints/eth-block-number)

## OpBlockProof

The block proof structure used by other proof types (receipt, transaction, account, etc.) to validate that the block is part of the OP-Stack chain. Contains the preconfirmation proof which verifies the block's validity through the sequencer signature.

The Type is defined in [src/chains/op/ssz/op\_proof\_types.h](https://github.com/corpus-core/colibri-stateless/blob/v1.1.30/src/chains/op/ssz/op_proof_types.h#L184).

```python
class OpBlockProof(Container):
    block_proof : Union [  # proof for the block (preconfirmation-based)
        OpPreconf,         # preconfirmation proof (sequencer-signed execution payload)
        Bytes32]           # blockhash hint identifying the cached execution payload
```

**Referenced Types**

* [OpPreconf](/specification-colibri-stateless/specifications/op-stack.md#oppreconf)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://corpus-core.gitbook.io/specification-colibri-stateless/specifications/op-stack/block-proof.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.