Skip to content
HomeEnter terminal

Contact

The channels below are the only ones operated by the platform. Anything else using this name is not us.

A row that says To be published is empty on purpose. Do not guess an email.

Purpose Channel
Security disclosure To be published
Legal, privacy, and terms To be published
General and support To be published
Announcements X · Telegram · Discord

These three announcement accounts are also linked from the documentation header. Security, legal, and support mailboxes are not published yet; Terms §11, Privacy §7, and Security Disclosure still wait on those.

This matters more than the list above. Impersonation is the most common way people in this market lose funds, and it does not require breaking anything.

We will never ask for your private key, seed phrase, or a signature that grants spending rights over your wallet. Not in support, not to “verify” an account, not to “recover” a failed transaction, not during a launch. Anyone who asks — using any channel, any name, any urgency — is not us, and the conversation is already an attack.

We do not send you direct messages first. If a message from “support” arrives before you contacted anyone, treat it as hostile regardless of how correct it looks.

Check the domain, not the name. Display names, avatars, and handles are cheap to copy. The addresses on this page, reached from this documentation site, are the reference — not a link someone sent you.

Because the platform is non-custodial, some requests cannot be fulfilled by anyone, including us:

Request Why not
Reverse, cancel, or refund a transaction Once submitted it belongs to the chain
Recover a lost key or seed phrase We have never held it
Recover funds sent to a wrong address Same
Restore a locally created wallet after clearing browser data It lived only in your browser. Export before clearing
Delete your account There is no account — see Privacy

Anyone offering to do any of the above for a fee is running a recovery scam.

We are a small team. Security reports are handled first and on the timeline in Security Disclosure, once a channel exists. Everything else is answered as capacity allows. We would rather say that than publish a response target we cannot hold.