Quote from: leventturksoy on Today at 03:17:20 PM

Quote from: MrFreeDragon on Today at 02:40:56 PM

I really can not understand why are you trying here broadcast the transaction through simple pushtx services. The issue is in bitcoin address creation, as the TC used uncompressed public key for segwit address creation (it was said here several times).
That means that broadcasting the transaction to different nodes will not work in this case. They use the same protocol and can not accept the non-standard transaction.

So what is the reason for pushing tx to bitcoin network through different nodes?

Certain nodes not running Bitcoin Core allow for non-standard transactions. Although the odds of one of these nodes mining a block is incredibly slim, it's still worth taking a shot at since the BTC sum here is considerable.

So, it's not impossible/pointless, just very unlikely.

Ok, makes sense.
However you posted the signed transaction to move funds from stuck address 34dqaqvQNWMgbMJmmxVa8LeGz7St6ATT97 to you another address 3MN8FMhwPJcGRC5zEQL1UcQZC3YxmtB5k9, and you can't be sure who was the successful "tx pusher".

It is better to create a separate signed transaction to move funds from stuck address to your target new address AND bitcoin address of the "tx pusher". In case of success you will have your funds on your new address, and the "tx pusher" will receive his bounty to his bitcoin address (as both outputs will be in the same transaction).