Pages:
Author

Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 91. (Read 274562 times)

hero member
Activity: 742
Merit: 500
I have two problems with bccapi

1. The server is not open source. I asked the developer about it, see here: https://bitcointalksearch.org/topic/m.571018
2. The server needs to know you. It needs to store an account with your addresses, because it keeps track of your transactions as it downloads the blockchain. In other words, its database works just like bitcoind, whereas the Electrum server behaves like a Blockexplorer database

These two facts create a situation where users are tied to a server that belongs to a single individual.
Even if Jan decided to open-source his code, the fact that users need to be known in advance from the server does not favor privacy or freedom of choice.
This is the reason why I decided to write Electrum (https://bitcointalksearch.org/topic/m.585227)

This is the reason why I am interested in using Electrum.
donator
Activity: 2772
Merit: 1019
There is bccapi, very similar to electrum, but in java.

Actually Im playing with BitcoinSpinner, rewriting network layer to be compatible with Electrum servers. Spinner is pretty nice and really easy to use, but did you know that BCCAPI server implementation isnt opensource? ;-)

Goddamnit, none of the android wallets work on my android 2.1 (can't upgrade as it seems). Why is that?

No, I didn't realize BCCAPI server is not opensource. Is the protocol documented?
legendary
Activity: 1896
Merit: 1353
1. An android client is needed. I tried to do it in python, I compiled python for Android, but it is difficult to use. It might be easier to rewrite Electrum in java.

There is bccapi, very similar to electrum, but in java.

https://bitcointalksearch.org/topic/announcing-bccapi-36892

I have two problems with bccapi

1. The server is not open source. I asked the developer about it, see here: https://bitcointalksearch.org/topic/m.571018
2. The server needs to know you. It needs to store an account with your addresses, because it keeps track of your transactions as it downloads the blockchain. In other words, its database works just like bitcoind, whereas the Electrum server behaves like a Blockexplorer database

These two facts create a situation where users are tied to a server that belongs to a single individual.
Even if Jan decided to open-source his code, the fact that users need to be known in advance from the server does not favor privacy or freedom of choice.
This is the reason why I decided to write Electrum (https://bitcointalksearch.org/topic/m.585227)
donator
Activity: 2772
Merit: 1019
slight bug found: missing cairo does not have the same nice explanation on how to install as some of the other dependencies
staff
Activity: 4270
Merit: 1209
I support freedom of choice
Spinner is pretty nice and really easy to use, but did you know that BCCAPI server implementation isnt opensource? ;-)
Wow! So you will release a Spinner client that works with them? Cheesy
I hope that they will release BCCAPI server source code after this.
legendary
Activity: 1386
Merit: 1097
There is bccapi, very similar to electrum, but in java.

Actually Im playing with BitcoinSpinner, rewriting network layer to be compatible with Electrum servers. Spinner is pretty nice and really easy to use, but did you know that BCCAPI server implementation isnt opensource? ;-)
staff
Activity: 4270
Merit: 1209
I support freedom of choice
oh, good to know! thank you Cheesy
legendary
Activity: 1386
Merit: 1097
I really like to see this feature:
http://coderrr.wordpress.com/2011/06/30/patching-the-bitcoin-client-to-make-it-more-anonymous
I think that this should be by default on every bitcoin client.

That's called "coin selection" and it is on my list.
donator
Activity: 2772
Merit: 1019
1. An android client is needed. I tried to do it in python, I compiled python for Android, but it is difficult to use. It might be easier to rewrite Electrum in java.

There is bccapi, very similar to electrum, but in java.

https://bitcointalksearch.org/topic/announcing-bccapi-36892
donator
Activity: 2772
Merit: 1019
If somebody can't read the codes, they can't have faith on this clients.

huh? then why do people have faith in satoshi client?
hero member
Activity: 714
Merit: 504
^SEM img of Si wafer edge, scanned 2012-3-12.
staff
Activity: 4270
Merit: 1209
I support freedom of choice
I really like to see this feature:
http://coderrr.wordpress.com/2011/06/30/patching-the-bitcoin-client-to-make-it-more-anonymous
I think that this should be by default on every bitcoin client.

And also an option/feature to add private keys Smiley
legendary
Activity: 1386
Merit: 1097
It is already possible, you can simply create a script or an alias like:

This is a good example why storing keys outside of app settings is a good idea...

Quote
Also, ThomasV suggested another (better) solution for Linuxes. You run the client with the wallet file set in /dev/shm (temporary storage in RAM):

Well, it is nice that it can be done, but as far as keys are stored only in the encrypted form, I don't see it as a real threat. Keeping unencrypted keys in the memory is much worse, but it probably don't have a solution (until there will be hardware tokens keeping private keys outside the machine completely).
sr. member
Activity: 252
Merit: 250
Electrum already has the deterministic wallets working right? Is it possible and reasonable to have a feature where the wallet is cleanly deleted after every use and regenerated next time it is needed?

It is already possible, you can simply create a script or an alias like:

Code:
alias electrum='/path/to/electrum.py ; rm -f ~/.electrum/electrum.dat'

The client would also be easy to patch to not commit the file to disk at all. You start it, it asks for the mnemonic phrase, generates the keys, and when you close the client the data is purged from memory.

Also, ThomasV suggested another (better) solution for Linuxes. You run the client with the wallet file set in /dev/shm (temporary storage in RAM):

Code:
electrum.py -w /dev/shm/electrum-wallet.dat

But can you tell me what the usage scenario is? I don't think it's that useful, do you think it would be a security feature? What are you trying to prevent happening?
legendary
Activity: 1246
Merit: 1016
Strength in numbers

Today I thought about features I'd like to see in best-bitcoin-client-ever, there is my brain dump. Maybe if others have some nice ideas it will be good to make a pool of them to let programmers pick what they want to implement.

* Firstbits support (in progress)
* Qt GUI (in early steps, not sure with results. I have many possible improvements of GUI in my head, however they're related to basic gui design, so nothing to reveal yet)
* Coin selection
* Notification for new client version (as protocol is in early stage it's important to tell users they have to upgrade)
* Send bitcoins to email (using server-side escrow, sending back not withdrawed coins)
* Wallet in the cloud (sync wallets across multiple computers)
* Server failover (server peer switching)
* Make network layer more robust (permanent connection, interface for browser clients, but fallback to poling for restrictive networks)
* Make wallet format more robust

Fristbits!

After that.. better wallet format seems good.

Coin selection sounds fun, though in practice I imagine it'll mostly involve people paying a little extra in fees and having false sense of added privacy since they'll screw it up.

Electrum already has the deterministic wallets working right? Is it possible and reasonable to have a feature where the wallet is cleanly deleted after every use and regenerated next time it is needed?
full member
Activity: 162
Merit: 100
I just tried it and it works great in my opinion.
I'm so glad that it's written python so noobs as me play around with the code hehe.
hero member
Activity: 714
Merit: 504
^SEM img of Si wafer edge, scanned 2012-3-12.
legendary
Activity: 1896
Merit: 1353
pygtk is hard to install on windows xp

allways say : " import _gtk error: load dll failure."



I know. slush is working on a Qt gui for Electrum.
hero member
Activity: 714
Merit: 500
pygtk is hard to install on windows xp

allways say : " import _gtk error: load dll failure."

legendary
Activity: 1896
Merit: 1353
I just released a new version, version 0.28

changelog:
* the wallet_dir option was replaced by a wallet filename option
* pycrypto is no longer used, it was replaced with slowaes (native python)

both slowaes and python-ecdsa are native python, and are included in the package, so the installation should be highly facilitated.

Note that the wallet format has changed. if you have encrypted your wallet, you will need to upgrade it with a script.
you can either uncrypt your wallet before the upgrade (the easiest option), or run the upgrade.py script that will upgrade your wallet to the new format.

Pages:
Jump to: