From 92a1b28dfbe24b01e018c5946a851286f15e284a Mon Sep 17 00:00:00 2001
From: ashbz <67267642+ashbz@users.noreply.github.com>
Date: Sat, 27 Mar 2021 22:07:48 +0200
Subject: [PATCH] README

---
 README.md | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 README.md

diff --git a/README.md b/README.md
new file mode 100644
index 0000000..dcd2381
--- /dev/null
+++ b/README.md
@@ -0,0 +1,33 @@
+
+# BruteBTC
+
+![](https://i.imgur.com/RKJkkWN.png)
+
+### Description
+
+BruteBTC is a BTC key collider developed with C#. It can check over 15000 keys a second with a modern CPU. 
+Should work on Windows, Mac OS and Linux, although it has been compiled and tested only on Windows.
+
+##### What does a BTC key collider do?
+A BTC key collider generates random private keys and checks if those private keys have the same public address as one of the known addresses with balance in them (if there is a collision).
+
+##### How likely is it that such a collission will happen?
+According to [Bitcoin Wiki](https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses "Bitcoin Wiki"):
+> Because the space of possible addresses is so astronomically large it is more likely that the Earth is destroyed in the next 5 seconds, than that a collision occur in the next millenium.
+
+So chances are pretty slim, but you just never know.
+
+## How to use
+1. Download a list of the known BTC addresses with balance in them from here:  http://addresses.loyce.club/soon.html
+2. Extract the .tsv file
+3. Drag and drop the .tsv file into BruteBTC.exe
+
+The program will then read the wallet addresses into memory, and then once that is done it will start generating private keys and checking.
+
+## Requirements
+- At least 8GB of free RAM (loading all wallets into memory will take 7GB)
+- A good CPU with multiple cores (program uses multi-threading for faster checking)
+- .NET Core 3.1
+
+## Uses
+- [NBitcoin](https://github.com/MetacoSA/NBitcoin "NBitcoin")