Verona 백서

Verona

원문

bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 54쪽 중 1쪽

# Welcome to Verona Making AI Intelligent — the intelligence layer for AI [Verona](https://verona.dev/) is the intelligence layer for AI. It makes user-verified data portable, private, and programmable, so agents can transact on information the user actually owns. **Making AI Intelligent** is the through-line. **Verify once · Reuse everywhere · Expose nothing.** * **Truth Engine** makes intelligence grounded. Zero-knowledge verification across websites (zkTLS), email (zkEmail), passports (zkPassport), and apps (attestations) turns claims into provable, reusable facts—without revealing underlying secrets. * **Generalized Abstraction** makes the network usable. Protocol-level abstractions for accounts, signatures, gas, payments, and devices remove friction for mainstream apps. Users log in with familiar credentials; developers ship Web2-quality UX on verifiable infrastructure. ## About Verona Learn what Verona is, how verification and abstraction fit together, and the product surfaces you can build on. <table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What is Verona?</strong></td><td>Overview of the intelligence layer, Truth Engine, and abstraction stack.</td><td><a href="/en/about-verona/overview">What is Verona?</a></td></tr><tr><td><strong>Truth Engine</strong></td><td>zkTLS, zkEmail, zkPassport, and app attestations—verify once, reuse everywhere.</td><td><a href="/en/about-verona/verification-infrastructure">Truth Engine</a></td></tr><tr><td><strong>Surfaces</strong></td><td>Ero (EarnOS) and Burnt Verified—live consumer and enterprise proof.</td><td><a href="/en/about-verona/surfaces">Surfaces</a></td></tr></tbody></table> ## Build on Verona Guides for developers building apps, agents, and integrations on the network. <table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Accounts</strong></td><td>Meta Accounts, authentication, gasless transactions, and web, backend, or mobile app development.</td><td><a href="/en/build-on-verona/accounts">Accounts</a></td></tr><tr><td><strong>Computation</strong></td><td>Quick-start apps, local development, contract library, and integrations (tokens, oracles, indexers).</td><td><a href="/en/build-on-verona/computation">Computation</a></td></tr><tr><td><strong>Verification</strong></td><td>Verify real-world data and identity without revealing it—zkTLS, ZK email, and app attestations.</td><td><a href="/en/build-on-verona/verification">Verification</a></td></tr><tr><td><strong>Tools &#x26; SDKs</strong></td><td>Verona Agent Toolkit, daemon CLI, Mob signing client, and Abstraxion.</td><td><a href="/en/build-on-verona/tools">Tools &amp; SDKs</a></td></tr><tr><td><strong>For AI Agents</strong></td><td>One-line setup for agentic development with Meta Accounts and Treasury.</td><td><a href="/en/about-verona/ai-agents">For AI Agents</a></td></tr></tbody></table> ## Help & Support <table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Discord Developer Support</strong></td><td>Chat with developers on Discord.</td><td></td><td><a href="https://discord.gg/verona">https://discord.gg/verona</a></td></tr><tr><td><strong>Telegram Developer Support</strong></td><td>Chat with developers on Telegram.</td><td></td><td><a href="https://t.me/+5KA8xBuU5wYzZjU0">https://t.me/+5KA8xBuU5wYzZjU0</a></td></tr><tr><td><strong>Found an issue in the docs?</strong></td><td>Report it, or submit a pull request on the page where you found it.</td><td></td><td><a href="https://github.com/burnt-labs/docs/issues/new">https://github.com/burnt-labs/docs/issues/new</a></td></tr></tbody></table> ## Why Verona AI agents need verified information they can act on without becoming custodians of sensitive data. Verona makes verified facts portable, private, and reusable across authorized applications and agents. Verify once, let the user control reuse, and expose proofs instead of raw records. # What is Verona? Intelligence layer overview — Making AI Intelligent ### 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](/en/about-verona/surfaces/earnos) (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](/en/about-verona/surfaces/burnt-verified). **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](/en/about-verona/verification-infrastructure). **Abstraction layer** Generalized Abstraction embeds account, signature, gas, payment, device, and interoperability abstraction in the protocol. See [Meta Accounts](/en/about-verona/generalized-abstraction/meta-accounts) and [Intro to Account Abstraction](/en/about-verona/generalized-abstraction/intro-to-account-abstraction). <figure><img src="https://3630978198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FB5Z5ijJgMx0GJO3l1Il9%2Fuploads%2FZfw73quqyQMaOGipiq9L%2FXION%20Infrastructure%20Graphic%20Chain%20Abstraction%202.png?alt=media&amp;token=ae68ab17-4a4f-4e7f-bfd3-33c105d538ef" 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**](/en/about-verona/surfaces/earnos) (EarnOS) — Consumer proof: verified participation and user-owned data flows. * [**Burnt Verified**](/en/about-verona/surfaces/burnt-verified) — Enterprise proof: income, employment, and credential verification without document custody. See [Surfaces](/en/about-verona/surfaces) 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](/en/build-on-verona/tools/verona-toolkit) and [For AI Agents](/en/about-verona/ai-agents). 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](/en/about-verona/overview/architecture-and-tech-glossary) and [Rebrand: XION → Verona](/en/others/rebrand-from-xion) for rename and Phase 2 boundaries. Continue to [Truth Engine](/en/about-verona/verification-infrastructure), [Meta Accounts](/en/about-verona/generalized-abstraction/meta-accounts), and [Build on Verona](/en/build-on-verona/overview). # Use Cases Verona combines the [Truth Engine](/en/about-verona/verification-infrastructure) and [Generalized Abstraction](/en/about-verona/generalized-abstraction) so apps and agents can act on **verified once, reused everywhere** facts—without collecting or storing sensitive source data. The patterns below map to the four audiences on [What is Verona?](/en/about-verona/overview). For integration detail, see [Build on Verona — Verification](/en/build-on-verona/verification) and [Surfaces](/en/about-verona/surfaces). ## Humans | Pattern | What becomes possible | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Verified participation** | Users prove everyday activity and earn from what they already do—raw records stay private. See [Ero (EarnOS)](/en/about-verona/surfaces/earnos). | | **Portable reputation** | Prove a loyalty tier, rating, or account standing from one platform to another without the source app's cooperation. | | **Controlled sharing** | Disclose only the attribute an app needs (for example "premium subscriber") while keeping underlying data private. | ## Enterprises | Pattern | What becomes possible | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Income and employment** | Cryptographic proof from payroll or HR sources in seconds—no document uploads, no custodial liability. See [Burnt Verified](/en/about-verona/surfaces/burnt-verified). | | **Verified acquisition** | Target offers to users who cryptographically prove competitor loyalty or spend tiers—without invasive tracking. | | **Compliance and underwriting** | KYC/KYB, insurance, and lending workflows on scoped proofs instead of document archives. | ## Agents | Pattern | What becomes possible | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authorized context** | Agents read attestations bound to a [Meta Account](/en/about-verona/generalized-abstraction/meta-accounts)—income range, identity attributes, account standing—instead of scraped or self-reported input. | | **Action without custody** | Refills, travel check-in, loan steps, and similar flows run on proofs the user already verified; the agent never holds bank statements or passports. | See [For AI Agents](/en/about-verona/ai-agents) for toolkit setup. ## Developers | Pattern | What becomes possible | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Proof → action → settlement** | Read an attestation, trigger app or agent logic, settle on chain in one flow—with [Treasury](/en/build-on-verona/accounts/getting-started/treasury-contracts) gas sponsorship for end users. | | **Composable verification** | Combine zkTLS, zkEmail, zkPassport, and app attestations into multi-factor gates for access, pricing, or rewards. | | **On-chain policy** | CosmWasm contracts query attestations before executing transfers, governance, or game outcomes. | # Architecture & Glossary Key Terms and Concepts ### Product Terms | Term | Definition | | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Verona** | The intelligence layer for AI—the network and layer (not “another chain” in narrative). Verified facts are user-owned and reusable by authorized agents. Product surfaces include Ero (EarnOS) and Burnt Verified; on-chain identifiers remain **XION**. | | **Truth Engine** | Verification infrastructure comprising zkTLS (websites), zkEmail (email), zkPassport (identity documents), and App Attestations (mobile apps). Turns claims into provable, reusable facts without exposing underlying data. | | **Ero (EarnOS)** | The live consumer surface on Verona. Users verify everyday activity and participate in reward flows with user-owned proofs; EarnOS is the product surface, Ero is the consumer experience. | | **Burnt Verified** | The enterprise verification surface—income, employment, and credentials verified at the source without document custody. | | **zkTLS** | Zero-knowledge verification for web data. Creates proofs over TLS-encrypted sessions from any website, enabling claims about ratings, balances, loyalty status, and more without exposing raw data. | | **DKIM Module (zkEmail)** | Verification module that creates zero-knowledge proofs over email contents using DKIM signatures. Proves email-based claims without exposing the email. | | **zkPassport** | Verification module for identity documents. Proves attributes such as age or citizenship without copying or storing the passport or ID. | | **App Attestation** | Verification module that creates cryptographic proofs of mobile application data. Proves in-app state without exposing app credentials or full data. | | **Attestation** | An on-chain record of a verified claim. Created when a zero-knowledge proof is successfully verified by the protocol. Queryable by smart contracts. | | **Zero-Knowledge Proof (ZKP)** | A cryptographic method that allows one party to prove a statement is true without revealing any information beyond the truth of the statement itself. | | **Selective Disclosure** | The ability to prove specific claims from a data source while keeping all other data private. E.g., proving "income above $100K" without revealing exact income. | | **Composable Proofs** | Multiple attestations from different verification modules combined to create a multi-dimensional verified profile for a single user. | ### Abstraction Terms | Term | Definition | | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Generalized Abstraction** | The Verona network's protocol-level abstraction of accounts, signatures, gas, payments, devices, and interoperability. Makes blockchain invisible to end users. | | **Meta Account** | A CosmWasm smart contract that serves as a user's on-chain account. Supports modular authentication, programmable permissions, and account recovery. Replaces traditional wallets. | | **Authenticator** | A module within a Meta Account that validates a specific authentication method (email JWT, WebAuthn/passkeys, cryptographic keys, etc.). Multiple authenticators can be registered per account. | | **Session Key** | A temporary, permission-scoped keypair that allows an application to execute specific operations on behalf of a user without requiring approval for each transaction. | | **Treasury Contract** | A smart contract deployed by an application developer that sponsors gas fees for users. The primary mechanism for gas abstraction on the Verona network. | | **Parameterized Fee Layer** | The Verona network's gas abstraction system that allows fees to be paid in any token, sponsored by applications, or built into product pricing. | | **Abstraxion SDK** | The Verona network's developer SDK that wraps all abstraction layers (account, gas, signature, payment, device) into a simple integration for web and mobile applications. | ### Infrastructure Terms | Term | Definition | | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CosmWasm** | The smart contract execution environment used by the Verona network. Contracts are written in Rust and compiled to WebAssembly (Wasm). | | **CometBFT** | The Byzantine Fault Tolerant consensus engine underlying the Verona network (formerly Tendermint). | | **Cosmos SDK** | The framework on which the Verona network is built. Provides modular blockchain application development. | | **IBC** | Inter-Blockchain Communication protocol. Enables native cross-chain messaging and asset transfers between the Verona network and other Cosmos ecosystem chains. | | **Proof of Stake (PoS)** | The Verona network's consensus mechanism. Validators stake $VERONA (Previously $XION) to participate in block production and earn rewards. Inflation is calculated only against staked tokens. | | | | ### Economic Terms | Term | Definition | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **$VERONA** | The native token of the V
프로젝트로 돌아가기