# Wallet Infrastructure

## AI Agent Wallet Architecture

Each instance of Onyx AI is provisioned with a dedicated on-chain  wallet, referred to as an agent wallet. These wallets are permissionless and have no centralized control. These wallets serve as the execution layer for autonomous tasks. Users can:

* Fund the agent wallet with any ERC20 token or Ethereum on Onyx, Ethereum, Base, and BNB Chain.
* Predefine operational rules (e.g., budget limits, whitelisted dApps, risk thresholds).
* Allow the agent to execute autonomously within those constraints, using AI to interpret prompts and derive task sequences.

Wallets are deterministic, derived via cryptographic hashing of user identifiers and secured by permissionless layers that enforce non-custodial ownership. Additionally, agent wallets can integrate time locks, multisig guards, and circuit breakers to ensure execution safety.

***

### Deployment Environment and Ecosystem Integration

* Blockchain: Onyx, Ethereum, Base, BNB
* Gas Token: All computational and transaction costs are paid in XCN, the native token of the Onyx Ledger which are converted to `Credits` . There is no gas required as the agent is gas-free.
* dApp Support: Onyx AI is extensible and continuously updated with support for top-tier dApps in categories including DeFi, NFT marketplaces, staking, and governance.

***

*Example Architecture*

<figure><img src="/files/VffkyHWNC37Cv1BCMdSB" alt=""><figcaption></figcaption></figure>


---

# 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.onyx.org/onyx-ai/wallet-infrastructure.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.