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

# 9. Technical Architecture

<figure><img src="/files/5e96nh2KUAW6U4SRpqvr" alt=""><figcaption></figcaption></figure>

### 9.1 Architecture Overview

BTSChain is designed as a mobile-app-centered AI Community Metaverse that connects AI services, user profiles, community functions, BTSc payment, staking-related features, and safety systems into a practical service architecture.

The initial architecture focuses on usability, controlled automation, wallet signature-based BTSc payment, server-side AI processing, and separate DeFi contract-based staking functionality.

The system is designed to support AI Avatar creation, AI Social Proxy activity, relationship discovery, Daily Social Reports, membership access, and policy-based moderation.

***

### 9.2 Technical Design Principles

<table><thead><tr><th width="303">Principle</th><th>Description</th></tr></thead><tbody><tr><td><strong>Mobile-first</strong></td><td>Initial user experience is centered on the mobile application.</td></tr><tr><td><strong>Modular design</strong></td><td>AI, application, data, blockchain, integration, and security layers are separated for maintainability.</td></tr><tr><td><strong>Wallet signature-based payment</strong></td><td>BTSc payment is authorized through wallet signature-based transactions.</td></tr><tr><td><strong>Privacy-conscious data structure</strong></td><td>Personal information and conversation contents are not stored directly on-chain.</td></tr><tr><td><strong>Separate DeFi staking</strong></td><td>Staking-related functions are implemented through a separate DeFi contract.</td></tr><tr><td><strong>Safety by design</strong></td><td>Logs, approval controls, activity restriction, and moderation are included from the architecture level.</td></tr></tbody></table>

***

### 9.3 High-level System Layers

| Layer                          | Main Function                                                              | Key Components                                                            |
| ------------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
| **Mobile Application Layer**   | Provides the primary user interface.                                       | AI Avatar setup, membership, reports, approval, community access          |
| **AI Services Layer**          | Runs AI-driven service logic.                                              | AI Avatar Engine, AI Social Proxy, Matching Engine, Report Engine         |
| **Application Backend Layer**  | Manages accounts, service access, community functions, and business logic. | User service, membership service, community service, notification service |
| **Data & Storage Layer**       | Stores service data and logs.                                              | User DB, activity logs, report data, relationship memory, cache, backup   |
| **Blockchain & Payment Layer** | Handles BTSc utility and wallet-based verification.                        | BTSc token, membership payment, wallet signature verification             |
| **DeFi Staking Layer**         | Provides staking-related membership features.                              | Separate staking contract, tier enhancement, staking pool logic           |
| **Safety & Moderation Layer**  | Supports compliance, safety, and platform control.                         | Logs, reports, blocking, policy engine, moderation tools                  |

***

### 9.4 Mobile App-centered Service Structure

The initial BTSChain service is designed around a mobile app experience. Users create AI Avatars, configure social preferences, review Daily Social Reports, approve sensitive actions, and manage membership status through the mobile application.

A web dashboard or admin portal may be used for platform operation, moderation, partner management, analytics, and internal administration, but the primary user experience is mobile-first.

***

### 9.5 Wallet Signature-based BTSc Payment

BTSChain does not integrate the existing BTSChain Mobile Wallet into the initial rebranded service architecture. Instead, BTSc payments are designed to be processed through wallet signature-based transactions.

This approach allows users to authorize BTSc membership payments through supported wallets while keeping membership verification, service access, and user tier status synchronized within the BTSChain application layer.

***

### 9.6 AI Services Layer

<table><thead><tr><th width="247">Module</th><th>Function</th></tr></thead><tbody><tr><td><strong>AI Avatar Engine</strong></td><td>Creates and manages user profile-based AI Avatars.</td></tr><tr><td><strong>AI Social Proxy System</strong></td><td>Allows AI Avatars to participate in communities automatically.</td></tr><tr><td><strong>Matching Engine</strong></td><td>Supports friend, hobby, interest, community, and dating-oriented discovery.</td></tr><tr><td><strong>Recommendation Engine</strong></td><td>Suggests communities, users, next actions, and relationship opportunities.</td></tr><tr><td><strong>Daily Report Engine</strong></td><td>Generates once-per-day activity reports and social summaries.</td></tr><tr><td><strong>Emotion Analysis Module</strong></td><td>Processes summarized emotion signals for Normal and Pro reports.</td></tr></tbody></table>

***

### 9.7 Data & Storage Layer

AI conversation data, activity logs, Daily Social Reports, Relationship Memory, and moderation logs are stored on platform servers for service operation, reporting, safety review, and policy enforcement.

All logs are retained for 6 months and deleted thereafter according to the platform data retention policy. Users may delete AI Avatar data except for required logs retained for safety, abuse prevention, and platform operation purposes.

Personal information and conversation contents are not stored directly on-chain.

***

### 9.8 Blockchain & Smart Contract Layer

<table><thead><tr><th width="284">Contract / Component</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>BTSc Token Contract</strong></td><td>BEP-20 utility token used for membership and ecosystem utility.</td></tr><tr><td><strong>Membership Payment Logic</strong></td><td>Verifies BTSc payment and updates Normal / Pro membership status.</td></tr><tr><td><strong>Separate DeFi Staking Contract</strong></td><td>Supports Pro User staking access and membership tier enhancement.</td></tr><tr><td><strong>Reward Pool Logic</strong></td><td>Supports platform-defined participation and contribution rewards.</td></tr><tr><td><strong>Operation Pool Allocation</strong></td><td>Supports AI infrastructure, operation, moderation, and maintenance.</td></tr><tr><td><strong>Staking Pool Allocation</strong></td><td>Supports staking-related membership features and ecosystem participation.</td></tr></tbody></table>

***

### 9.9 Separate DeFi Staking Contract

Staking-related functions are planned to be implemented through a separate DeFi contract, independent from the AI communication and community service layer.

The staking function is designed for Pro User access, membership tier enhancement, ecosystem participation, and platform-defined benefits. It is not designed to guarantee fixed income, investment returns, token price appreciation, or risk-free rewards.

***

### 9.10 Security, Compliance & Moderation Layer

<table><thead><tr><th width="199">Area</th><th>Architecture Control</th></tr></thead><tbody><tr><td><strong>Data encryption</strong></td><td>Encryption for transmission and storage where applicable.</td></tr><tr><td><strong>Wallet authorization</strong></td><td>Wallet signature-based transaction approval for BTSc payments.</td></tr><tr><td><strong>Access control</strong></td><td>Role-based permission management for users, admins, partners, and internal systems.</td></tr><tr><td><strong>Activity logs</strong></td><td>AI conversations and key actions are logged for safety, reporting, and moderation.</td></tr><tr><td><strong>Moderation tools</strong></td><td>Reporting, blocking, policy enforcement, and activity restriction.</td></tr><tr><td><strong>Data retention</strong></td><td>Logs retained for 6 months and deleted according to policy.</td></tr><tr><td><strong>On-chain policy</strong></td><td>No direct storage of personal information or conversation contents on-chain.</td></tr></tbody></table>

***

### 9.11 Data Flow Overview

<table><thead><tr><th width="84" align="right">Step</th><th>Flow</th></tr></thead><tbody><tr><td align="right">1</td><td>User creates or updates profile and AI Avatar settings in the mobile app.</td></tr><tr><td align="right">2</td><td>Application backend validates account status, membership tier, and service permissions.</td></tr><tr><td align="right">3</td><td>AI Services Layer processes AI Avatar activity, social proxy interaction, matching, and reports.</td></tr><tr><td align="right">4</td><td>Data Layer stores required logs, report data, and relationship memory according to retention policy.</td></tr><tr><td align="right">5</td><td>Wallet signature-based BTSc payment verifies Normal or Pro membership access.</td></tr><tr><td align="right">6</td><td>Separate DeFi staking contract handles staking-related membership features for eligible Pro Users.</td></tr><tr><td align="right">7</td><td>Safety and moderation systems monitor reports, restrictions, and sensitive approval requirements.</td></tr></tbody></table>

***

### 9.12 Key Message

BTSChain’s technical architecture is designed to make AI-assisted community participation practical, scalable, and controllable.

The system connects mobile app access, AI Avatar services, wallet signature-based BTSc payment, server-side data processing, separate DeFi staking contracts, and safety controls into one service-oriented architecture.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://doc.btschain.net/9.-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.