# 7. Attesters/Users verify epoch key proof

```bash
npx ts-node cli/index.ts verifyEpochKeyProof \
    -x $UNIREP_CONTRACT_ADDRESS  \
    -pf $EPOCH_KEY_PROOF  \
    -p $EPOCH_PUBLIC_SIGNALS
```

{% hint style="info" %}
**NOTE:** 

`-p` is the public signals of the epoch key proof

`-pf` is the epoch key proof

See: [cli/verifyEpochKeyProof](/unirep/package/cli/epoch-key-and-proof.md#verifyepochkeyproof) for more `verifyEpochKeyProof` options.
{% endhint %}

If the epoch key proof is successfully verified, it prints

```bash
Verifying epoch key 1421637519 with GSTRoot 14270915092725970451268204538779500502278807167690661595734149116833065872952 in epoch 1
Verify epoch key proof with epoch key 1421637519 succeed
```


---

# Agent Instructions: 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:

```
GET https://unirep.gitbook.io/unirep/getting-started/start-with-cli-commands/7.-attesters-users-verify-epoch-key-proof.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.