Got a technical question? You’re in the right place.
Whether you’re building with Midnight, exploring Compact, or debugging something tricky, this is where developers help each other out. Ask questions, share solutions, and learn together!
How to Ask for Help
When asking a question, please include as much context as possible to help others help you faster. Use the template below so it can be easily found, answered, and referenced by others in the future.
What are you trying to do?
Briefly describe the goal or task you’re working on.
What’s not working or unclear?
Explain the specific problem, error, or point of confusion.
What have you tried so far?
List all debugging steps, docs you read, code you wrote, etc.
Any relevant code or error messages?
Include any code snippets, error logs, or link to a GitHub repo if helpful. Use code blocks (```) to format.
Where are you asking from? (Optional but helpful)
Let us know if you’re working from a tutorial, SDK version, or part of the docs. Example: “I’m working from the bulletin-board tutorial, using SDK version 0.3.1”.
Tags
Be sure to add tags that are relevant to your question. This helps sort your technical questions so it’s easier to get an answer!
Here are a couple tags that might be helpful when writing a new topic:
- compact — Anything related to the Compact language: syntax questions, usage patterns, best practices, etc.
- previously-asked — Saw this question on Discord already? Post it here with this tag. If you know the answer, go ahead and reply to your own post—future builders will thank you!
- sdk — Questions about Midnight’s SDKs (e.g., TypeScript, Python). Use this when you’re running into issues, need guidance, or have tips to share.
- contract-development — Smart contract-specific topics: writing, deploying, testing, and debugging contracts on Midnight.
- tooling — Discussions about CLIs, language bindings, IDE integrations, and other tools you use when working with Midnight.
- zkp — Anything related to zero-knowledge proofs: general questions, implementation help, or educational resources.
- error-help — Use this when you’re stuck on a specific error and need help debugging. Bonus points for including logs or screenshots!
- best-practices — Advice or questions about how to approach things the “right” way—secure, efficient, or idiomatic development in the Midnight ecosystem.
- learning — For beginners or those exploring a new area of Midnight—great for asking “why” or “what does this mean?” style questions.