Permalink
Browse files

Merge pull request #1 from TRTLAlien/patch-1

Update README.md
  • Loading branch information...
RocksteadyTC committed Jun 10, 2018
2 parents 7f03de3 + e016104 commit 89e7130e12685a86f143f4d973e08e7957f16bdf
Showing with 1 addition and 1 deletion.
  1. +1 −1 README.md
@@ -36,7 +36,7 @@ If you've submitted an issue, and you don't quite know how to fix it on your own
_TIP: Some people will notice that when they spend time helping in these channels that a robot may drop by and fill their pockets with some shells. We want you to spend time helping people and doing nerd stuff to help the project, so it only makes sense that it rains the most in these rooms :)_

## Explanation of risk
There is always a risk that the person running the project you're using has embedded super secret nuclear missile plans that they hacked out of a Russian datacenter, but odds of this are slim, and it's never happened. We'd be stupid to say there isn't a risk that someone contributing to a community project, through no fault of their own, creates a bug that corrupts your wallet file (backup your keys!) or otherwise causes things to mess up on your system. However unlikely this is to happen, we want to error on the side of responsibility and advise you of the potential for mistakes like this, and we ask that you please back up your spend key, view key, and mnemonic seed somewhere very safe just in case we mess up the nuclear-blueprint-hiding-algorithm and blow up your router in the process. Our keyloggers are top notch.
There is always a risk that the person running the project you're using has embedded super secret nuclear missile plans that they hacked out of a Russian data center, but odds of this are slim, and it's never happened. We'd be stupid to say there isn't a risk that someone contributing to a community project, through no fault of their own, creates a bug that corrupts your wallet file (backup your keys!) or otherwise causes things to mess up on your system. However unlikely this is to happen, we want to error on the side of responsibility and advise you of the potential for mistakes like this, and we ask that you please back up your spend key, view key, and mnemonic seed somewhere very safe just in case we mess up the nuclear-blueprint-hiding-algorithm and blow up your router in the process. Our keyloggers are top-notch.


_Thanks for reading this, if you got down this far, please say something in the chat to be showered with emojis._

0 comments on commit 89e7130

Please sign in to comment.