summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawmPTL3pk1gDt1-zQJY2Qv0K8VzPbTYUmPQ <Max_F@web>2014-02-20 11:32:49 +0000
committerGravatar admin <admin@branchable.com>2014-02-20 11:32:49 +0000
commit32f2fcea16456a9d75618e9a49cfb513d3f81dee (patch)
tree5135daa8dfc3ea6c78403ef5d14bdc5c51569aa8 /doc/todo
parentb552be80e26112ccd9fe654b8f1deb86d43299b3 (diff)
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn
new file mode 100644
index 000000000..76c8796a3
--- /dev/null
+++ b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn
@@ -0,0 +1,10 @@
+This is just an idea, and I have no idea if it would work (that's why I'm asking):
+
+**Would it be possible to use ASICs made for Bitcoin mining inside git-annex to offload the hashing of files?**
+
+I got the idea, because I have two RaspberryPis here:
+
+- one runs my git-annex archive. It is really slow at hashing, so I resorted to using the WORM backend
+- another one runs 2 old-ish ASIC miners. They are just barely "profitable" right now, so in a few months they will be obsolete
+
+Both devices to some kind of `SHA256`. I have a feeling this is either extremely easy or extremely complicated to do… :)