Polkadot Developer Support¶
The documentation answers most questions, but sometimes you need more: an answer to a specific problem, a working example, or someone to talk to. This page lists where to find that help.
If something in the documentation is missing, unclear, or broken, open a documentation issue.
Choose the Right Channel¶
Developer support is split by who operates the service you are using. Find your problem in this table before you ask, so it reaches the team that can resolve it.
| Your problem involves | Where to ask |
|---|---|
| Polkadot SDK, runtime development, parachains, or core Polkadot infrastructure | Polkadot Developer Support |
Paseo Next v2, or Parity's tools for building Polkadot Products, such as the playground CLI | Polkadot Developer Support, or the tool's own GitHub repository for bug reports |
Products Devnet, PCF's Polkadot App builds (including the Google Play app), deploying a Polkadot Product to Products Devnet, or pad | PCF Developer Support: products-devnet-issues, or #devnet-discussion on the Polkadot Discord server |
The Polkadot Community Foundation (PCF) operates Products Devnet and its Polkadot App builds using open-source technology developed by Parity. Parity does not operate those services, so the Polkadot Developer Support channels cannot resolve problems with them.
Support Channels¶
Use one of the channels below to get live technical support or ask questions.
-
Telegram: Polkadot Developer Support
- Who’s there: DevRel team and active developer community.
- Response time: Within 2 business days, usually faster.
- Topics: Polkadot SDK, runtime development, parachains, core Polkadot infrastructure, and Polkadot Products built with Parity's tools. For PCF-operated services, see Choose the Right Channel.
-
Discord: Polkadot Official Server
- Smart contracts: Ask in
#solidity-smart-contractsand#ink_smart-contracts. - General developer support: Ask in
#dev-discussion. - Response time: Within 1 business day, usually faster.
- Smart contracts: Ask in
-
Matrix: Polkadot Developer Support
- Who’s there: Parity, W3F, DevRel, and community contributors.
- Response time: Within 1 business day, usually faster.
- Topics: Polkadot SDK, runtime development, parachains, core Polkadot infrastructure, and Polkadot Products built with Parity's tools. For PCF-operated services, see Choose the Right Channel.
- Bridged with Telegram (all messages synced).
Community Resources¶
-
Stack Exchange
- Browse commonly asked technical questions.
- Ask your own and get detailed responses from experienced devs.
-
Reddit: r/Polkadot
- General discussions and community perspectives.
- Developer questions are welcome when tagged appropriately.
-
YouTube: @PolkadotNetwork
- Developer tutorials.
- Ecosystem interviews.
- Event recordings and walkthroughs.
-
X (Twitter): Official Accounts
- @PolkadotDevs: Updates for developers.
- @Polkadot: Network-wide news.
- @Kusamanetwork: Kusama-specific updates.
- @Web3Foundation: Grants, research, and ecosystem programs.
-
X (Twitter): Community Accounts
- @PolkadotDeploy: News from the deployment portal and tooling updates.
-
Polkadot Forum
- Join community discussions around the direction of the ecosystem.
-
Polkassembly: OpenGov
- Explore and vote on governance proposals for Polkadot and Kusama.
- Help shape the future of the network.
-
Subsquare: OpenGov
- Track, discuss, and vote on Polkadot OpenGov proposals.
- Stay informed on governance activity across the network.
AI Resources¶
-
AI Resources
Access documentation structured and optimized for use with large language models (LLMs) and AI tools. These resources help build AI assistants, power code search, or enable custom tooling trained on Polkadot’s documentation.
| Created: July 15, 2025