# What is Verona?

### What is Verona?

**Making AI Intelligent.** Verona is the **intelligence layer for AI**—a network where facts about the real world are proven once, owned by the user, and reusable by any agent they authorize, with the data underneath never exposed.

Verona makes user-verified data **portable, private, and programmable**, so agents can transact on information the user actually owns. In public language, Verona is a **network and a layer**, not “another chain.” The chain is how it works; the layer is what it is.

**Verify once · Reuse everywhere · Expose nothing.**

### The gap

Today's AI is capable—until it counts. Agents need **provable information** to act and cannot store sensitive data. Scraped text, self-reported forms, and one-off KYC checks do not scale: every new app makes the user prove the same thing again, and every broker stores another copy.

Verona treats a verification as a **durable, user-owned asset** on the network—not a disposable check that dies on use.

### The unlock

**One proof, and the whole network trusts it.** Verify a fact once, at its source. You own it; any agent you authorize acts on it; the data underneath never shows.

The **Truth Engine** generates zero-knowledge proofs across four surfaces:

| Surface       | Module           | What it proves                                             |
| ------------- | ---------------- | ---------------------------------------------------------- |
| **Websites**  | zkTLS            | What a site shows about you—without handing over the login |
| **Email**     | zkEmail (DKIM)   | What landed in your inbox—without opening it up            |
| **Passports** | zkPassport       | Who you are—without copying the document                   |
| **Apps**      | App Attestations | What you did in an app—without exposing the account        |

Verified claims are recorded on the network, bound to the user's **Meta Account**, and reusable by any application or agent the user permits.

### Why abstraction still matters

Powerful verification is useless if people cannot reach it. **Generalized Abstraction** is embedded at the protocol level: accounts, signatures, gas, payments, devices, and interoperability are abstracted so users log in with email, pay with familiar methods, and rarely see blockchain mechanics.

The network runs on Cosmos SDK, CometBFT, and CosmWasm. Builders still use chain-precise identifiers where required (`xion-testnet-2`, `xiond`, on-chain addresses).

### Who Verona is for

**Humans** — Turn everyday proof into assets you own. [Ero](/verona/about-verona/surfaces/earnos.md) (by EarnOS) is the live consumer surface: verified activity without exposing raw data.

**Enterprises** — Make decisions on records cryptographically verified at the source. No one touches the data underneath; you never carry the liability. See [Burnt Verified](/verona/about-verona/surfaces/burnt-verified.md).

**Agents** — Act on what the user has already verified, without rechecking or holding sensitive data. Prescription refills, flight check-in, loan workflows, and similar actions become possible when context is provable and permissioned.

**Developers** — Build on a network of verified facts. Intelligence owned by users, permissioned to your app. Read a proof, have an agent act on it, settle when it acts—proof, action, and settlement in one flow. No collecting data, no storing it, no carrying the liability.

### Architecture at a glance

**Verification layer (Truth Engine)**

Protocol-level zero-knowledge verification across websites, email, passports, and apps. See [Truth Engine](/verona/about-verona/verification-infrastructure.md).

**Abstraction layer**

Generalized Abstraction embeds account, signature, gas, payment, device, and interoperability abstraction in the protocol. See [Meta Accounts](/verona/about-verona/generalized-abstraction/meta-accounts.md) and [Intro to Account Abstraction](/verona/about-verona/generalized-abstraction/intro-to-account-abstraction.md).

<figure><img src="/files/TAItt2GipSLpVV4bI1CP" alt=""><figcaption></figcaption></figure>

**Consensus and execution**

Cosmos SDK with CometBFT consensus and CosmWasm smart contract execution. Proof of Stake with inflation calculated against staked tokens. IBC provides native interoperability.

### Surfaces into one network

Product **surfaces** are doors into the same Truth Engine—not separate products:

* [**Ero**](/verona/about-verona/surfaces/earnos.md) (EarnOS) — Consumer proof: verified participation and user-owned data flows.
* [**Burnt Verified**](/verona/about-verona/surfaces/burnt-verified.md) — Enterprise proof: income, employment, and credential verification without document custody.

See [Surfaces](/verona/about-verona/surfaces.md) for Phase 1 entry points.

### For developers: what this means

Building on Verona gives you:

1. **Verification primitives** — Prove real-world data privately; trust between parties without seeing sensitive underlying information.
2. **Reusable attestations** — One verification, many authorized consumers—agents and apps query proofs instead of re-running KYC.
3. **Abstraction primitives** — Meta Accounts, gas sponsorship, familiar login and payment flows.
4. **Agent-ready tooling** — [Verona Agent Toolkit](/verona/build-on-verona/tools/verona-toolkit.md) and [For AI Agents](/verona/about-verona/ai-agents.md).
5. **CosmWasm smart contracts** — On-chain logic with mature Rust tooling.
6. **An existing ecosystem** — Production verification usage across brands including Uber, Amazon, and Nike, and millions of users on the engine.

### Network economics (high level)

$VERONA secures the network through Proof of Stake. Because end-user flows are often gas-sponsored, token value is designed to track **network revenue and usage**—revenue share from ecosystem apps, enterprise verification, and agent activity—rather than raw transaction gas alone. Stakers and validators participate in that growth through staking rewards and governance. See [Architecture & Glossary](/verona/about-verona/overview/architecture-and-tech-glossary.md) and [Rebrand: XION → Verona](/verona/others/rebrand-from-xion.md) for rename and Phase 2 boundaries.

Continue to [Truth Engine](/verona/about-verona/verification-infrastructure.md), [Meta Accounts](/verona/about-verona/generalized-abstraction/meta-accounts.md), and [Build on Verona](/verona/build-on-verona/overview.md).


---

# 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/about-verona/overview.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.