Nice chart!
I will link to it from http://lovebitcoins.org/getStarted.html
my table is really meant to get people started quickly with mobile wallets. But the desktop wallets are important too.
Topic: Desktop clients - Quick comparison chart - page 3. (Read 7985 times)
your table has to make some sort of distinction btwn "server based" and "locally held clients".
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
I've put in a mention that Electrum relies on remote servers (which are open source as well).
About the risk of a malicious server: the Stratum protocol doesn't allow for any executable code or scripts, so
"uploading the keys" is impossible IMHO. The worst thing a malicious server could do, in theory, is lie about your balance.
However, note that I'm not an expert in the Electrum technicalities, better ask ThomasV for an authoritative answer.
Also Electrum DOES support offline transactions already, but only through the command-line at this time. Armory's GUI-based support for them is clearly more intuitive IMHO.
you are right.
There is no way a malicious Electrum server could steal your keys or passwords. The only malicious thing it can do is lie about your balance/history. There are 5 active servers at the moment, and they are identified by their domain name. As a user, you decide from which server you get that information, and you can also compare the answers of several servers if you have a doubt.
Electrum does have offline signing and watching-only wallets. However, these functions require to use the command line.
The command line options of Electrum are fairly comprehensive; they allow you to handle several wallets, and they give you full control on the transaction (choosing the change address, sending from an address)
your table has to make some sort of distinction btwn "server based" and "locally held clients".
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
I've put in a mention that Electrum relies on remote servers (which are open source as well).
About the risk of a malicious server: the Stratum protocol doesn't allow for any executable code or scripts, so
"uploading the keys" is impossible IMHO. The worst thing a malicious server could do, in theory, is lie about your balance.
However, note that I'm not an expert in the Electrum technicalities, better ask ThomasV for an authoritative answer.
Also Electrum DOES support offline transactions already, but only through the command-line at this time. Armory's GUI-based support for them is clearly more intuitive IMHO.
Isn't the satoshi client portable? I mean, if you put the client and the blockchain on the usb drive it should work without problems. You have to put in the parameters to tell it to use the blockchain on the usb drive but except that it should work...
Hi, thanks, I will test this when I get a chance. I'm mostly worried about whether the performance is bearable, and initial setup duration (downloading the blockchain to a USB drive...)
Isn't the satoshi client portable? I mean, if you put the client and the blockchain on the usb drive it should work without problems. You have to put in the parameters to tell it to use the blockchain on the usb drive but except that it should work...
your table has to make some sort of distinction btwn "server based" and "locally held clients".
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
i don't know Electrum as well as i should but i believe that the generation and encryption of deterministic wallets and the holding of private keys is on the client side. that is good. my only concern, which might be an invalid one, is that once private local keys are decrypted a malicious server could somehow upload the keys. someone correct me if i'm wrong.
i admittedly use and like Armory b/c of the offline tx signing which in my opinion is superior. again, correct me if i'm wrong.
Wallet encryption was added in 0.4.0 (though it was flawed, initially; it sometimes left traces of the unencrypted keys on disk for a while).
If you have an encrypted wallet, the encrypted keys are loaded into memory, and only decrypted when necessary (after asking for a passphrase). When using the RPC interface, you can ask to keep the passphrase cached for a while, but even then, the actual keys are not decrypted until needed.
If you have an encrypted wallet, the encrypted keys are loaded into memory, and only decrypted when necessary (after asking for a passphrase). When using the RPC interface, you can ask to keep the passphrase cached for a while, but even then, the actual keys are not decrypted until needed.
Thanks for the info, I have updated the chart.
Hi flatfly,
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
Thanks Jim, I've updated the chart accordingly.
Hi flatfly,
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
yeah, that is cool.
Hi flatfly,
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
That is a very handy chart for people to use when looking at the different bitcoin clients.
By 'Portable' do you mean 'Can it run from a USB drive?'
If so, you can run MultiBit off a USB drive for all of Mac/ Linux/ Windows as described here:
http://multibit.org/help_runFromUSBDrive.html
Cheers,
Jim
OS compatibility and minimum supported OS version
Wallet encryption was added in 0.4.0 (though it was flawed, initially; it sometimes left traces of the unencrypted keys on disk for a while).
If you have an encrypted wallet, the encrypted keys are loaded into memory, and only decrypted when necessary (after asking for a passphrase). When using the RPC interface, you can ask to keep the passphrase cached for a while, but even then, the actual keys are not decrypted until needed.
If you have an encrypted wallet, the encrypted keys are loaded into memory, and only decrypted when necessary (after asking for a passphrase). When using the RPC interface, you can ask to keep the passphrase cached for a while, but even then, the actual keys are not decrypted until needed.
The Satoshi client also has the wallet encrypted while running.
Sorry, I must have missed this change. Has this been fixed recently?
The Satoshi client also has the wallet encrypted while running. Import/export of private keys is possible, but not via the user interface.
Thanks for the feedback. I will first fix the incorrect information (in a few minutes), then I will start adding stuff.
1. it would be nice to allow ppl to vote which client they use.
2. define "portable"
3. Armory IS encrypted while running.
4. Armory IS deterministic.
5. Armory CAN import/export private keys.
6. need category for paper one time backups.
7. need category for "offline tx's"
8. need category for "watching only wallets".
2. define "portable"
3. Armory IS encrypted while running.
4. Armory IS deterministic.
5. Armory CAN import/export private keys.
6. need category for paper one time backups.
7. need category for "offline tx's"
8. need category for "watching only wallets".
I think an additional row needs to be for Clients that require another program to run to function, i.e. how Armory for example requires the actual bitcoin-qt to be open and loaded to access the blockchain.
Yup, if there is a dependency, then that would be useful on the chart.
For instance, Electrum's dependency is on the Electrum servers so connectivity becomes the dependency.
Nice chart, by the way.
I think an additional row needs to be for Clients that require another program to run to function, i.e. how Armory for example requires the actual bitcoin-qt to be open and loaded to access the blockchain.
I've made this chart for my own usage, but thought it might help new users navigate through the existing options for Bitcoin clients. Note that I purposefully chose to focus on desktop-based (non web-based), open-source clients only.
If others find the chart helpful, I can update it regularly, as new versions get released. Also feel free to suggest any other criteria that would be interesting to compare in a table format. And thanks for letting me know of any mistakes.
Disclaimer: Although I have tried all the clients listed, I'm almost exclusively an Electrum user - and I make stand-alone Windows builds for it.
If others find the chart helpful, I can update it regularly, as new versions get released. Also feel free to suggest any other criteria that would be interesting to compare in a table format. And thanks for letting me know of any mistakes.
Disclaimer: Although I have tried all the clients listed, I'm almost exclusively an Electrum user - and I make stand-alone Windows builds for it.
Jump to: