> For the complete documentation index, see [llms.txt](https://summa.gitbook.io/summa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://summa.gitbook.io/summa/smart-contract/verifiers.md).

# Verifiers

Summa utilizes three verifier contracts and one key contract: [**SnarkVerifier**](https://github.com/summa-dev/summa-solvency/blob/v2/contracts/src/SnarkVerifier.sol), [**GrandSumVerifier**](https://github.com/summa-dev/summa-solvency/blob/v2/contracts/src/GrandSumVerifier.sol), [**InclusionVerifier**](https://github.com/summa-dev/summa-solvency/blob/v2/contracts/src/InclusionVerifier.sol), and [**VerifyingKey**](https://github.com/summa-dev/summa-solvency/blob/v2/contracts/src/VerifyingKey.sol) . The **SnarkVerifier** and **VerifyingKey** contracts must be regenerated whenever custodians redeploy the Summa contract with new configurations, as they are specifically generated to a particular circuit configuration by the [`halo2-solidity-verifier`](https://github.com/summa-dev/halo2-solidity-verifier).

For example, let's assume the Summa contract is initially deployed with the configuration to support two cryptocurrencies as specified by the custodian. This setup allows users to verify their inclusion proofs containing two currencies within the Summa contract. If the custodian decides to accommodate three cryptocurrencies for user convenience, they must redeploy the Summa contract with newly generated SnarkVerifier and VerifyingKey contracts configured for three cryptocurrencies.

In contrast, the **GrandSumVerifier** and **InclusionVerifier** contracts do not need to be regenerated for new deployments. These contracts are capable of verifying proofs regardless of size, including any number of cryptocurrencies included in the proof.

This means that custodians might not need to deploy these contracts themselves if they are already deployed on EVM.

{% hint style="info" %}
**Note:** Generating a `SnarkVerifier` for more than 9 currencies may exceed the Ethereum mainnet contract size limit.
{% endhint %}


---

# 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://summa.gitbook.io/summa/smart-contract/verifiers.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.