BSD, ZFS, OpenSSH, PAM: Distributed, Encrypted Open Source Data Sync, Share, & Storage with Bitcoin Message Signing
Project: http://electrum.org - Lightweight Bitcoin thin client, as advocated for by Satoshi Nakamoto [1]
Developed by Dr. Thomas Voegtlin, French PhD neuroscientist, Electrum
is an exceptionally simple Bitcoin wallet written in Python, that
protects you from losing your Bitcoins due to backup mistakes or computer
failure. Electrum automatically generates with each newly created wallet a
list of twelve common words from English poetry, which Thomas hand-picked
specifically to aid in memorization and long-term recall.
You must be willing to make extensive use of IRC for communication,
and you should probably at least possess a passing interest in Bitcoin,
if you want to take on this project.
I'm looking for a systems engineer who can think about problems
creatively. I've been agonizing over how to appropriately handle data
sync, share, and storage. I've considered everything from Tahoe-LAFS to
BitTorrent, from a simple Flask API to Git. I'm looking for the simplest
possible solution. If this sounds even slightly interesting please email
me at:
BSD, ZFS, OpenSSH, PAM: Distributed, Encrypted Open Source Data Sync, Share, & Storage with Bitcoin Message Signing
Project: http://electrum.org - Lightweight Bitcoin thin client, as advocated for by Satoshi Nakamoto [1]
Developed by Dr. Thomas Voegtlin, French PhD neuroscientist, Electrum is an exceptionally simple Bitcoin wallet written in Python, that protects you from losing your Bitcoins due to backup mistakes or computer failure. Electrum automatically generates with each newly created wallet a list of twelve common words from English poetry, which Thomas hand-picked specifically to aid in memorization and long-term recall.
You must be willing to make extensive use of IRC for communication, and you should probably at least possess a passing interest in Bitcoin, if you want to take on this project.
I'm looking for a systems engineer who can think about problems creatively. I've been agonizing over how to appropriately handle data sync, share, and storage. I've considered everything from Tahoe-LAFS to BitTorrent, from a simple Flask API to Git. I'm looking for the simplest possible solution. If this sounds even slightly interesting please email me at:
echo YW5keUBzaWVycmEzZC5jb20K | base64 -d
or ping me on #electrum (Freenode). I'm atweiden.
-Andy
[1]: http://www.mail-archive.com/cryptography@metzdowd.com/msg099...