-
-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat[docs]: add bug bounty program to security policy #4230
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nit comments; overall good to go IMO.
- If a compiler bug affects production code, it is in scope. | ||
- This includes bugs in older compiler versions still used in production (excluding known issues). | ||
- If a compiler bug does not currently affect production but is likely to in the future, it is in scope. | ||
- This mainly applies to the latest compiler release (e.g., a new release is available but contracts are not yet deployed with it). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there might be questions re what "new" exactly means (like 2 weeks, 6 months etc.). But we can address this if someone challenges it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I agree, but it was intentional. I think it's realistic that 0.3.10 might be used, but how far into the past should we go? I leave it up to the hunters to convince us / ask further questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 0.3.7
has been used widely but we shouldn't overthink it too much indeed.
Co-authored-by: sudo rm -rf --no-preserve-root / <[email protected]>
Co-authored-by: sudo rm -rf --no-preserve-root / <[email protected]>
--------- Co-authored-by: sudo rm -rf --no-preserve-root / <[email protected]>
What I did
How I did it
How to verify it
Commit message
Commit message for the final, squashed PR. (Optional, but reviewers will appreciate it! Please see our commit message style guide for what we would ideally like to see in a commit message.)
Description for the changelog
Cute Animal Picture