# What Echo Poly is?

Echo Poly is a copy-trading layer for Polymarket.

It is built for users who want to follow selected Polymarket traders without pretending that copy trading is magic. The system is designed to observe source activity, calculate proportional follower size, apply risk controls, execute only when conditions are acceptable, and report the reason behind each decision.

At the product level, Echo Poly has three surfaces:

* A public website for education, pricing, onboarding, and trust.
* A Telegram bot for identity, alerts, controls, and operator interaction.
* A backend follower system that monitors public activity, evaluates source trades, and routes execution decisions.

## The Core Promise

Echo Poly is designed around one principle:

> A copied trade must be explainable before it is scalable.

If a source buys a contract, the follower system does not blindly mirror it. The system asks:

* Is the source action recent enough?
* Has the market moved too far?
* Is there enough liquidity?
* Would this create same-side or category concentration?
* Is the follower account eligible under its plan?
* Is the copied size large enough to matter and small enough to survive?
* Is execution currently paused or restricted?

The result can be:

* Copied.
* Scaled down.
* Delayed.
* Skipped.
* Blocked.

The user can understand why.

## Why Telegram First

Telegram is the control room because trade decisions are time-sensitive.

The website is useful for context, plans, metrics, and account surfaces. Telegram is better for immediate alerts:

* Trade copied.
* Trade skipped.
* Price drift detected.
* Risk cap reached.
* Account setting changed.
* System health event.

The product is therefore not a website with a Telegram link. It is a Telegram-native trading assistant with a website dashboard.

## What Makes Echo Poly Different

Many copy-trading products try to sell the fantasy of perfect mirroring. Echo Poly does the opposite.

It makes the imperfections visible:

* Source fills are not follower fills.
* Markets move during delay.
* Order books can be thin.
* Public wallet activity can arrive late.
* Winning sources can still create bad copied entries.
* A trade can be correct and still oversized.

The edge is not only in finding sources. It is in filtering, sizing, skipping, and reporting.

## Public And Private Layers

Echo Poly has a public methodology and a private source engine.

**Public:**

* Copy sizing formula.
* General guardrail categories.
* Risk principles.
* Product behavior.
* Research framework.
* Backtesting methodology.

**Private:**

* Source identities.
* Source weights.
* Live source basket.
* Ranking formulas.
* Inclusion thresholds.
* Proprietary execution settings.

This split is intentional. The user deserves transparency about how the product behaves, while the system protects the exact map of its edge.


---

# 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://docs.echopoly.xyz/what-echo-poly-is.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.