Get help

Stuck on something? Start here.

Where	Best for
Discord ↗	Quick questions, deploy help, talking to other builders and the team.
dig-store issues ↗	CLI bugs, feature requests, anything dig-store.
DIGHUb issues ↗	Web app / publish / domain problems.
Troubleshooting · FAQ · Error codes	Answers you can find without waiting.

Pre-release — expect rough edges

DIG is pre-release. If something is broken or confusing, that's worth reporting — it's how the rough edges get filed down. There are no dumb questions in Discord ↗.

Before you ask

You'll get an answer faster if you check these first:

1. Troubleshooting — the common failures and their fixes.
2. Error codes — look up the exact code you got (RPC -32xxx, a CLI exit code, or a DIGHUb code like SLUG_TAKEN).
3. FAQ — the questions that come up most.

How to file a good report

A report that gets answered fast includes:

• What you ran — the exact dig-store command (or the DIGHUb step), and what you expected.
• What happened — the full error message and any error code (e.g. exit code 12, RPC -32602, or DIG_INSUFFICIENT). See Error codes.
• Versions — digs --version, your OS; for the web, your browser and wallet.
• Reproduce it — the smallest set of steps that triggers it.

For CLI issues, re-run with --verbose (and --json if scripting) and include the output.

Never paste secrets

Don't share your mnemonic, your ~/.dig/seed.enc, a deploy key, or a private store's salt. Support will never ask for them.

Related

• Troubleshooting — fixes for the common failures
• FAQ — frequently asked questions
• Error codes — every error code in one table
• Changelog — what changed across the CLI, RPC, and window.chia
• Status — health of the DIG services
• Concepts & glossary — the vocabulary, defined once