report vulnerabilities privately. never in public issues, pull requests or discussions.
- github: security tab -> report a vulnerability
- email: security@octra.org
include the repo, commit or release, impact, and steps to reproduce.
every submission goes through octra's automated security pipeline, which has been running since 2026-07-24 and has reviewed every public repository. every finding it has recorded is timestamped. a submission that overlaps an earlier record is not eligible.
only genuinely new, reachable, protocol-level findings that don't require user action will be considered.
we aim to acknowledge serious submissions within 3 business days and to fix within 90 days. excessively generated and irrelevant reports will be ignored. we allow public disclosure only when an issue is fixed.
| severity | reward |
|---|---|
| critical | up to 1,000,000 oct |
| high | up to 250,000 oct |
| medium | up to 50,000 oct |
| low | up to 5,000 oct |
reviewers set severity and likelihood at their discretion. a finding that is unlikely to occur will not be rewarded. awarded oct may be vested for up to 24 months. submissions may require a working proof of concept or a reproduction on devnet.
lite_node and webcli.
- devnet tests allowed with amounts less than 10 oct.
- mainnet tests NOT allowed. read only.
- no denial of service, spam or load testing.
- extortion attempts and unauthorized public disclosure forfeit any reward.