Join the community
Shinzo is open source and the team is easy to reach. Whether you're running a node, building an app, or just curious about the protocol, here's where to go and what to expect from each channel.
Discord
The Shinzo Discord is the main hub. It's where onboarding happens, where node operators ask setup questions, and where most of the day-to-day technical conversation lives. If you're not sure where to start, start here.
You'll find channels for:
- Onboarding and support: help getting a Generator or Host client running.
- Developer discussion: View authoring, app-sdk questions, GraphQL schema design.
- Operator discussion: hardware, deployment examples, tuning.
- Announcements: testnet updates, releases, and protocol changes.
GitHub
All of Shinzo's code lives under the shinzonetwork organization. The repos you'll most likely touch:
- docs: this site. Report broken links, missing pages, or doc feature requests here.
- shinzo-generator-client: the Generator client.
- shinzo-host-client: the Host client.
- app-sdk: the Go SDK for embedding Shinzo in an application.
- viewkit: the CLI for building and deploying Views.
To contribute code or documentation, see Contributing. To report a bug, see Get help.
X
Follow @shinzonetwork on X for announcements, release notes, and project updates. It's a read-only channel, so if you need a response, use Discord or GitHub.
Telegram
The Telegram group is a lighter-touch community channel for general discussion and questions. For technical support or onboarding help, Discord will get you a faster answer.
Which channel to use
| You want to... | Go to |
|---|---|
| Get help running a node or building an app | Discord |
| Report a bug or request a feature | GitHub Issues |
| Contribute code or documentation | Contributing |
| Follow announcements | X |
| Ask a general question | Discord or Telegram |
Community guidelines
Be respectful and patient. Most people answering questions in Discord are doing so on their own time. When asking for help, include the details that matter: what you did, what you expected, what happened instead, and the versions you're running. The bug report checklist is a good template even for Discord questions.