-
Notifications
You must be signed in to change notification settings - Fork 195
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2fbcd89
commit 1e56e2a
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Security Policy | ||
|
||
## Reporting a Vulnerability | ||
|
||
The Lido team appreciates your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions. | ||
|
||
To report a security issue, please use the [Lido Bug Bounty program on Immunefi](https://immunefi.com/bounty/lido). | ||
|
||
The Immunefi platform allows the Lido team to better track and respond to vulnerabilities, while also providing an opportunity for researchers to be rewarded for their findings. | ||
|
||
Please DO NOT file a public issue on GitHub or disclose the vulnerability publicly in any way before it has been addressed by the Lido core contributors. | ||
|
||
## Scope | ||
|
||
For details on what is considered in scope for the bug bounty program, please refer to the Lido Bug Bounty page on Immunefi. | ||
|
||
## Process | ||
|
||
1. Submit your report through the Immunefi platform. | ||
2. The Lido team will assess the report and may ask for additional information or clarification. | ||
3. Once validated, the team will work on a fix and coordinate the release process. | ||
4. After the fix has been deployed, the team will publish a security advisory and acknowledge your contribution (if you wish to be credited). | ||
|
||
Thank you for helping keep Lido and its users safe! |