-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: Christoph Otter <[email protected]>
- Loading branch information
1 parent
ff1da32
commit 38c7bd1
Showing
1 changed file
with
1 addition
and
1 deletion.
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 |
---|---|---|
|
@@ -22,7 +22,7 @@ There are three ways to report a security issue | |
| | Cosmos HackerOne Bug Bounty program | security<span>@</span>interchain.io | security<span>@</span>confio.gmbh | | ||
| ------------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| Maintained by | Amulet | Amulet | Confio | | ||
| Eligable for bounty | yes | no | no | | ||
| Eligible for bounty | yes | no | no | | ||
| Reporting link | <https://hackerone.com/cosmos> | [[email protected]](mailto:[email protected]) | [[email protected]](mailto:[email protected]) | | ||
| Reporter management | professional communation | professional communation | best effort | | ||
| Details | See program details at <https://hackerone.com/cosmos> | If you prefer to report an issue via email, you may send a bug report to [email protected] with the issue details, reproduction, impact, and other information. Please submit only one unique email thread per vulnerability. Any issues reported via email are ineligible for bounty rewards. | You will receive a response from us within 4 working days confirming that a human read your email. If you do not hear back within 1 week, feel free to send a reminder or try to notify core team members via different channels. | | ||
|