Discord + Substrate Wallet Integration

Why Discord + Substrate Wallets is worth wiring up

In a Polkadot-ecosystem community, membership tiers usually derive from on-chain state rather than from tenure or chat volume. Wallet linking makes that enforceable: roles follow verified holdings, so a holders channel stays a holders channel after tokens move, and quests can be gated to the addresses a programme is actually meant to reward.

What teams use it for

• Polkadot parachains: separate collator, nominator, and holder roles so channel access reflects on-chain role rather than self-description.
• Substrate dApps: gate testing quests to wallets that have interacted with the contract, which filters out participation farming.
• On-chain governance: derive voting-discussion access from holdings so proposal channels are not open to unverified accounts.
• Allowlist verification: check eligibility from the chain instead of collecting addresses in a form nobody can audit later.

Setup notes, in order

• Enable wallet linking before creating gated quests, so the first gated quest is not blocked by an unverified membership base.
• Decide the snapshot rule in advance: a role tied to current holdings behaves differently from one tied to a point in time.
• Create the gated quest on a channel only verified members can see, so ineligible members are not shown a reward they cannot claim.
• Distribute to verified holders in batches you can reconcile, because on-chain reward distribution is the step disputes are about.

Mistakes that cost the most

• Collecting wallet addresses manually and reconciling them by hand, which does not survive the second campaign.
• Gating on a snapshot taken after an announcement, which rewards whoever bought the news rather than whoever held.

Setup steps

1. Enable wallet linking in server settings
2. Configure Substrate connection
3. Create wallet-gated quests
4. Distribute rewards to verified holders

FAQ