> ## Documentation Index
> Fetch the complete documentation index at: https://help.primevault.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wallets, Vaults and Addresses

## What is a vault in PrimeVault, and how does it relate to blockchain addresses?

A vault is your team’s governed container. It owns one account or address on each blockchain you enable, and it applies one set of rules to all of those accounts. Those rules cover who can approve, how much can be moved, which destinations are allowed, and when actions are permitted. Think of the vault as the “entity,” and each chain account as a sub-account that follows the same rulebook.

On EVM networks, a vault typically uses a single deterministic address across EVM chains. On non-EVM networks such as Tron or Solana, the address format is different, so each chain has its own address. If you want different rules or spend domains (for example, Treasury versus Operations), create additional vaults so each can have its own policy and audit trail.

### Can a vault have multiple addresses on the same chain?

A vault is designed to map to one address per chain. This keeps things predictable and easy to govern. If you need more than one address on a chain, create another vault, for example, “Ops-ETH,” “Grants-ETH,” or “Client Funds-ETH.” This avoids conflicting rules inside a single governed unit and keeps approvals and logs clean.

### Do EVM chains share the same vault address? What about exceptions?

Yes. For EVM networks, a vault’s address is deterministic and consistent. The rare exceptions you may have seen in demos usually come from one-off migrations. In production workspaces, we keep EVM consistency and document any deviation in advance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.