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

# Architecture

LONGRISE AI's complete computing infrastructure, security framework, and data flow.

***

## Computing Infrastructure

Twin Engine throughput is directly determined by physical infrastructure. The compute cluster and exchange connectivity paths are designed to minimize latency.

| Item                     | Detail                                                                         |
| ------------------------ | ------------------------------------------------------------------------------ |
| Compute Cluster          | GPU cluster (NVIDIA H100 Tensor Core-based), NVLink inter-node interconnect    |
| Exchange Connectivity    | Singapore-region proximity hosting · redundant API gateways to major exchanges |
| Data Pipeline Throughput | Kafka cluster processing up to 3.2 million messages per second                 |
| Storage                  | Dedicated columnar time-series database + cold archive, dual-layered           |
| Failover Structure       | Active-active redundancy, average regional failover time of 1.8 seconds        |
| Platform Uptime          | 99.97% (cumulative, verified over 21 months)                                   |

## Security Framework

| Layer                | Technology                                  | Role                                                                                                                                               |
| -------------------- | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| Wallet Segregation   | Cold/hot wallet separation                  | 90%+ of operating assets held in cold wallets; only API-connected operating funds held in a separate hot wallet — minimizes hacking and theft risk |
| Authentication       | 2FA · email verification                    | Protects member identity                                                                                                                           |
| Transaction Security | Transaction password                        | Dual protection for withdrawals and transactions                                                                                                   |
| Encryption           | AES-256 + TLS 1.3                           | Protects data in transit                                                                                                                           |
| API Key Management   | Distributed, encrypted storage per exchange | Limits exposure to a single exchange even if a key is compromised — prevents full asset exposure                                                   |
| Token                | SPL (Solana) + multi-signature              | Transaction verification                                                                                                                           |
| Monitoring           | 24/7 AI monitoring                          | Detects abnormal transactions                                                                                                                      |
| Audit                | Quarterly external audit (CertiK planned)   | Ongoing verification                                                                                                                               |

## AI Algorithm Risk Management Framework

Where security protects asset custody, this framework controls the risk inherent in AI operations. The following four principles operate automatically alongside every trade executed by the HFT Quant Engine.

| Item                            | Detail                                                                                                                                 |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Automatic Stop-Loss System      | Maximum loss limits pre-set per position · automatic liquidation at threshold to contain losses                                        |
| Asset Diversification Principle | Avoids concentration in a single exchange or position · mitigates systemic risk through multi-exchange, multi-strategy diversification |
| Real-Time Volatility Monitoring | Automatic strategy switching on volatility spikes · automatic position reduction or standby mode under abnormal market conditions      |
| Transparent Trade Logging       | Timestamped record of every operational trade · full traceability for internal audit and regulatory submission                         |

## Data Flow

From the moment a member is active on the platform to the moment revenue reaches their wallet, all LONGRISE AI processing runs through a 5-stage automated pipeline, repeating daily at UTC 00:00 without human intervention.

1. **Member Activity Collection** — transaction records, login patterns, referral activity
2. **Casino AI Analysis** — pattern recognition, risk assessment, recommendation generation
3. **HFT Quant Execution** — signal detection, trade calculation, arbitrage capture
4. **Revenue Distribution** — base dividend + referral bonus + team bonus + CNYT allocation
5. **Monthly Payout** — USDT internal wallet + CNYT blockchain distribution


---

# 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, and the optional `goal` query parameter:

```
GET https://doc.longrise.ai/technology/architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.