Bitcoin Transaction Stuck For 3 Days (Potential DoS Bug)

[HasherMe]

My transaction has been stuck without confirmation for > 3 days.  

Yesterday this was stuck and a double spend warning on top:
https://blockchain.info/tx/1efea73fc797ae98edcaf9f407742152bd473cef6fbd4376326b330da558e379

Today this is stuck:
https://blockchain.info/tx/91f04808fb89a18b08c523cea2037f1ec6372309e5fc21a873a5e6064bb75b0f

Somehow the transactions are changing.

I own the privatekeys for these 4 wallet addresses involved in the unconfirmed transaction:

1PLoWicvwt4ZQyPXjob1qF5PNwnchfkhR8
1HEEehUwzadonZ62a1bBVknofeqEjG58Kp
1AmirA93DaDaKMsTjWaNdSyiEyU3SVN59C
1Amir1fqsTfbf4XF3CsnnJkPCHrtnhMrTx

I used electrum to send the first three transactions and bitcoin-qt for the last (v0.10) on linux.  I tried pywallet to remove the transactions.   I turned my qt and electrum off for now. Anyone know what is going on?  Is there anything I can do to confirm or rollback this tranaction?

Since every wallet address I send to gets stuck at unconfirmed, couldn't someone use this as a DOS by sending a small amount of coins to many addresses from one of these corrupt accounts?

[1715161242]

1715161242

[Lauda]

The problem with the recent transaction is that you're trying to make a TX with a input that has not been confirmed. This means that the problem lies in TX1 and TX2. This problem was caused solely by you and not the network. You've included a fee (Fees :0.0001 BTC) less than the recommended one. The rate is 0.0005 BTC per 1K of data consumed by the transaction.

I think that you should backtrack from the last transaction and start manually deleting. Start by deleting this one and then TX2 and then TX1 as mentioned above.

[HasherMe]

The problem with the recent transaction is that you're trying to make a TX with a input that has not been confirmed. This means that the problem lies in TX1 and TX2. This problem was caused solely by you and not the network. You've included a fee (Fees :0.0001 BTC) less than the recommended one. The rate is 0.0005 BTC per 1K of data consumed by the transaction.

I think that you should backtrack from the last transaction and start manually deleting. Start by deleting this one and then TX2 and then TX1 as mentioned above.

I will use PyWallet to delete the first two TXs.  Thanks for the advice. 

[thew3apon]

The network is getting damaged you should do a higher fee and it will go through

[HasherMe]

Doesn't this give me the ability to spam many other wallet addresses and cause a DoS?  All I need to do is send 1 satoshi with a very small transaction fee to many addresses and they will be stuck as well.  

Why doesn't the network reject low fee transactions instead of acting so unpredictable?  I thought this is a protocol with hard rules.    

My address with 0.9 BTC has been stuck since last Wednesday (7/8/2015).  I really screwed up by sending with a low fee but this might be a potential vulnerability in the Bitcoin protocol.  I can infect other addresses with these toxic wallet addresses.  Once I send to another address, that address becomes stuck and propogates the issue.  

I was able to remove the 3 transactions from my Bitcoin Qt wallet.  I will let it sit for days or until I don't see the transactions anymore on blockchain.info.