# 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](/verona/about-verona/generalized-abstraction.md) 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 
```


---

# 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-design.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.