# Verification

This section covers how to integrate the **Truth Engine** into your application on the Verona network. Whether you are building a consumer app, an agent workflow that needs verified context, or a DeFi protocol that assesses creditworthiness, these guides walk through full integration.

Conceptual background: [Truth Engine](/verona/about-verona/verification-infrastructure.md) · Product surface: [Burnt Verified](/verona/about-verona/surfaces/burnt-verified.md)

### ZK Infrastructure

#### [Publishing ZK Verification Keys](/verona/build-on-verona/verification/publishing-zk-verification-keys.md)

Publish and manage verification keys (vkeys) for custom ZK circuits on the Verona network. This is **infrastructure-level** guidance for advanced use cases requiring custom ZK proving systems (Groth16, Gnark, UltraHonk).

> **Note**: Most applications use pre-configured vkeys for standard verification features (zkTLS, zkEmail, App Attestations). This guide is for developers building custom ZK circuits.

### Explore the verification modules

#### [Internet Verification (ZK Module, zkTLS)](/verona/build-on-verona/verification/internet-verification.md)

Verify data from any website using zero-knowledge proofs over TLS-encrypted sessions. Prove user credentials, financial data, and platform reputation without exposing sensitive information.

* **Reclaim Integration**: Verify social media stats, financial data, and platform activity
* **Opacity Integration**: Alternative zkTLS provider for internet verification

#### Email Verification (DKIM Module, ZK Email)

Verify email contents cryptographically using existing DKIM signatures. Prove purchase receipts, employment verification, and account ownership without accessing the user's inbox.

***(Guides coming soon)***

#### Mobile Verification (App Attestations)

Verify mobile application data with cryptographic proofs. Prove rideshare ratings, fitness metrics, and app usage from mobile devices.

***(Guides coming soon)***


---

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

```
GET https://docs.burnt.com/verona/build-on-verona/verification.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.