Can someone help with this so we can solve this once and for all?

[CoinVisitor]

We had a transaction we tried to send and it was way above the normal size for us. Our set fee was way to low and now it is just floating in the chain popping in and out. We need to stop this so we can apply the proper fees and break down the size perhaps.

We had a huge jump in users and this was unexpected, it has been almost a week in limbo.

Here is transaction ee082cd20d6bd35380d1311f84ca4ff967d72821aa12ca3f354718c3a5208e66.

 Any help is much appreciated.

Kev

(coinvisitor)

[1715155578]

1715155578

[mintymark]

I started trying to advise the OP, but truth to tell I don't really know enough about this to reliably advise. One of the outputs in that unconfirmed transaction is spent, which seems unexpected?

I am hoping that someone will explain exactly what one should do in this situation and what the general approach is for a transaction like this.

[CoinVisitor]

I agree, if this happens in the future a overall standard procedure would be nice.

[DannyHamilton]

Probably the best thing you can do is contact some of the larger mining pools and offer a bounty for including this transaction in their next block.  That would allow the transaction to confirm and nobody would have any issues.

If you aren't going to go that route, then other options would depend a bit on which client you are using to create and send transactions.  If you are using Bitcoin-Qt, I *think* you can use pywallet to remove the transaction from your wallet (I'm not a pywallet expert, so I could be wrong here).  Then after the network stops relaying the transaction, you could create a new transaction sending the same amounts to the same addresses and including a proper fee.

This would probably result in that one spent output vanishing and causing issues for whoever owns/controls 19usibXR6YN4uaJWfmawC23RXD6VUHyf7w.

If you can't figure out how to remove the transaction with pywallet, I think you can:

• Export the private keys of:
    
  • 1p4otARafmxH8hBLUi259Aq6TtUwVXiom
  • 1JXgUxEXg5FkL97ArkACUNVxpBw33TBFtf
  • 1Fwn2csUnkKcmW9BhdWuhx97ynLRLyo8Ff
  • 12bRw6fX5tna6iyFwwAqDR4M4brTzRfazk
  • 1Sc1ea1hsTACfYNT2jCbDujB314wdqcun
  • 1EW5RTqiEuQ7Z67DKz4vrwHJ93WnHvNCwk
  • 1GaPVstTVA3bKpbwt6kpGQn5V2UrWHtwUj
  • 13GgzCDnQYf4yTQ8rL3oMB3ovtmJrAmF5b
  • 1NZkAnbGCcVH5V6TY2QapxhgL75U5EpjkB
  • and 1EgKtq1NbAFUFdZa9gZWr7JZAPVbcL7i18

• Shut down Bitcoin-Qt
• Wait for the network to stop relaying the transaction and forget about it
• Start up a new blank wallet
• Import the private keys that were exported in step one
• Create a RAW transaction using the exact same outputs/inputs as the problem transaction with the exception of a smaller change transaction to allow for a proper fee
• Wait for this new transaction to confirm
• Shut down Bitcoin-Qt
• Restart Bitcoin-Qt with the old wallet

This process would probably solve everyone else's problem, but I'm not sure how your current wallet will react when it comes back online and discovers that all the outputs in it's current unconfirmed transaction are no longer available.  It might cause you some issues moving forward from there.

[CoinVisitor]

Awesome response Danny thank you.

 He is doing something along that lines and will pass this along to him. I will get back to you on results and any other input would be appreciated. Thanks

[CoinVisitor]

This will take some time for sure if we continue this route, we have 700 keys complete out of well over 2000. We talking like 3 days long.

[DannyHamilton]

This will take some time for sure if we continue this route, we have 700 keys complete out of well over 2000. We talking like 3 days long.

700 keys?

If you are exporting private keys why would you need to export more than 10?

Also, are you doing them by hand?  It seems that you could easily write a script that dumps out the private keys rather quickly if you really want them all?

[CoinVisitor]

would you be available for a chat danny?  http://coinvisitor.com/chat/?login  if possible....... Thanks Kev....

[DannyHamilton]

Yep. No problem.