Getting Help
Last updated: 16 August 2026
There's a Get help button in the bottom-right corner of every page, including the landing page. You don't need to be signed in to use it.
Pick what it's about
The category isn't decoration — it decides where your message goes and who sees it.
| Category | Use it for |
|---|---|
| Bug | Something is broken or doesn't do what it says |
| Verification | Anything about identity checks (KYC) |
| Idea | A change you'd like to see |
| Help | You're stuck and need a hand |
| Other | Anything that doesn't fit the rest |
Verification questions are handled privately
This is the one worth knowing about.
Bug reports, ideas and help requests are posted to a public Telegram group that anyone can read without joining. That's deliberate — it means other contributors can see what's already been reported and add to it.
Verification questions are not. They go directly to the team as a private message and are never posted to that group, or to any other public channel.
The reason is that a verification question is identifying by nature. Even a stub saying "somebody asked about KYC at 14:32" can be matched against everything else in the group at that moment, which would defeat the point of not naming you. So nothing is posted at all.
Choose Verification and tell us what's stuck — the status you can see, and what happened. Don't include ID numbers, or photos of documents. We don't need them to answer "why is mine stuck", and no legitimate support process will ask you for them in a chat box.
What we can see
Whatever you type, the page you were on, and your browser's user-agent string (which helps reproduce a bug). If you're signed in, your GitHub username is attached — resolved from your session, not typed in, so nobody can file a report as somebody else.
Your IP address is recorded against the report for abuse investigation and is never forwarded to Telegram or Discord.
A screenshot is optional. For the public categories, please don't include anything in it you wouldn't post publicly.
Your report is saved before we try to send it
When you press Send, the report is written down first, then delivered. If a delivery channel is down, your report still exists and reaches us later.
That's why you'll only ever see an error if the save itself failed — and in that case your text stays in the box so you can try again. A success message means it's recorded, not merely that a message was fired off somewhere.
What happens next
There's no ticket number and no status page yet. Replies come through however you contacted us or via your GitHub account. If something is urgent and you've heard nothing, send it again and say it's a follow-up — duplicates are cheaper than a stuck contributor.