aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authoranonimal <anonimal@i2pmail.org>2017-04-24 20:04:26 +0000
committeranonimal <anonimal@i2pmail.org>2017-04-24 20:11:10 +0000
commit66ecee0942e79618ed6a1407e5a6872415d35500 (patch)
tree7d828602107163b0133361fd47ecaf9284c0ed48 /README.md
parentDocs: add Vulnerability Response Process (diff)
downloadmonero-66ecee0942e79618ed6a1407e5a6872415d35500.tar.xz
Docs: add VRP link to README
Diffstat (limited to '')
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index acb997e13..1023b82c0 100644
--- a/README.md
+++ b/README.md
@@ -84,6 +84,10 @@ See [LICENSE](LICENSE).
If you want to help out, see [CONTRIBUTING](CONTRIBUTING.md) for a set of guidelines.
+## Vulnerability Response Process
+
+See [Vulnerability Response Process](VULNERABILITY_RESPONSE_PROCESS.md).
+
## Monero software updates and consensus protocol changes (hard fork schedule)
Monero uses a fixed-schedule hard fork mechanism to implement new features. This means that users of Monero (end users and service providers) need to run current versions and update their software on a regular schedule. Here is the current schedule, versions, and compatibility.