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