Topic: Transaction catastrophe (Read 861 times)

Holy F@#king sh!t, I got my transaction to finally go threw. Someone might have suggested this and I did not understand, but this is what I followed "https://data-dive.com/unconfirmed-bitcoin-transactions-electrum".
This is what happend "https://blockchain.info/tx/c8effd35b1f05b0ff74bb1946df9adfcba685495e9bb5f243f72c0755e38f182".

Thanks to all that took some time out of their day to try and help me.

I don't see a competing (double-spend) transaction.  Perhaps most of the network has already forgotten it?  Perhaps most of the netowrk never saw it?  It's difficult to know what happened without more information.


If you used those multiples of wallets on different computers to send transactions?  Yes.


If there is a competing (double-spend) transaction, then only one of the competing transactions will confirm.  The other will become invalid. However, as long as both transactions are unconfirmed, then it is up to ViaBTC to choose when they want to forget about the other transaction they saw.  You'd have to ask them how they handle that.

http://imgur.com/a/hCf8j

The questions below are in reference to the picture at the above link:

Could someone point out to me where it was "double spent"?
Could I have caused a "double spend" by opening multiples of the same wallet.dat (different backups on different computers, looking for lost key) in a short time?
If I just keep my wallet open will the "double spend" flag get dropped once one of the transactions gets dropped (if there are multiples)?

Things are not looking good, I got this reply from ViaBTC:
http://imgur.com/a/hCf8j
Can some one tell me which was my problem?
Not sure if it was dropped from the mem pool: [urlhttps://blockchain.info/search?search=c8effd35b1f05b0ff74bb1946df9adfcba685495e9bb5f243f72c0755e38f182][/url]
Not sure about the double spent how or if I "doublespent".

So it looks like my coin is stuck here: https://blockchain.info/address/1EJFi2ivgcjTpXqg6Kz2st91h4qyf7weLF

Any suggestions or should I take it as a loss and lesson learned?

Viabtc now provides a paid accelerator service in addition to its free service. It costs 0.01BTC to use its paid service, and you have to email [email protected] to use it.

Pestalent1 could pay viabtc 0.01BTC to confirm his transaction.

Unfortunately viabtc haven't done much to advertise its paid service yet.

https://www.viabtc.com/tools/txaccelerator/

Its put the link below at the bottom of the free accelerator webpage.


After you click it the text below is revealed.

I'm at home at the moment, so i don't have access to the mails i exchanged with the OP, but i did indeed tried to help him.

If i remember correctly (i get several mails from different people each day), the main problem here was that the sending wallet no longer helt the private key to spend the original unspent output that was used as an input for the stuck transaction. Because of this, it was impossible to double spend the input of the stuck transaction. Also, the 1 sat/byte fee made sure the OP couldn't use viabtc.
This also means there's quite a bit of pressure for the OP, since if this transaction doesn't get into a block, he has to re-broadcast it indefenately, since it would be the only way for him to recuperate his BTC.

Don't really remember why we couldn't get a CPFP tx to work. OP, maybe you can post the unsigned CPFP tx we created, that way more people can have a look at it...

The only thing i can imagine is that it has something to do with this time machine (don't have a mac, so i don't really know how this works)... I certainly hope a more knowledgeable member than myself can help the OP out...

BTW: i do remember the wallet.dat was generated pre-0.13, so it's not a HD wallet, so if you restore to an to old version of wallet.dat, you'll lose private keys.

Good luck OP!!!

Bitcoin Client Software and Version Number: 14.0
Operating System: Sending OSX 10.11.6/ Receiving Win7 Pro (up to date on updates)
System Hardware Specs: Two different machines, if needed I will supply
Description of Problem: See below:
Any Related Addresses: (sending) 1NdagsP6LGW4mLhujZ8HoLs8QjybncBawv/
                                                                                  (Receiving) 177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR
Any Related Transaction IDs: c8effd35b1f05b0ff74bb1946df9adfcba685495e9bb5f243f72c0755e38f182
 


A bit of back story: I have 2 wallets (Bitcion core 14.0), I sent out the original transaction from wallet
“1NdagsP6LGW4mLhujZ8HoLs8QjybncBawv” on OSX
to wallet
 “177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR” on Windows

I did not add enough transaction fee (new to this and did not understand)
 
The transaction took place at this time and date:4/23/17 07:06

4/23/17 07:06 Unconfirmed. Sent to (no label) 177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR -0.13400000

Below was shown in the sending wallet, when you click on transaction tab and then open transaction details:

Status: 0/unconfirmed, in memory pool
Date: 4/23/17 07:06
To: 177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR
Debit: -0.13399774 BTC
Transaction fee: -0.00000226 BTC
Net amount: -0.13400000 BTC
Transaction ID: c8effd35b1f05b0ff74bb1946df9adfcba685495e9bb5f243f72c0755e38f182
Transaction total size: 226 bytes
Output index: 1


I attempted to fix my insufficient fee

I did these things to try to remedy my fee under payment:

-zapwallettxes
I then tried abandonment
Transaction not eligible for abandonment (code -5)
I also used “time machine” on my Mac to restore to an earlier point before I made the transaction.(dated April 7th, may be import, due to the date on the messed up transactions) (My bitcoin data is on an external hard drive)

At this point I tried to use a backup of my wallet (It was made before the transaction, “4/23/17 07:06 Unconfirmed. Sent to (no label) 177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR -0.13400000
“ from wallet,  “1NdagsP6LGW4mLhujZ8HoLs8QjybncBawv”)

When I reopened my wallet, the original unconfirmed transaction was gone and replaced by the following: (The dates are off, not the actual date I sent the transaction) (The the date of my time machine restore)
TRUE   2017-04-07T15:50:22   Sent to      1EJFi2ivgcjTpXqg6Kz2st91h4qyf7weLF   -0.17732902   ec62fe6efdc749bf453fe5c1736d7cb514fe8c9c567de9f95a0a3bf04b5b01bc
TRUE   2017-04-07T15:50:22   Sent to      1LDFuin4Hbue4yYAkYNPd1jTZp8qNYRYBj   -0.00567098   ec62fe6efdc749bf453fe5c1736d7cb514fe8c9c567de9f95a0a3bf04b5b01bc
Which I assume is the original split in 2 (transaction and change wallet?).
The dates are totally different: 4/23/17 07:06 changed to 2017-04-07

The 3 following links seem to show the transaction:
https://blockchain.info/address/1NdagsP6LGW4mLhujZ8HoLs8QjybncBawv
https://blockchain.info/address/1EJFi2ivgcjTpXqg6Kz2st91h4qyf7weLF
https://blockchain.info/address/177AnkPzv12EWThJEQq4iSDC3W5EZUtfPR
 
The sending and reviving wallets "Final balance" is not what these pages show"

Below is what the sending wallet now looks like: (sorry don't know how to embed in page)
http://imgur.com/a/jIbM1

I was told by"Quickseller", " Even when I send a transaction to f2pool for confirmation, transactions are still prioritized based on the fee attached to the transaction, and you have attached a fee of 1 sat/byte, which would likely be too low for it to ever get confirmed -- you will still need to compete with other transactions that are sent to f2pool for confirmation by others.)
So apparently I cant do that
.
"Mocacinno" tried to help but I could not get his "child pays for parent" page to work with my transaction.

If the transaction is eventually dropped out of the memory pool, will it go back to my sending wallet (I'm scared because of the corruption that happened to my sending wallet)

Any and all help would be appreciated.