aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorRiccardo Spagni <ric@spagni.net>2017-05-05 11:23:44 +0200
committerRiccardo Spagni <ric@spagni.net>2017-05-05 11:23:44 +0200
commitbef164f5ce4ede2af659dfa8a2b475ce29f9e945 (patch)
tree42750b5ec178fa892ee84f3f775e003cac61fc47 /README.md
parentMerge pull request #1986 (diff)
parentDocs: add VRP link to README (diff)
downloadmonero-bef164f5ce4ede2af659dfa8a2b475ce29f9e945.tar.xz
Merge pull request #1995
66ecee09 Docs: add VRP link to README (anonimal) 1a66db8f Docs: add Vulnerability Response Process (anonimal)
Diffstat (limited to 'README.md')
-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.