> For the complete documentation index, see [llms.txt](https://polysync-1.gitbook.io/psync/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polysync-1.gitbook.io/psync/1.-welcome-to-polysync/1.2-technical-architecture.md).

# 1.2 Technical Architecture

#### Data Collection and Aggregation

PolySync collects real-time blockchain data from all major token networks. Data points include transaction records, wallet balances, token price histories, and trading volumes. Our infrastructure relies on decentralized node providers and blockchain explorers to ensure that the data collected is accurate, up-to-date, and secure.

#### Data Processing & Analytics Engine

Our advanced analytics engine processes the collected data to derive insights on wallet performance. The engine performs functions such as:

* **Return on Investment (ROI) Analysis**: Determines the profitability of trades based on entry and exit prices.
* **Risk Metrics Calculation**: Assesses risk profiles of wallets by evaluating the volatility and diversity of assets in their portfolios.
* **Trading Patterns Identification**: Utilizes machine learning algorithms to detect recurring trading behaviors that correlate with profitable outcomes.

#### User Interface and Bot Integration

PolySync’s analytics and insights are accessible via a user-friendly web interface and an integrated chatbot. By submitting a token address through the bot, users can instantly access Top Trader and P\&L data. Features of the interface include:

* **Token Search Functionality**: Quickly access information on any token by inputting its address.
* **Interactive Charts and Metrics**: Visual representations of wallet data for easy interpretation.
* **Custom Alerts and Notifications**: Get notified when specific high-performing wallets make significant moves.


---

# 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://polysync-1.gitbook.io/psync/1.-welcome-to-polysync/1.2-technical-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.