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

# Wallet Architecture

The **NOXCAT Wallet** is built on a layered architecture that separates user identity, wallet control, and blockchain execution.

This design allows users to interact with Web3 through a familiar identity-based experience while preserving the security and compatibility of self-custodial blockchain wallets.

At a high level, the architecture consists of three layers:

```
UID
↓
Wallet
↓
Address
↓
Blockchain Execution
```

***

## Identity Layer — UID

The **UID** is the user’s persistent identity within the NOXCAT ecosystem.

Instead of treating a wallet address as the primary user identity, NOXCAT introduces UID as the root identity layer for wallet access, social interactions, and ecosystem participation.

A UID can be created through:

* Email login
* Social login
* Apple ID / Google login
* Future identity providers

The UID is used to connect:

* User profile
* Wallets
* Social relationships
* Transaction contacts
* Ecosystem permissions
* Future reputation or credit systems

This allows users to interact with people and identities instead of raw blockchain addresses.

***

## Wallet Layer — Asset Control

The **Wallet Layer** represents the user’s self-custodial asset control environment.

Each UID can manage one or multiple wallets, depending on the user’s needs.

The wallet layer may support:

* System-generated wallets
* Imported wallets
* Multi-chain wallets
* Future smart accounts
* Future account abstraction features

This design gives beginner users a simple default experience while still allowing advanced users to manage multiple wallets and assets.

The wallet remains self-custodial. NOXCAT does not take custody of user assets.

***

## Execution Layer — Addresses

The **Execution Layer** connects wallets to blockchain networks.

Each wallet may correspond to one or more chain-specific addresses used to execute transactions on supported networks.

These addresses remain fully compatible with public blockchains, decentralized applications, and smart contracts.

However, for everyday users, addresses are abstracted behind UID-based interactions.

Users do not need to manually manage addresses for normal social or ecosystem interactions, while advanced users can still access address-level details when needed.

***

## Blockchain Execution

All on-chain actions are ultimately executed through blockchain transactions.

This includes:

* Sending assets
* Receiving assets
* Swapping tokens
* Staking
* Interacting with smart contracts
* Accessing escrow services
* Participating in governance

The wallet coordinates these actions through the appropriate network, wallet, and address while keeping the user experience consistent.

***

## Architecture Diagram

```
                 NOXCAT Wallet Architecture

                       User
                        │
                        ▼
              ┌──────────────────┐
              │       UID        │
              │  Identity Layer  │
              └──────────────────┘
                        │
                        ▼
              ┌──────────────────┐
              │      Wallet      │
              │  Control Layer   │
              └──────────────────┘
                        │
                        ▼
              ┌──────────────────┐
              │     Address      │
              │ Execution Layer  │
              └──────────────────┘
                        │
                        ▼
              ┌──────────────────┐
              │    Blockchain    │
              │ On-chain Action  │
              └──────────────────┘
```

***

## System Properties

### Self-Custodial by Design

The architecture is designed so that users retain control over their assets.

NOXCAT provides the interface, identity layer, and execution coordination, but user assets remain controlled through self-custodial wallet infrastructure.

### Identity Abstraction

Users interact through UID-based identity rather than manually relying on wallet addresses.

This improves usability, reduces address-related mistakes, and creates a foundation for social finance.

### Multi-Wallet Support

A single UID may manage multiple wallets.

This allows users to separate assets, strategies, or accounts while maintaining a unified identity across the ecosystem.

### Multi-Chain Compatibility

The architecture supports multiple blockchain networks under a single user experience.

Users can access assets across different chains without needing to treat every network as a separate product environment.

### Execution Compatibility

Although the user experience is abstracted, the underlying execution remains compatible with blockchain standards.

Addresses, transactions, smart contracts, and supported networks continue to operate according to their native blockchain rules.

***

## Why This Architecture Matters

Traditional wallets often make blockchain addresses the center of the user experience.

NOXCAT separates **identity** from **execution**.

This allows the wallet to provide a simpler and more human-centered experience while preserving the transparency and composability of blockchain infrastructure.

In practice, this means:

* Users can interact with identities instead of addresses.
* Wallets can support multiple chains under one experience.
* Social finance becomes easier to build.
* Advanced users can still access address-level control.
* Future systems such as reputation, credit, governance, and smart accounts can be built on top of the same identity layer.

The result is a wallet architecture designed for both everyday users and future financial infrastructure.