# Introduction to EVE Vault

**EVE Vault** is the official wallet and inventory manager for EVE Frontier on Sui, available as a [web app and Chrome extension](https://github.com/evefrontier/evevault). For what it is, how to install it, and how wallet and identity work (including zkLogin), see [Wallets & Identity](/eve-vault/wallets-and-identity.md).

**Features:**

* Sui Wallet Standard compliance for fast, safe, cross-dApp integration.
* FusionAuth OAuth support for linking your EVE Frontier account and in-game character to your wallet.
* Permissioned dApp access: connect to player-made dApps and tools while protecting your infomorph's identity—even if your clone is destroyed.

***

## The Economy and Currencies

The EVE Frontier economy on Sui supports open, player-powered trading between real-world and in-game value.

* **LUX**: Used for most in-game transactions, purchases, trades, and services.
* **EVE Token**: A Sui-based utility token for ecosystem participation, modding, and developer rewards; supports dApp onboarding and can be used to acquire special game assets.

EVE Vault enables:

* Trading and storage of LUX, EVE Token, and other Sui-based assets.
* Secure management and transfer of player-generated and alliance-specific currencies.
* Integration with markets, trading systems, and configurable infrastructure rewards.

**Core advantages:**

* Trade assets, currencies, services, and reputation with robust permissions and privacy.
* Create, exchange, and use custom currencies—including alliance tokens and specialized mission rewards.
* Seamless experience for builders, traders, and players operating across the decentralized EVE Frontier world.

***


---

# Agent Instructions: 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.evefrontier.com/eve-vault/introduction-to-eve-vault.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.