-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #30 from mountainprotocol/chore/security-policy
Create SECURITY.md
- Loading branch information
Showing
1 changed file
with
15 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,15 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
At Mountain Protocol, we highly value the security of our smart contracts and implement measures to guarantee that we're delivering secure code. The USDM token contract has undergone a in-depth secure development process, including a thorough [audit by OpenZeppelin](https://github.com/mountainprotocol/audits), a leading firm in Blockchain security. The following table reflects the version of the contract currently being supported with security updates. | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 1.0.0 | :white_check_mark: | | ||
|
||
## Reporting a Vulnerability | ||
|
||
If you have discovered a potential security issue or vulnerability in our smart contract, we greatly appreciate your help in disclosing it to us in a responsible manner. | ||
|
||
Please send us a detailed description of the issue to our dedicated email address: security@mountainprotocol.com. The report should include the steps to reproduce the vulnerability, potential impacts, and any relevant information that could help us understand the issue. |