Transaction help

[jerk]

I wanted to try out the wiper app so a sent some bits to the address it created I then sent $1 worth to a friend through the app to see how it works, I chose no fee just for the hell of it, the transaction has yet to confirm and now has my transactions after that point messed up as well. I initiated the transaction on March 3rd and everyday since it keeps changing the date the network claims to have received the transaction.

So my question is will this transaction ever get confirmed?

https://blockchain.info/tx/2eb7444227c6cf70a7373f9f9c11c810ed0b0da8648eab71fd33560f8e5fa53f

[Gisado]

Blocktrail says that tx is expired. Maybe send it again with a fee?

[DeathAndTaxes]

The reason the date keeps changing is because your client keeps rebroadcasting the txn to the network to try and get it confirmed.  Nodes periodically delete old unconfirmed txns from the memory pool and when your client rebroadcasts it then it appears as a 'new' txns.

It may eventually confirm but it may be a very long time.   What wallet are you using.  That will determine your options to 'fix' this.

[jerk]

This was me testing out using wiper's bitcoin wallet.

[EcuaMobi]

This was me testing out using wiper's bitcoin wallet.

While blockchain shows your address has a balance of 0, blocktrail and insight shows it has BTC0.015
https://insight.bitpay.com/address/1HbzsSTSum4bgs115dhU2X7mzi6UF9rLqW

Did you try using the sweeper again (this time with a fee)? Which sweeper are you using?

[pooya87]

This was me testing out using wiper's bitcoin wallet.

While blockchain shows your address has a balance of 0, blocktrail and insight shows it has BTC0.015
https://insight.bitpay.com/address/1HbzsSTSum4bgs115dhU2X7mzi6UF9rLqW

Did you try using the sweeper again (this time with a fee)? Which sweeper are you using?

this is just because of different coding. bc.i and most explorers deduct the unconfirmed amount from the balance but insight shows unconfirmed transactions separately and only updates the balance after confirmation.

[jerk]

what are my options? this transaction has basically made my other transactions since not confirm as well...

[jerk]

anyone got any ideas? I sent the remaining balance back to one of my other wallets and it's basically made that wallet unspendable as well...nothing ever gets confirmations.

[EcuaMobi]

anyone got any ideas? I sent the remaining balance back to one of my other wallets and it's basically made that wallet unspendable as well...nothing ever gets confirmations.

You need to try resending the original unconfirmed transaction.
You can do that by getting the TX: https://blockchain.info/tx/2eb7444227c6cf70a7373f9f9c11c810ed0b0da8648eab71fd33560f8e5fa53f?format=hex
https://blockchain.info/decode-tx

Code:

{
   "lock_time":0,
   "size":226,
   "inputs":[
      {
         "prev_out":{
            "index":0,
            "hash":"1c71ef5e2e4ca989d680a5b889c8afd42b349125afa1e7b821063296dcd927f3"
         },
         "script":"483045022100e739f3f8868a9e6ae18ca9d7afaab7660e213b6d0f6f8afdc17e9458e296479c02205ad090e328f33c34b135e84b5235a8fa29880f73641f7cc94a15fc6f8b817eea0121030ab2b32813bc52b25b00c81d96d21fc6a283bc1192966e471d50d9ef5893d986"
      }
   ],
   "version":1,
   "vin_sz":1,
   "hash":"2eb7444227c6cf70a7373f9f9c11c810ed0b0da8648eab71fd33560f8e5fa53f",
   "vout_sz":2,
   "out":[
      {
         "script_string":"OP_DUP OP_HASH160 546e4852074defe61506eb3408ccdf91b4830c8d OP_EQUALVERIFY OP_CHECKSIG",
         "address":"18hRsgE63BTLZNgnNkqFW6T1ox4v4AebPv",
         "value":356000,
         "script":"76a914546e4852074defe61506eb3408ccdf91b4830c8d88ac"
      },
      {
         "script_string":"OP_DUP OP_HASH160 aff282b2bda6520486502e9978a7a4b32b1b8011 OP_EQUALVERIFY OP_CHECKSIG",
         "address":"1H3KmVtP8cZTP9zAK4fE1hwoH91zYruf95",
         "value":1144000,
         "script":"76a914aff282b2bda6520486502e9978a7a4b32b1b801188ac"
      }
   ]
}

Modify it to add a fee (by reducing an out value), sign it and re-broadcast it. You will need to install bitcoin-qt or other wallet and get familiar with command line.

[DeathAndTaxes]

I am not familiar with that wallet but it looks like the developer foolishly allowed users to creates txns which may never confirm.   The network will never forget about the 'bad' txn because your wallet keeps rebroadcasting it.  You will need to contact the developer of that wallet to find out how you can manually delete a txn locally so your wallet will stop broadcasting it.  Then within 24-72 hours most nodes should forget about it allowing you to create a new txn (this time hopefully w/ proper minimum fee).  The other option would be to export the private keys from that wallet and turn off that wallet (so it stops rebroadcasting). You then can import the keys into another wallet and send w/ proper fee but even then you will need to wait until other nodes drop the original as Bitcoin's built in double spend prevention will be working against you.

In general (for any wallet)
1) You must stop the original wallet from broadcasting the 'bad' txn otherwise #2 will never happen.
2) Without a rebroadcast most nodes will drop the 'bad' txn from the memory pool within 24-72 hours (it can vary and you have no control over this).
3) When the bad txn has been dropped you can respend those coins using either the same wallet or a different wallet by exporting and importing the keys.

If it was a common wallet I (bitcoin-core, armory, etc) I could give you instructions but this is a wallet specific process.  

[jerk]

Thanks guys! At least i know i have some options.