Support and incident reporting

Status: Not decided

A public support and security-reporting contact has not been supplied.

Q-009 records the gap. The backend security document asks for private reporting, but its referenced maintainer contact is absent from the available README. This page therefore supplies no invented address, response deadline or incident promise.

What an eventual report should contain

Preserve the action attempted, the displayed error code, the relevant network and transaction identifier, and the time it occurred. Explain the expected and observed result. Those details help distinguish an application failure from a transaction that has already been accepted.

Do not include secret keys, recovery phrases, reveal secrets, raw income documents or hardship reasons in a public issue. An authorized responder should request sensitive evidence only through an approved protected channel. A public payment identifier can already link activity to a wallet.

Before support opens

Kunal needs to supply the contact, ownership, escalation and security-reporting route. The published workflow must distinguish routine help from a suspected vulnerability and specify where to send evidence. Until then, no form shown in a design is treated as a working support service.

For present development status, see known limitations. The data map explains why different evidence requires different recipients.