Disclaimer: I'm not very familiar with the bitcoin code or even C++ itself, so please correct me if I'm wrong and tell me what I missed

https://github.com/mhanne/bitcoin/tree/removeprivkey

This adds a new RPC call "removeprivkey" which takes an address and removes the corresponding keys.
It's intended to be used after a key has been dumped (showwallet branch).

Currently, it removes the name and the key from the wallet and the private and public key from memory.

What it does NOT do is updating the coressponding account/transactions, so if you have spent transactions and you remove keys, you might get negative balances.
I'm not sure what to do about that, I tried to find and remove transactions, but couldn't figure out how. Rescan doesn't help either.
However, I think for some usecases (like my online-wallet) this won't even be a problem because a user never sees any balances until the keys are loaded.

Also, since this is obviously very dangerous, maybe there should be some safeguards like checking if the key has been dumped before, or at least a compile-time option.
Maybe even require the dumped key to be passed as input, for proof that the user has it?

Please look at the code and tell me what you think and if it might be worth a pull request.

 Marius

During the last days I started hacking together a little online-wallet and thought some of you might be interested.

It is based on the bitcoind RPC API for handling accounts and adds custom labels stored in database.

If you want to send coins to a labeled address, just start typing the label and it will autocomplete.

It is a Ruby/Rails application released under the MIT license, so you can setup your own online wallet or even run it locally and use it instead of the default client UI.

Note that this is just a very early development version which still needs a lot of work.

Project/Source: http://open.sourceagency.org/projects/webtc
Demo (testnet): http://webtc.interesthings.de
(There is a demo Account: foo@bar.baz / password, but feel free to create new accounts, the email doesn't have to exist)

Feedback, bug reports, patches and donations welcome