> For the complete documentation index, see [llms.txt](https://vaulta.gitbook.io/vaulta-guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vaulta.gitbook.io/vaulta-guides/accounts/vaulta-native-accounts.md).

# Vaulta Native Accounts

Accounts serve as the primary means of identifying participants and managing resources. Unlike traditional blockchain addresses, Vaulta accounts are human-readable names that facilitate user interactions and smart contract deployments. This document provides an in-depth overview of Vaulta accounts, their structure, creation process, and associated permissions.

Smart Contracts are also deployed on top of accounts, and the account owner can control the smart contract unless control is relinquished.

## Account Structure

A Vaulta account is a unique identifier stored on the blockchain, representing an individual or a group, depending on its permission configuration. Each account is associated with a set of permissions that define its authority within the network. These permissions control the actions an account can perform and are crucial for transaction authorization. 

| Component              | Description                                                                                                                                                                                                  |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Account Name**       | A unique, human-readable identifier (up to 12 characters) used to receive EOS-related tokens and interact with the Vaulta network.                                                                           |
| **Owner Public Key**   | The public part of the owner key pair. This key is stored on the blockchain and is used to verify ownership of the account.                                                                                  |
| **Owner Private Key**  | The private part of the owner key pair. This key grants full control over the account, including the ability to change both owner and active keys. It should be stored securely offline (cold storage).      |
| **Active Public Key**  | The public part of the active key pair. This key is stored on the blockchain and is used to verify transactions that require active permission.                                                              |
| **Active Private Key** | The private part of the active key pair. This key is used for day-to-day operations like transferring funds and voting. It should be stored securely but is used more frequently than the owner private key. |

## Account Names

EOS account names are human-readable and must adhere to specific conventions:

* Length: Up to 12 characters.
* Characters: Lowercase letters (a-z), digits (1-5), and periods (.).
* Naming Rules:
  * Names cannot start or end with a period.
  * The first letter of a 12 characters account name must start with an alphabet.\
    (✅ samplename12 ❌ 12samplename)
  * Periods denote ownership hierarchies, allowing for the creation of nested accounts (e.g., <mark style="color:green;">sub.account</mark>).

These conventions ensure efficient and organized account management within the EOSIO ecosystem.&#x20;

## Smart Contracts and Accounts

In the Vaulta ecosystem, smart contracts are deployed to and executed by accounts. Each account can host a single smart contract, which can be updated or modified by the account owner, provided the appropriate permissions are in place. This design facilitates decentralized application development and management, with accounts serving as both user identities and application hosts.&#x20;

## Takeaway

Vaulta accounts are foundational to the Vaulta blockchain, providing a flexible and secure framework for identity management, resource allocation, and permission control. Understanding the structure and functionality of Vaulta accounts is essential for participants aiming to interact effectively with the network, whether for personal transactions, application development, or smart contract deployment.

## Resources


---

# 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, and the optional `goal` query parameter:

```
GET https://vaulta.gitbook.io/vaulta-guides/accounts/vaulta-native-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.