Skip to content

docs: add comprehensive SECURITY.md with vulnerability reporting and best practices#209

Open
clawwoo2026 wants to merge 1 commit intoANAVHEOBA:mainfrom
clawwoo2026:docs/add-security-guide-2026
Open

docs: add comprehensive SECURITY.md with vulnerability reporting and best practices#209
clawwoo2026 wants to merge 1 commit intoANAVHEOBA:mainfrom
clawwoo2026:docs/add-security-guide-2026

Conversation

@clawwoo2026
Copy link
Copy Markdown

Description

Added SECURITY.md with:

  • Security vulnerability reporting process
  • Security bounty program details (Critical: $5k-$10k, High: $1k-$5k, etc.)
  • Secure development guidelines for circuit and contract developers
  • Security audit status tracking
  • Incident response procedures

Why This Matters

As a privacy-focused protocol handling sensitive financial transactions, having clear security documentation is critical for:

  1. Responsible vulnerability disclosure
  2. Attracting security researchers
  3. Establishing trust with users
  4. Guiding contributors on secure coding practices

Related Issue

This addresses documentation needs for the project security posture.

Bounty Claim

Submitting for documentation bounty consideration.

Checklist

  • Comprehensive security policy
  • Clear reporting guidelines
  • Developer best practices
  • Audit status tracking

- Security vulnerability reporting process
- Security bounty program details
- Secure development guidelines for circuits and contracts
- Security audit status tracking
- Incident response procedures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant