Skip to content

Conversation

@fxamacker
Copy link
Member

@fxamacker fxamacker commented Jan 22, 2026

This PR adds a "Flow Rewards" section to SECURITY.md with some text paraphrased from some of @j1010001 ideas today, which might reduce security-related noise while still encouraging valid security reports.

Thanks @j1010001! 👍

Caveats

  • If we make the text too strict, we may risk discouraging valid security reports.
  • If we make the text too relaxed, we may spend more time reviewing and disqualifying invalid security reports.

  • Targeted PR against main branch
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work
  • Code follows the standards mentioned here
  • Updated relevant documentation
  • Re-reviewed Files changed in the Github PR explorer
  • Added appropriate labels

This commit adds a "Flow Rewards" section to SECURITY.md with some text (paraphrased from Jan's ideas) that might reduce security-related noise while still encouraging valid security reports.
@fxamacker fxamacker requested a review from j1010001 January 22, 2026 01:59
@fxamacker fxamacker requested a review from turbolent as a code owner January 22, 2026 01:59
@fxamacker fxamacker added the documentation Improvements or additions to documentation label Jan 22, 2026
The first paragraph under "Flow Rewards" section is moved to the vulnerability disclosure program by Jan, so we don't have to keep that requirement in this document.

This commit replaces the specific requirement with the more general statement:

"Security reports that follow the guidelines and meet other conditions of the vulnerability disclosure program might qualify for Flow Protocol Rewards."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants