Resources · Support
Reach the team.
Four channels. The feedback inbox is the primary loop, issues, integration friction, and the bounty-cohort feedback all funnel there.
Channels
Pick by signal
Feedback inbox
docs/feedback/inbox/ on the SDK repo
Reproducible friction with a concrete surface.
SLA: Triaged weekly. Major entries become PRs within a release cycle.
security@tokenops.xyz
Privilege escalation / money loss / ACL bypass / signature forgery.
SLA: 48-hour first response. Same-day for serious reports.
Zama Discord (#tokenops)
Discord channel inside Zama's community
Synchronous integration questions during the bounty cohort.
SLA: Best-effort during the cohort window. Out-of-cohort: file an inbox entry.
GitHub Issues
tokenops-sdk repo
Public bugs that don't fit the feedback-inbox shape (e.g. a CI break).
SLA: Linked to feedback inbox at triage time.
What we'll need
Before you reach out
Reproduction checklist
(1) SDK version (npm view @tokenops/sdk version). (2) Chain id + network (Sepolia / mainnet / Anvil). (3) The tx hash if it broadcast. (4) The wallet address that signed (we can read public state from it; don't share the private key). (5) A 5-line repro snippet. Anything more than that goes in a gist linked from your message.Self-serve first
Where to look before asking
Cmd+K
Search 215 hooks + every concept + every recipe in one keystroke.
/concepts/errors
Per-class recovery patterns. Most production failures map to a known class.
/llms.txt
Pipe to your AI assistant, every page in one fetch. Often faster than a Discord round-trip.