> For the complete documentation index, see [llms.txt](https://hyperalpha.gitbook.io/hyperalpha-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperalpha.gitbook.io/hyperalpha-docs/platform-features/telegram-real-time-notifications.md). # Telegram Real-Time Notifications In the hyper-volatile perpetuals market, microsecond informational latency determines asset lifelines. HyperAlpha (hyperalpha.org) deeply integrates a 24/7/365 Telegram Intelligence Risk Bot, compressing account updates, execution telemetry, and systemic risk alerts into second-level pushes delivered straight to your palm. Even when you are completely away from your desk, you retain absolute, omniscient control over every trade. ### 1. Radical Activation & Capital Safety Mandates Users maintain complete sovereignty over their data push channels via the control interface located in the top-right quadrant of the terminal: * Engine Activation: Toggling the parameter to 【ON】 instantly initializes the real-time backend notification infrastructure. * Hard Access Barrier: To defend absolute capital preservation, HyperAlpha enforces a strict architectural rule: the Telegram notification engine must be verified as 【ON】 before any automated Copy Matrix campaign can be initialized. This structural setup guarantees that business-critical drawdown alerts reach your terminal during sudden liquidity crashes without delay. ### 2. Globalized Linguistic Localization To guarantee zero mathematical misinterpretations when processing high-priority quantitative indicators, HyperAlpha delivers fully localized message structures: * English: Meticulously tailored with standard international trading syntax and institutional terminology. * Traditional Chinese: Optimized with authentic financial nomenclature specifically compiled for active market participants across Taiwan, Hong Kong, Macau, and global Chinese quantitative trading desks. * Instant Telemetry Update: The moment a language tier is switched inside the control dashboard, the Telegram Bot immediately updates its core parsing library. ### 3. Cryptographic Handshake Protocol HyperAlpha utilizes specialized Interaction-Based Recognition tracking technology to achieve seamless, non-custodial binding between Web3 wallets and Telegram accounts: * Active Routing: Selecting the link routes your session directly to the verified HyperAlpha Copy-Trading Bot terminal. * The Secure Handshake: The exact millisecond the user triggers \[/START] inside Telegram, the engine programmatically captures your unique Telegram ChatID, mapping it securely to your HyperAlpha system identity. * Persistent Communication Channel: This is a zero-maintenance, single-setup protocol. The backend leverages this encrypted anchor ID to execute all subsequent business triggers, guaranteeing cryptographic privacy and delivery uniqueness. ### 4. Comprehensive Telemetry Matrix Delivered The system monitors your trading accounts 24/7/365 across the following granular dimensions: * Open Orders: Millisecond-level synchronization of your followed master trader’s (Pros or Retail profiles) initial market entries. * Closed Orders: Instant broadcasting of full or partial exits, highlighting precise Take-Profit (TP) and Stop-Loss (SL) execution values. * Order Tracking: Deep historical tracking of pending limit, market, and triggered conditional setups to keep your macro telemetry updated. * System Alerts: Immediate delivery of key framework changes and critical Hyperliquid API Key Expiration countdowns. ### 5. The Funds Security Sentinel (High-Priority Risk Controls) These represent the highest-priority, unthrottled alert classes designed to shield your available margin from unexpected market liquidations: * Equity & Drawdown Alerts: Prompt pushes dispatched when your total account net equity hits a pre-configured stop-loss boundary, or when a position's ROE breaches historical tolerance metrics. * Margin Calls: If the engine flags insufficient available margin to maintain active order blocks, a margin warning is compiled. To entirely eliminate notification fatigue and guarantee that real warnings are not ignored, these alerts are strictly rate-limited to a maximum of one push per hour. * Execution Deficit Reporting: Immediate logging of chain slippage protection overrides or automated order cancelations triggered by system timeouts. ### 6. Proactive Account Maintenance Manager Keeps your automated strategy engine completely optimized and functionally compliant: * API Health & Validation Tracker: Provides continuous checking of your protocol bridge connectivity, alerting you to sudden API key permission rollbacks or expiration threats so your automated strategies never drop. * Security Telemetry Logs: Instant logging of critical backend variable changes, including wallet re-authentications or modifications to sensitive margin risk parameters. * True Zero-Fee Transparency: HyperAlpha offers its entire copy-trading automation core and tracking apparatus with 0% platform service fees. 100% of the algorithmic alpha generated belongs entirely to your performance sheet. ### Quantitative Technical Architecture: OrderNoticeService To process millions of high-concurrency messages with 100% data fidelity and zero duplication anomalies, our OrderNoticeService processes information through a strict technical pipeline: $$\text{Execution Finalized} \longrightarrow \text{UID Mapping} \longrightarrow \text{Validation Scan} \longrightarrow \text{Loop Closure}$$ 1. Execution Finalized: The matching engine completes an order block on the ledger and logs the exact state variables into our distributed cluster database. 2. UID Mapping: The pipeline maps the execution address back to the master system UID to pull the validated Telegram ChatID anchor. 3. Validation Scan: For complex conditional or limit configurations, the service runs a rigid one-minute state-validation loop. A push notification is only dispatched once the order state is definitively verified on Hyperliquid as "Filled". 4. Loop Closure: The exact millisecond a message is accepted by the Telegram gateway, the database updates the status flag to 【DISPATCHED】, mechanically blocking duplicate notifications during peak high-frequency market events. ### Core Troubleshooting FAQ Q: Why is my Telegram Bot silent even though the terminal interface toggle is set to ON? * A: Inactive Cryptographic Session. Verify that you have explicitly engaged the \[/START] interface inside the official Telegram channel. Without this baseline user-initiated handshake, HyperAlpha's data router cannot programmatically fetch or write your ChatID to the ledger, causing the push queue to safely drop. --- # 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://hyperalpha.gitbook.io/hyperalpha-docs/platform-features/telegram-real-time-notifications.md?ask= ``` 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.