...

[Akka]

You could directly ask some large pool operator to please include it. Maybe for a small donation to the pool.

[caveden]

As I said to OP, you may attempt to send the "locked money" to yourself, and pay a large transaction fee in the process. Theoretically the whole unconfirmed chain should be analyzed together by miners. (the fee would be used to pay for all of them).

afaik no miner software has that implemented.

I thought this behavior had already been implemented in bitcoind. I might be wrong though, can't find it on github.

[DeathAndTaxes]

afaik no miner software has that implemented.

It isn't part of memory pool selection rules in bitcoind.  Most (all?) major pools use custom software but AFAIK unless it has changed recently no pool does "forward looking of fees".  

The OP has two solutions:
The first solution is to delete the offending transactions locally (requires some wallet.dat surgery).  Other nodes including miners will "forget" about the unconfirmed transactions in time (I believe 24 hours?).  This would allow creating a replacement transaction with an appropriate fee to ensure timely inclusion.

The second solution is to contact a pool operator directly, provide them the transaction hash(es) and for a manually paid bounty (fee) they may be willing to manually add the offending transactions to the pool's next block.  IIRC Luke has done this in the past.

If both of those solutins sound like they suck, well that is the point.  The mandatory fee rules exist to protect the network from a denial of service attack.  If one could create 600 outputs using 22KB for a mere 0.0005 BTC (about 1.2 cents) then one could also create transactions totaling ~30,000 transactions and 1 MB for about $0.50.  For less than minimum wage an attacker could denial of service attack the largest computing network in the world and add roughly about 4GB of spam to the blockchain per month.

Simple version:  DON'T BYPASS MANDATORY ANTI-SPAM RULES.  They exist to protect the network.  When you bypass them the network teats the transaction like a threat and the "immune system" which consists of dropping and delaying high-cost low-value transactions kicks in.

[DannyHamilton]

I'm getting "transaction not found" when I look for  http://blockchain.info/tx/88eb395b48a6d3875d8d55a6efd34afd2e1d4e397b43f9f790479914fba0c74b

Was there a double-spend on this initial transaction?  Wow, that would be quite a mess for a lot of people.

[deepceleron]

afaik no miner software has that implemented.

The OP has two solutions:
The first solution is to delete the offending transactions locally (requires some wallet.dat surgery).  Other nodes including miners will "forget" about the unconfirmed transactions in time (I believe 24 hours?).  This would allow creating a replacement transaction with an appropriate fee to ensure timely inclusion.

There is no time restriction on re-spending transaction inputs; the same transaction can immediately be double-spent - resent with less change and more fees. The unconfirmed transaction will be discarded from memory pools when a replacement transaction using the same inputs is included in a block.

The only caveat is that if you delete the transaction from the Bitcoin client and send a different total amount, Bitcoin may compose the replacement transaction from different inputs, since it uses an algorithm that chooses inputs based on minimizing change. A "resend transaction with more fees" feature could be implemented in Bitcoin that ensures a duplicate spend of the same inputs (plus more inputs if needed to add the increased fee). However there is little need, because the reference Bitcoin always includes at least the minimum fees.

blockchain.info will temporarily brand your address with a double-spend warning for others when it detects them on the network.

[DeathAndTaxes]

There is no time restriction on re-spending transaction inputs; the same transaction can immediately be double-spent - resent with less change and more fees. The unconfirmed transaction will be discarded from memory pools when a replacement transaction using the same inputs is included in a block.

I think you misunderstood any node following the reference client rules will drop and refuse to relay a double spend.  So if you have tx A and you wish to replace it with tx B, when your node broadcasts tx B to the 8 (or 50) immediate peers the most likely outcome is they all detect tx B is a double spend of tx A (because tx A is in their memory pool) and promptly drop it.  You can keep broadcasting tx B thousands or even millions of times and they will happily drop it each time. 

Now eventually nodes do "forget" about unconfirmed tx so after that you can broadcast tx B, and your peers not having a record of tx A relay the tx on to other nodes, who will relay it to other nodes, and eventually every node and miner will know about tx B.   There is one "gotcha" though. As long as your node knows about tx A (it is still in the wallet) your node will keep reminding other nodes about tx A (who will remind other nodes) this will ensure that nobody ever forgets about tx A preventing a spend of tx B.

So simple version:
a) Bypass the peer network and get the replacement tx in a block.
OP can contact a mining pool and ask him for help (likely for a fee)

or

b) Allow the network to "forget" about the original tx and try again.
OP (or someone who in the future is in the same scenario and doesn't want to need to contact a miner) can remove the tx from the wallet file, wait long enough that the network forgets about it and create a replacement tx.

[deepceleron]

There is no time restriction on re-spending transaction inputs; the same transaction can immediately be double-spent - resent with less change and more fees. The unconfirmed transaction will be discarded from memory pools when a replacement transaction using the same inputs is included in a block.

I think you misunderstood any node following the reference client rules will drop and refuse to relay a double spend.

I don't think this is true. I was able to double spend MtGox by sending a payment with the same coins (with fee) as was transmitted by MtGox auto-sweep an hour before (without fees). https://bitcointalk.org/index.php?topic=139180.msg1483106#msg1483106. It was included in the next block.

[caveden]

The first solution is to delete the offending transactions locally (requires some wallet.dat surgery).  Other nodes including miners will "forget" about the unconfirmed transactions in time (I believe 24 hours?).  

Don't the receivers of an unconfirmed transaction also try to keep it alive by rebroadcasting?

Considering these transactions have ~600 outputs, it's likely that some of its receivers did get it.

[Akka]

Don't worry, there is already a 5 BTC reward up to include this transactions in a Block:

https://bitcointalk.org/index.php?topic=143915.0

So they will probably get confirmed soon.

[piuk]

And I did the same thing today, I'm getting sick of blockchain.info support, they take forever to reply.

It's not my fault if I've set the goddamn fee to generous but it still goes out with 0.0005 BTC fee.

I'm temporarily suspending payments, this is causing too much mess.

Why not limit the number of outputs in each transaction?

[DannyHamilton]

- SNIP -
http://blockchain.info/tx/ccb75ea48acc40f249f445ab7b6913e6a805938c022fbc6c9dcbdc67e4cb8847
http://blockchain.info/tx/88eb395b48a6d3875d8d55a6efd34afd2e1d4e397b43f9f790479914fba0c74b
 - SNIP -

Good news! Both of those transactions have finally confirmed.

Bad news...

The following transaction is a double-spend and will therefore NEVER confirm.

http://blockchain.info/tx/97825f2228c0087acf2b7edce81c79838931845c4b0595ed4088966ebdf9d633

[DannyHamilton]

Actually, how was that transaction marked as a double spend? I've done some math and the transaction was not sent with any of those first two transactions change. How's that possible?

You are looking in the wrong place.

The 0.81177179 BTC change from this transaction:
http://blockchain.info/tx/f3b95391c4ed5af0fa7f737aac52a6d9892feb34543a077f30b81696cc1d4021

Was used as the input for BOTH of these 2 transactions:
http://blockchain.info/tx/97825f2228c0087acf2b7edce81c79838931845c4b0595ed4088966ebdf9d633
http://blockchain.info/tx/ccb75ea48acc40f249f445ab7b6913e6a805938c022fbc6c9dcbdc67e4cb8847

Since the spend of that change in ccb75ea48acc40f249f445ab7b6913e6a805938c022fbc6c9dcbdc67e4cb8847 has been confirmed, it no longer exists to be used by 97825f2228c0087acf2b7edce81c79838931845c4b0595ed4088966ebdf9d633.

[piuk]

There would still be a risk of it not get confirmed since the fee is not what it should be (> 0.0005).

Can't you make it send the correct fee? (like it should)

You can now use the settxfee JSON RPC command to set the default transaction fee for 24 hours http://blockchain.info/api/json_rpc_api

or set fee policy to generous in the javascript interface to increase the base fee to 0.001 BTC