It's always great to have competition, as it makes products more perfect. From my side, I would happily agree to split the bounty between the developers of the most stable and easily usable wallets. There should be a voting at the 1st of July (?) of the best GUI, picked by the users.

The prizes could be the following ('x' is a variable which stands for the amount of the bounty, equally split into 8 parts):
1st place: 5 * x
2nd place: 2 * x
3rd place: 1 * x

Please give feedback about my idea!


EDIT: I have done a little bit of research of those T and F parameters when querying the transaction history. According to ByteCoin's simplewallet.cpp file, from lines 613-629, diving into the meaning of 'td.m_spent' took me to wallet2.cpp and wallet2.h. It's interesting to take a look at the struct 'transfer_details' in the header file, as there seem to be some nice parameters there which are useful. Anyway, I think that the 'm_spent' parameter indicates whether the money of a TX have already been spent on something, and 'm_tx' may contain some information we need.

Also, we shouldn't forget that values with a type of 'double' could be negative too. I've just started investigating further, and will update everyone about the case here.

EDIT #2: It looks like I was right, 'send' transactions should not be deducted from the account's balance. Proof:


EDIT #3: I have solved the problem in my client, it temporarily shows the types as "unknown" for safety. Don't worry though, the RPC integration will probably solve everything.