# Technical Architecture

#### **1. Client Layer**

* Local key storage and signing
* Transaction review, simulation, and confirmation
* DApp interactions via WalletConnect and in-app browser
* Cold and hot wallet execution modes\
  This layer never exposes private keys to external systems.

#### **2. Service Layer**

A set of stateless services that support wallet operations without taking custody of user assets.

* **Routing & Execution**\
  Normal transactions and UGF-abstracted cross-chain actions are routed through standardized API flows.
* **Portfolio & Price Engine**\
  Multi-chain balance aggregation, token metadata, and pricing.
* **UGF Integration**\
  Quote generation, fee calculation, and cross-chain forwarding logic.

This layer improves UX but is not required for users to retain control over assets.

#### **3. Chain Integration Layer**

Connects to multiple networks through RPC providers, indexers, and relayers.

Supports:

* EVM chains
* Solana
* Sui
* Tron

#### **4. AI & Analytics Layer**

Used for insights and assistive intelligence.\
Does **not** make autonomous actions.

Provides:

* PTI signals
* Gas fee insights
* Pattern recognition
* Risk indicators


---

# 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://tychi.gitbook.io/tychi-whitepaper/core-principles/technical-architecture.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.