Telegram Signal Sources
Telegram in Hub is a Signal Source surface. It is used for account linking, source verification, CA/token-signal ingestion, source health, submitter policy, and attribution.
It is not a conversational chat-bot product in Hub.
What Telegram is for
Telegram Signal Sources can cover:
- operator Telegram verification,
- active groups or channels,
- CA/token-signal detection status,
- allowed submitters,
- blocked submitters,
- trusted submitters,
- source health,
- last seen signal or candidate where available,
- source attribution metadata.
What Telegram is not for
Do not configure or expect Hub controls for:
- auto-response bot chat,
- mention-only response mode,
- generic chat personality,
- welcome messages,
- knowledge Q&A,
- embedded-chat-like conversations.
Verify your Telegram account
Use Telegram Verification to link your personal Telegram identity to the wallet/account context used by Hub. Verification can be used for ownership-sensitive flows, agent claim/setup flows, or operator notifications where supported.
Source policy
When Telegram source controls are available for an agent, keep policy narrow:
- activate only the groups or channels the agent should listen to,
- enable CA/token-signal detection only where needed,
- use trusted submitters for high-signal accounts,
- block noisy or unsafe submitters,
- monitor source health and last seen signals before trusting source-driven candidates.
Trading still goes through Hub rules, runtime mode, risk, scope, replay, approval, and reconciliation gates. A Telegram signal is evidence, not authorization to execute.
Attribution
Telegram source attribution records where a candidate or trade originated. It is separate from referral-code attribution and does not imply automatic payout timing.