Support

How to get help.

Five channels, each with a clear scope. The Vouch Assistant answers most "how does X work" and "give me a sample of Y" questions in seconds; the other four are for normative specification questions, implementation bugs, community-level discussion, and security disclosures.

For quick answers

Vouch Assistant

A retrieval-grounded assistant that knows the specification, the SDKs, the conformance levels, and the compliance mappings. Every reply is itself signed by a real Vouch credential. Use the web chat for the fastest path, send an email if you prefer text in your inbox, or run one of the AI-tool packages on your own subscription (Claude Skill, OpenAI Custom GPT, Gemini Gem).

For specification questions

open standards body

The mailing list is the right venue for normative questions about the specification, transition pathways to the VC Working Group, and proposed clarifications.

For implementation bugs

GitHub Issues

Bugs in the Python, TypeScript, or Go reference implementations belong on the issue tracker. Include the SDK version, a minimal reproducer, and the cross-language scenario if applicable.

For community discussion

Discord

Real-time discussion, quick questions, and integration help. Channels for general discussion, ideas and feedback, dev-discussion, support, and github-activity.

For security disclosures

Private security channel

Do not file public GitHub issues for vulnerabilities. The disclosure process and PGP key are documented in SECURITY.md. The editor will acknowledge within 48 hours and coordinate a disclosure timeline.

§ II

Run the assistant on your own AI subscription

The same canonical Vouch knowledge that powers the web chat is also packaged for three other AI tools, so you can ask Vouch questions inside the interface you already use. These run on your plan, not ours.

§ III

Before opening an issue

A quick checklist that resolves most of the questions we see:

  1. Check the CHANGELOG. The feature may already have shipped (or been deprecated) in a version you do not have. Current release is v1.6.0.
  2. Search the FAQ. Most cross-language verification mismatches, install failures, and verifier rejections have a known cause.
  3. Search closed GitHub issues. If somebody hit it before, the resolution is usually in the issue thread or referenced commit.
  4. Reproduce against the published test vectors. If a Python-generated test vector verifies in your TypeScript or Go code, the bug is probably in your integration; if not, it is probably in the SDK.
  5. Include the version, OS, and the minimal reproducer. "It fails for me" is not actionable; a 10-line script that fails is.