It does seem that the standard client has way too many dependencies in general. Unfortunately, building a GUI that is really cross platform seems not to be an easily solved problem. I find all of boost, qt, gtk, etc. to be quite daunting and error prone to configure and build (I mostly run on Mac's and Ubuntu).
Are people interested developing a more minimal server client (ideally, for me, all in Python)? What projects already exist with goals like that?
For the client UI, it seems to me that an embedded web server whose client is built in HTML/JavaScript would be preferable to all the complex GUI Frameworks that are being used today.
Topic: Idea: Zero-Storage Wallet (Read 966 times)
Quote
In my spare time (not as much as I would like) I have been experimenting w/ a deterministic wallet variant which generates private keys "on demand" storing only the public key in the wallet. The goal would be to never write any private key to disk. However the way bitcoind is currently written makes that a challenge and will require extensive rewrite of the db and log code.
Exactly. The current code is a complete mess no wonder the wallet encryption bug. A Berkeley database, seriously ?
It seems that Electrum client will not run on Mac OS/X (PyGtk does not seem to be supported on Mac). Anyone know how I can get a Mac version running?
Mike Koss
CoinLab.com
Mike Koss
CoinLab.com
Thanks for the links! I especially like electrum - I'll dig into the code there and try it out.
Mike Koss
CoinLab.com
Mike Koss
CoinLab.com
I feel nervous about preserving private keys in any of the wallet solutions I've seen. In all cases, even if the keys in the wallet are encrypted, there is a non-zero chance the wallet.dat file (or equivalent) will be lost, making the deposits in the wallet irrevocably lost.
So, why not generate all the public/private keys in a wallet based on a user-provided seed? It's certainly possible to deterministically regenerate an arbitrary number of public/private key pairs, given only a random seed as a starting point (e.g., a string like "service-name/user-name/passphrase").
If the wallet need never be stored because it can always be regenerated, then you just have to ensure that you don't loose the seed value (i.e., your password).
I'd love to hear if someone has already implemented something like this. I'd be willing to work on including it as an option in the BitCoin client as well.
Thanks,
Mike Koss
Coinlab.com
Seattle, WA
So, why not generate all the public/private keys in a wallet based on a user-provided seed? It's certainly possible to deterministically regenerate an arbitrary number of public/private key pairs, given only a random seed as a starting point (e.g., a string like "service-name/user-name/passphrase").
If the wallet need never be stored because it can always be regenerated, then you just have to ensure that you don't loose the seed value (i.e., your password).
I'd love to hear if someone has already implemented something like this. I'd be willing to work on including it as an option in the BitCoin client as well.
Thanks,
Mike Koss
Coinlab.com
Seattle, WA
see http://ecdsa.org/electrum/
and this thread: https://bitcointalk.org/index.php?topic=50936.40
As long as you have a strong (and long) enough passphrase, I like the idea of a deterministic wallet where the private keys are only ever generated in memory when you want to send money.
The term is "deterministic wallet".
http://bitcoin.stackexchange.com/questions/718/what-is-a-deterministic-wallet
There are some that exist. Most use a pass-phrase to generate a seed to recreate a "traditional wallet".
In my spare time (not as much as I would like) I have been experimenting w/ a deterministic wallet variant which generates private keys "on demand" storing only the public key in the wallet. The goal would be to never write any private key to disk. However the way bitcoind is currently written makes that a challenge and will require extensive rewrite of the db and log code.
http://bitcoin.stackexchange.com/questions/718/what-is-a-deterministic-wallet
There are some that exist. Most use a pass-phrase to generate a seed to recreate a "traditional wallet".
In my spare time (not as much as I would like) I have been experimenting w/ a deterministic wallet variant which generates private keys "on demand" storing only the public key in the wallet. The goal would be to never write any private key to disk. However the way bitcoind is currently written makes that a challenge and will require extensive rewrite of the db and log code.
That sounds close - it eliminates to possibility of losing a wallet.dat file. But it would also be nice if private keys are NEVER written to disk, and so are much less vulnerable to theft.
There exists a forked client that does exactly this, allowing the user to probably recreate a damaged or lost wallet.dat file based upon a secret passphrase used as the seed for new addresses, but I can't remember the name of it nor could I vouch for it's trustworthyness otherwise.
I feel nervous about preserving private keys in any of the wallet solutions I've seen. In all cases, even if the keys in the wallet are encrypted, there is a non-zero chance the wallet.dat file (or equivalent) will be lost, making the deposits in the wallet irrevocably lost.
So, why not generate all the public/private keys in a wallet based on a user-provided seed? It's certainly possible to deterministically regenerate an arbitrary number of public/private key pairs, given only a random seed as a starting point (e.g., a string like "service-name/user-name/passphrase").
If the wallet need never be stored because it can always be regenerated, then you just have to ensure that you don't loose the seed value (i.e., your password).
I'd love to hear if someone has already implemented something like this. I'd be willing to work on including it as an option in the BitCoin client as well.
Thanks,
Mike Koss
Coinlab.com
Seattle, WA
So, why not generate all the public/private keys in a wallet based on a user-provided seed? It's certainly possible to deterministically regenerate an arbitrary number of public/private key pairs, given only a random seed as a starting point (e.g., a string like "service-name/user-name/passphrase").
If the wallet need never be stored because it can always be regenerated, then you just have to ensure that you don't loose the seed value (i.e., your password).
I'd love to hear if someone has already implemented something like this. I'd be willing to work on including it as an option in the BitCoin client as well.
Thanks,
Mike Koss
Coinlab.com
Seattle, WA
Jump to: