Skip to content
No mailbox — every route is public or private by design

There is no sales team and no support desk. Maintainers are not named in the repository, so conversations happen where they can be read and answered in the open.

Every conversation stays in a public or private repository channel

  • GitHub issues
  • Private advisory
  • Documentation
  • No mailbox

This page has no mailbox. The button opens a new GitHub issue on the protocol repository with the fields above filled in, and you post it from there. For a suspected vulnerability, use the repository’s private advisory form instead of a public issue.

“Open a private channel with the upgrade multisig. Do not publish an unfixed exploit.”
security/INCIDENT_RESPONSE.md, first hour

That is the one case where a public issue is the wrong route. Everything else belongs in the open.

  • GitHub issues

    Bugs, questions about an instruction, and anything about the SDKs or the node process.

    Protocol issues

  • Private security advisory

    A suspected vulnerability goes to the repository's private advisory form, never to a public issue.

    Report privately

  • Documentation

    The written protocol surface, the decision records, and the guides for the SDKs and the CLI.

    Read the documentation

  • X

    Milestone notes and release announcements.

    Follow on X