bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 54쪽 중 3쪽
* Multi-device access without transferring keys
* Account recovery through configurable methods
*Detailed in:* [*Intro to Account Abstraction*](/en/about-verona/generalized-abstraction/intro-to-account-abstraction) *and* [*Meta Accounts*](/en/about-verona/generalized-abstraction/meta-accounts)*.*
**2. Signature Abstraction**
The Verona network supports all major cryptographic signature schemes natively at the protocol level.
* Applications request familiar actions ("confirm purchase," "approve transfer") rather than raw transaction signatures
* Cross-curve compatibility: secp256k1, ed25519, secp256r1 (WebAuthn/passkeys), and more
* Developers do not need to implement signature handling logic
* Users never see cryptographic operations
**3. Gas Abstraction**
The parameterized fee layer removes gas fees from the user experience entirely.
* **Fee grants:** Applications sponsor transaction fees for their users via Treasury contracts
* **Multi-token fees:** Fees can be paid in any token (USDC, $VERONA, or custom tokens), with automatic conversion
* **Predictable pricing:** Applications can build transaction costs into product pricing rather than exposing variable gas fees
* **No native token requirement:** Users never need to acquire $VERONA (Previously $XION) to use applications
*For developers: Treasury contracts are the primary mechanism for sponsoring gas. See the Developer > Getting Started section for Treasury contract setup and configuration.*
**4. Payment Abstraction**
The network enables familiar payment experiences within Verona applications.
* Credit card and Apple Pay integration at the protocol level
* Prices displayed in fiat currency (USD, EUR, local currencies)
* Automatic fiat-to-crypto conversion and settlement
* No requirement for users to hold or understand cryptocurrency
* Crossmint integration for digital asset purchases
**5. Device Abstraction**
Applications work identically across all devices without platform-specific setup.
* No browser extensions (no MetaMask, no Keplr)
* No device-specific wallets or key storage
* Seamless state and session transfer across desktop, mobile, and tablet
* Progressive web app support alongside native mobile (via Dave SDK)
**6. Interoperability Abstraction**
Cross-ecosystem operations are handled invisibly through protocol-level interoperability.
* Native IBC (Inter-Blockchain Communication) support for Cosmos ecosystem
* Cross-chain asset transfers without user-facing bridges
* Unified account identity across connected chains
* Developers can access cross-chain assets and liquidity without building bridge integrations
For more details: [xion.burnt.com/whitepaper.pdf](https://xion.burnt.com/whitepaper.pdf)
#### What This Means for Developers
When you build on Verona, you do not need to:
* Implement wallet connection flows
* Build gas estimation or fee management
* Create seed phrase backup/recovery systems
* Handle multi-device session management
* Integrate third-party bridge protocols
* Support multiple signature schemes manually
Instead, you use the Abstraxion SDK, which wraps all six abstraction layers into a developer-friendly interface:
```typescript
// Your user logs in with email. That's it.
import { useAbstraxionAccount } from '@burnt-labs/abstraxion-react';
const { login, isConnected, data: account } = useAbstraxionAccount();
// Login triggers Meta Account creation/connection
// Gas is sponsored by your Treasury contract
// User sees no wallets, no keys, no crypto terminology
await login();
```
The abstraction layer is what turns verification infrastructure into something billions of people can actually use. Without it, zero-knowledge proofs remain an academic curiosity. With it, they become invisible infrastructure powering everyday applications.
# Intro to Account Abstraction
Protocol-level account abstraction on the Verona network
### Types of Wallets in Blockchain
In general, blockchains have two types of accounts:
1. externally owned accounts (EOAs)
2. smart contract accounts (SCAs)
#### Externally-Owned Account (EOA)
Traditionally users interact with blockchains through externally owned accounts (EOAs) which involve the use of asymmetric cryptography. These accounts have a public/private key pair, whereby the public key is stored on the blockchain, and the private key is stored off-chain by the user. The private key, known only to the user, is used to sign transactions, while the public key is used to verify the signature’s authenticity. EOAs, however, have many drawbacks: they lack the ability to implement additional authentication mechanisms, they aren’t able to perform autonomous operations or smart contract executions, and a private/public keypair can not be changed. As a result, EOAs are a central point of failure for users. If a user loses access to their private key, they lose access to their account entirely. Similarly, if a user’s private key is compromised, their account is irreversibly compromised.
#### Smart Contract Account (SCA)
The second type of account, smart contract accounts (SCAs), are governed by code on the blockchain. Their creation involves being deployed to the blockchain through a transaction initiated by an EOA. Once deployed, these smart contracts reside at a specific address on the blockchain and their code dictates the rules and conditions under which they operate. These rules are executed autonomously when certain conditions are met or when they are triggered by transactions or other smart contracts. Traditionally, they are unable to initiate transactions due to an absence of private keys.
### Replacing Wallets with Programmable Accounts
Account abstraction is the foundation of the user experience on the network. Instead of requiring users to create cryptocurrency wallets, manage private keys, and secure seed phrases, Meta Accounts provide protocol-level smart contract accounts that behave like familiar Web2 accounts while retaining the full power of on-chain logic.
#### The Problem with Traditional Wallets
Traditional blockchain wallets are the single largest barrier to mainstream adoption:
* **Key management is risky.** Losing a seed phrase means permanently losing access to all assets. There is no "forgot password" recovery.
* **Onboarding is confusing.** New users must understand wallets, seed phrases, gas tokens, and transaction signing before they can do anything.
* **Device lock-in.** Most wallets are tied to a specific device or browser extension. Switching devices requires manual key transfer.
* **No programmability.** Traditional wallets are static. They cannot enforce spending limits, require multi-factor authentication for large transactions, or delegate limited access to applications.
#### How the Network Solves This
Account abstraction moves account logic from the application layer to the protocol layer. Every account on the Verona network is a smart contract (a "Meta Account") with programmable authentication, permissions, and recovery.
**For users, this means:**
* Log in with email, FaceID, passkeys, Google, or Apple login
* No seed phrases to memorize or secure
* Access the same account from any device
* Recover access if an authentication method is lost
* Set custom security rules (spending limits, session timeouts, multi-sig for high-value transactions)
**For developers, this means:**
* No wallet integration complexity
* No "connect wallet" flow to build and maintain
* Users authenticate through the Abstraxion SDK with one function call
* Gas sponsorship through Treasury contracts (users never pay fees)
* Session keys for background operations without repeated user approval
* Programmable account permissions for your application's specific needs
#### Key Concepts
**Authentication Methods:** Meta Accounts support multiple, swappable authentication methods. A user might log in with email on desktop and FaceID on mobile, both accessing the same account. New methods can be added and old ones revoked without creating a new account.
**Session Keys:** Applications can request time-limited, permission-scoped session keys. This allows operations like in-game actions or automated transactions without requiring the user to approve every single interaction. Session keys expire automatically and can be revoked at any time.
**Treasury Contracts:** The Verona network's mechanism for gas abstraction. Your application deploys a Treasury contract that sponsors transaction fees for your users. You configure which operations to sponsor, set spending limits, and fund the Treasury. Your users never see gas fees.
**Account Recovery:** Unlike traditional wallets, Meta Accounts support configurable recovery. If a user loses their authentication device, they can recover access through pre-configured recovery methods (additional email, social login, trusted contacts, time-locked recovery).
Detailed implementation guides are in [Build on Verona — Accounts](/en/build-on-verona/accounts/getting-started).
# Meta Accounts
Protocol-level account abstraction on the Verona network
## Protocol-Level Account Abstraction
Meta Accounts on the Verona network introduce a highly adaptable and secure account creation and management framework. Built at the protocol level, they have significant benefits over traditional crypto wallets and enable novel application use cases—including agent workflows that need scoped, user-consented access.
#### Core Capabilities
* **Familiar Authentication** Enables non-crypto-native users to log in with familiar methods such as email, social login, FaceID, or passkeys. No wallet downloads, no browser extensions, no seed phrases.
* **Cross-Device Access** Enables a user to interact securely and seamlessly from any device of their choice using the same account. A user can start on desktop, continue on mobile, and switch to tablet without any migration or key transfer.
* **Session Keys** Enables an account to maintain security by providing time-limited sessions, proactively reducing the risks associated with potential key compromise. Applications can request scoped permissions (e.g., "execute in-game actions for the next 30 minutes") without requiring approval for every transaction.
* **Account Recovery** Enables the ability to recover an account if one of the authentication methods is lost by the user. Unlike traditional wallets where a lost key means permanent loss, Meta Accounts support configurable recovery mechanisms.
* **Programmable Permissions** Enables custom security policies at the account level. Set spending limits, require multi-factor authentication for high-value transactions, delegate limited access to third-party applications, and define custom rules for how the account can be used.
* **Modular Architecture** The authentication module is separate from the account logic. New authentication methods (biometrics, hardware keys, institutional custody) can be added without modifying the account contract itself.
#### How Meta Accounts Interact with Verification
Meta Accounts serve as the identity anchor for the Truth Engine. When a user generates a zero-knowledge proof (via zkTLS, zkEmail, or App Attestations), the resulting attestation is bound to their Meta Account. This creates a persistent, verified identity layer:
* Attestations accumulate over time, building a rich verified profile
* Applications can query multiple attestations for a single Meta Account
* Users control which attestations are shared with which applications
* Verified credentials are portable across applications on the network
This connection between Meta Accounts and verification is what grounds **Verona's intelligence layer**: the account holds verified facts, and abstraction makes them accessible to users and authorized agents.
#### Start Building
Follow the [Getting Started with Meta Accounts](/en/build-on-verona/accounts/getting-started) guide to build with Meta Accounts today. The Abstraxion SDK provides a complete integration for web and mobile platforms.
*For technical deep-dive into Meta Account architecture, see* [*Meta Accounts Design*](/en/about-verona/generalized-abstraction/meta-accounts-design)*.*
# Meta Accounts Design
## Overview
Meta Accounts on the **Verona** network use a modular smart-contract account framework—the technical foundation for user identity, verified attestations, and agent-scoped access in **Verona** applications.
Built at the protocol-level, *meta accounts* have a host of benefits over traditional crypto wallets and enable novel Web3 application use-cases. See [How the Network Works](/en/about-verona/generalized-abstraction) for more information around use cases and features.
## Components
<details>
<summary>Identity Provider</summary>
In the case of social login an identity provider is used to handle the confirmation of identity.
</details>
<details>
<summary>Account API</summary>
A set of services used to assist and sponsor new meta account creation.
</details>
<details>
<summary>Abstraxion Library</summary>
This frontend library aids in integration with your react front end.
See the [repo](https://github.com/burnt-labs/xion.js)
</details>
<details>
<summary>Meta Account</summary>
This contract along with a custom module represent the core of the meta account functionality.
See the [repo](https://github.com/burnt-labs/contracts)
</details>
<details>
<summary>UserSessionKey</summary>
The temporary key generated on the app side which is granted ContractExecutionAuthorization by the user's Meta Account on a temporary basis.
</details>
<details>
<summary>FeeGrantTreasury</summary>
A account a app may user to sponsor transactions submitted by the UserSessionKey.
</details>
## Supported Authentication Methods
* Email login
* (MetaMask, biometrics, and many more coming soon)
## Workflows
```mermaid
sequenceDiagram
Actor User
participant DAPP
participant AbstraxionLibrary as Abstraxion Library
participant AccountManagementDashboard as Account Management Dashboard
participant VeronaInfra as Verona Network
User->>DAPP: Load Dapp
User->>DAPP: Clicks 'Mint NFT'
DAPP->>AbstraxionLibrary: connect()
AbstraxionLibrary->>AbstraxionLibrary: Check for Dapp UserSessionKey
AbstraxionLibrary->>AbstraxionLibrary: Check Dapp UserSessionKey Authz Expiry
Note right of AbstraxionLibrary: Note: Authz grants are a "session"
alt no active Dapp UserSessionKey
AbstraxionLibrary->>AbstraxionLibrary: Generate one time private UserSessionKey
AbstraxionLibrary->>AccountManagementDashboard: Redirect user along with permission scope
AccountManagementDashboard->>AccountManagementDashboard: Check for an active connection
alt no active connection
AccountManagementDashboard->>User: Initiate and complete connect flow
end
AccountManagementDashboard->>User: Show authz permission dialog
end
User->>AccountManagementDashboard: Accept permissions
AccountManagementDashboard->>VeronaInfra: Submit transaction with authz grants
alt transaction successful
VeronaInfra->>DAPP: Notify transaction success
DAPP->>User: Return user to dapp
else transaction failed
VeronaInfra->>AccountManagementDashboard: Notify transaction failure
AccountManagementDashboard->>User: Show error modal
end
User->>DAPP: Clicks 'Mint NFT'
DAPP->>AbstraxionLibrary: Locally sourced transaction
AbstraxionLibrary->>AbstraxionLibrary: Autosigned using Dapp UserSessionKey
AbstraxionLibrary->>VeronaInfra: Submitted
```
# Surfaces
Product surfaces on the Verona network
Verona is one **network** with multiple **surfaces**—interfaces where humans, enterprises, agents, and developers interact with verified intelligence. Each surface is a door into the same Truth Engine, not a separate product stack.
Phase 1 documentation covers surfaces that are **live or have clear integration paths today**.
<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>Ero (EarnOS)</strong></td><td>Live consumer proof—verified participation and user-owned data. People earn for what they already do online without exposing raw records.</td><td><a href="/en/about-verona/surfaces/earnos">Ero (EarnOS)</a></td></tr><tr><td><strong>Burnt Verified</strong></td><td>Enterprise proof—income, employment, and credentials verified at the source. Non-custodial; no document storage.</td><td><a href="/en/about-verona/surfaces/burnt-verified">Burnt Verified</a></td></tr></tbody></table>
**Verify once · Reuse everywhere · Expose nothing** applies across every surface: a fact proven once on the network can be reused by any service or agent the user authorizes.
Each surface builds on primitives documented under [Truth Engine](/en/about-verona/verification-infrastructure) and [Build on Verona](/en/build-on-verona/overview). Integration guides expand as product APIs stabilize.
# Ero (EarnOS)
Ero by EarnOS — verified participation on Verona
**Ero** (by EarnOS), built on Verona, is the **flagship consumer launch** for **user-owned, verified participation**. People earn for what they already do online: activity is cryptographically verified, and the data underneath is never exposed.
**EarnOS** is the product surface; **Ero** is the live consumer experience users open at launch. Together they demonstrate verification, ownership, reuse, and real economic activity on the same network validators secure and developers build on.
## What Ero shows
* Users connect everyday accounts (for example ride-share or delivery apps) and verify attributes with the [Truth Engine](/en/about-verona/verification-infrastructure)
* Verified facts stay **user-owned** on the network and can be reused where the user consents
* Rewards and campaigns map to **proof of eligibility**, not self-reported claims
* [Meta Accounts](/en/about-verona/generalized-abstraction/meta-accounts) handle identity and consent boundaries without wallet friction
## For developers
Ero builds on the same primitives as any Verona application:
* **zkTLS, zkEmail, zkPassport, and app attestations** for eligibility without raw data exposure
* **Meta Accounts** for authentication and permission scopes
* **CosmWasm** and Treasury patterns for on-chain settlement and gasless UX (`xion-testnet-2` for development)
Typical integration patterns:
1. Verify a user action or attribute with the Truth Engine
2. Map the proof to your app's business rules (campaign, tier, payout, agent gate)
3. Settle or record outcomes on the Verona network
{% hint style="warning" %}
Do not describe unannounced token products, partner programs, or revenue figures as live in your own apps or docs. Follow legal and marketing review before publishing reward, revenue-share, or token numbers.
{% endhint %}
## Related docs
* [Surfaces](/en/about-verona/surfaces)
* [Verification guides](/en/build-on-verona/verification)
* [Meta Accounts](/en/about-verona/generalized-abstraction/meta-accounts)
# Burnt Verified
Enterprise verification without document custody
**Burnt Verified** is Verona's enterprise surface for **income, employment, and credential verification**—cryptographic proofs from the source, with **no documents stored** and no custodial liability for the verifier.
Where Ero proves the consumer story, Burnt Verified proves the **real-company** story: paying customers, enterprise workflows, and verification revenue on the same Truth Engine that powers agents and apps.
## What it enables
* **Income and employment verification** — Users authenticate to payroll or HR sources; verifiers receive a cryptographic proof in seconds, not a document upload
* **Real-estate, lending, and insurance workflows** — Decisions on records verified at the source; the data underneath never transits through your systems
* **Non-custodial assurance** — Gate features, payouts, compliance, or agent tools on attestations instead of PII archives
* **Composable with agents** — Authorized agents 프로젝트로 돌아가기