> For the complete documentation index, see [llms.txt](https://crosschain-alliance.gitbook.io/hashi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-alliance.gitbook.io/hashi/tools/sp1-storage-proof-verifier.md).

# SP1 storage proof verifier

Hashi offers a tool able to generate a storage proof using Zero Knowledge proofs.\
This tools leverage [SP1 zkVM](https://docs.succinct.xyz/docs/introduction) to generate a storage proof that can be used with Hashi.

Install the SP1 storage proof generator from the [Github repo.](https://github.com/crosschain-alliance/sp1-eth-get-proof-verifier)

#### Usage

```
RUST_LOG=info cargo run --release -- --execute \
    --rpc-url <rpc_url> \
    --block-number <block_number_hex_encoded> \
    --proof-block-number <ancestral_block_number_hex_encoded> \
    --account <account> \
    --storage-key <storage_key>
```

where:

* `<rpc_url>`: The RPC URL of your node.
* `<reference_block_number>`(optional): The block number in hexadecimal format.
* `<proof_block_number>`: The block number for the proof, specified in hexadecimal format (e.g., 0xAABBCC). If `<proof_block_number>` is set to a value less than `<reference_block_number>`, the program will validate the entire chain of blocks from `<reference_block_number>` down to `<proof_block_number>`.
* `<account>`: The account address to verify.
* `<storage_key>`: The storage key you wish to verify.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://crosschain-alliance.gitbook.io/hashi/tools/sp1-storage-proof-verifier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.