Stuck transactions - possibly new attack?

[DeathAndTaxes]

it isn't going to magically fix old problems. 

Well, actually—

Zapwallet will fix these cases, in a kind of blunt way.

There is also a patch forthcoming that will release stuck coins (after, by default, something like 144 blocks).

I just saw zapwallet.  Nice solution.  Kill all tx records and then rescan to pickup only the confirmed ones. Smart.

[djeZo]

Okay, but will bitcoin-qt at least remove past malled transactions, and doing this correctly to keep proper account balances? Then I just need to do resends of all legit transactions that failed, right?

[djeZo]

I just checked out something; I issued getaccounts and did sum on balance of all accounts. The result is that summarized balance is far less than what is bitcoin-qt showing me on first page. The difference is much more than sum of all unconfirmed transactions. Where is the catch?

[djeZo]

I am trying to figure out the best strategy on how to salvage this.

I am scared of loosing some BTCs in the process.

What I was thinking I should do is following:
- wait for all legit transactions to get confirmed
- stop website from communicating with bitcoin-qt
- identify all legit non-confirming outgoing transactions (remember account + destination addr + amount + txid)
- use 'listaccounts' command and save balances of all customers
- identify all malled transactions (remember txid for each)
- close bitcoin-qt
- remove malled transactions and all legit non-confirming outgoing transactions using pywallet - one by one
- open bitcoin-qt
- use 'listaccounts' - if deletion of transactions went all ok, then some accounts will have higher balance than before - if one account has less, then something went wrong (is this assumption correct?)
- resend all previously saved legit non-confirming transactions

Can someone experienced with bitcoin accounts tell me if this procedure is correct?

[djeZo]

I have followed the steps previously pointed out and after deletion of all transactions, overall BTC balance was less, but when checking balance of all accounts -> they all had MORE in. So I decided to go forward and I resent stuck transactions. It looks like everything is fine now.

But I am still wondering why pywallet with command to delete all transactions messed accounts. Perhaps when deleting all transactions, internal "move" transactions are also deleted?

[DannyHamilton]

it isn't going to magically fix old problems. 

Well, actually—

Zapwallet will fix these cases, in a kind of blunt way.

There is also a patch forthcoming that will release stuck coins (after, by default, something like 144 blocks).

But will it figure out how to adjust the "accounts" that the OP is using in the way that he wants them updated?