Quote from: Jan on December 01, 2011, 05:03:39 PM

Quote from: westkybitcoins on December 01, 2011, 04:29:11 PM

Quote from: Jaagu on December 01, 2011, 11:39:06 AM

Quote from: Jan on November 28, 2011, 08:55:01 AM

Quote from: Findeton on November 27, 2011, 08:51:30 PM

The problem is you still have to wait to check if the transaction actually took place.

I am not sure what problem you are referring to. Please elaborate.

Maybe Findeton refers to a problem of sending couple transactions in quick succession? One needs to wait for each transaction to be picked up in a block then retrieve the TX outs again from server-side blockchain?

Yeah, that is a problem with only having one private key. I tripped up on this with StrongCoin too (although a workaround was implemented of allowing a spend to multiple addresses--this makes the problem much less severe.) Allowing multiple spends at once will help BitcoinSpinner too, but considering the simple design, it should probably be something the user has to ask for specifically. Also... while a little confusing at first, it might help to list the change itself as also being "coins on the way" ("change on the way?"), with the balance of the mini-wallet being 0.00 for a while after a spend.

StrongCoin and other alternative clients may have a limitation with change sent back to yourself. With BitcoinSpinner the change sent back to yourself is available for spending immediately, and you don't have to wait for a confirmation. In that regard BitcoinSpinner works like the Satoshi client.

You can do a simple test with BitcoinSpinner where you:
1. Have zero balance in BitcoinSpinner
2. Send 2 bitcoins to BitcoinSpinner in a single transaction
3. Send 0.9995 BTC to another client two times right after each other with no intermediate confirmations.
4. Wait for the funds to arrive in the other client.

I see. That's great then... another plus for BitcoinSpinner.

(I checked the last StrongCoin transaction I sent earlier today, and while it worked, it seemed a bit confusing as to exactly why it crafted the two (!) transactions for my single transaction in the way that it did...)