# Meta Accounts

## 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](/verona/build-on-verona/accounts/getting-started.md) 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*](/verona/about-verona/generalized-abstraction/meta-accounts-design.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/generalized-abstraction/meta-accounts.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.