Security
Reporting a vulnerability
Email security@noktoprotocol.org. Do not open a public issue, a pull request, or a discussion thread.
Useful to include: what you found, how to reproduce it, which component and version, and what you think an attacker gets. A rough report sent early is better than a polished one sent late.
You can expect an acknowledgement within three working days and an assessment within ten. If you do not hear back, assume the mail was lost rather than ignored, and send it again.
There is no bug bounty. Saying so up front is fairer than letting you find out afterwards.
security@noktoprotocol.orgScope
This repository: the Compact contracts and circuits, the @nokto-protocol/* packages, and the conformance vectors. Cryptographic breaks, invariant bypasses, disclosure leaks, and anything that lets a party prove a statement it should not be able to prove are the findings that matter most.
Vulnerabilities in Midnight itself, in the Compact toolchain, or in a third party's integration belong to those projects; we will help route a report if you are unsure where it goes.
Status
This protocol is unaudited and pre-1.0. No external review of the circuits or the cryptography has been done. The invariants are tested, which is not the same as having been attacked by someone whose job is to break them.
Deployment is blocked upstream, nothing is published to npm, and nothing here should be anywhere near real value or real personal data. A finding against this codebase is still worth reporting — the point of reporting now is to fix it before any of that changes.