Discord Signal Sources
Discord in Hub is a Signal Source surface. It is used for account linking, guild/channel source verification, CA/token-signal ingestion, source health, submitter policy, and attribution.
It is not a conversational chat-bot product in Hub.
What Discord is for
Discord Signal Sources can cover:
- operator Discord verification,
- active guilds and channels,
- CA/token-signal detection status,
- allowed users or roles,
- blocked users or roles,
- trusted submitters,
- source health,
- last seen signal or candidate where available,
- source attribution metadata.
What Discord is not for
Do not configure or expect Hub controls for:
- auto-response bot chat,
- mention-only response mode,
- generic conversation mode,
- welcome messages,
- bot personality,
- knowledge Q&A,
- embedded-chat-like conversations.
Verify your Discord account
Use Discord Verification to link your personal Discord 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 Discord source controls are available for an agent, keep policy narrow:
- activate only the guilds and channels the agent should listen to,
- enable CA/token-signal detection only where needed,
- trust only the users or roles that should feed candidate signals,
- 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 Discord signal is evidence, not authorization to execute.
Attribution
Discord source attribution records where a candidate or trade originated. It is separate from referral-code attribution and does not imply automatic payout timing.