Transaction is not exist for almost 2 weeks

[coinHasher123]

Pleas helps, I recently sent btc from my local wallet to cryptopia exchange and the never receive it

I have 2 laptops both laptop have the same wallet that using multibit client 5.14

Laptop #1 send with transaction detail below
status: seen by 1 peer. Pending/unconfirmed
date: 03 Dec 2017
amount sent: 0.010579
fee 0.0001425
total debit: 0.01059325

laptop#1 now have zero balance


Raw transaction
  e08534c29b38b15221e5663250d779e5f548e2d4f636adf9dc32ec44254e9ea7: Seen by 1 peer. Pending/unconfirmed.
     from 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N / 80e392626a3765222c78aa27746b952171193e371efa61b8e14b62880d58da4e:1
     from 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N / df37597af223f6e482a4ed9dcda6b0b948769e7d7cff005950d465ddbe4f970f:1
     from 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N / ee7bfa6010b4d04f19ac14abf90a99de87163be4b2e02b1dce04f5f1df7fc20a:1
     from 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N / ea5b9ec9ec6a095a2680d618245d3f305e5bc419b20004c39fdd280b54dc092a:0
     from 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N / 359ed2df46f3ffcfccdc9f67a1b9b187b0e454bdc48897d80a1d13787ebe69a8:1
       to 13Z7PVPjKUrGEEUQG277GkcNKSt5MHF9qp 0.10579 BTC


I think the fee too low and the transaction got lost in the network or never broadcast. I have tried blockchain, blockexplorer, viabtc to lookup or re-broadcast the tx below all of them stated the transaction is not exist, even member here also tried to accelerated the tx but still the tx not show up.

Now on my laptop#2 using same multibit client, I still see the balance 0.01059325 in my wallet, I also show here too https://blockchain.info/address/158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N
What is going here ? can someone explain and what can I do do now, been waiting for 2 weeks.
Can I resend the btc again to the same address or may be another exchange address if I do re-send what if the proper fee amount I should pay. Please advice


Send address: 158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N
Receive address: 13Z7PVPjKUrGEEUQG277GkcNKSt5MHF9qp    (cryptopia)
tx: e08534c29b38b15221e5663250d779e5f548e2d4f636adf9dc32ec44254e9ea7

[1715043348]

1715043348

[1715043348]

1715043348

[1715043348]

1715043348

[darkangel11]

Pleas helps, I recently sent btc from my local wallet to cryptopia exchange and the never receive it

I have 2 laptops both laptop have the same wallet that using multibit client 5.14

Do you mean multibit classic or multibit HD? Both of these are no longer supported as the team has abandoned the project, but an old multibit (classic) version has been outdated for more than a year. I remember that I had trouble moving my coins to HD 10 months ago, as it did not  allow you to choose fees manually which meant the transactions were being stuck for days. As you can see the situation doesn't look good since you can't extract the private key and move it to another wallet manually, you have to send the coins to a new address through the outdated multibit client. AFAIK the only way to do it now is to accelerate the transaction.

status: seen by 1 peer. Pending/unconfirmed

It seems this is the main problem now. The transaction doesn't get broadcasted at all and it's not visible on blockchain. You'd have to deal with this issue first before even having to worry about a low fee.
I can already tell you that it's going to be a pain to extract your coins from that wallet as it has already been like that in 2016 and now with the rising fees it has become even worse. Try rebroadcasting the transaction until it appears on blockchain.info

[coinHasher123]

Pleas helps, I recently sent btc from my local wallet to cryptopia exchange and the never receive it

I have 2 laptops both laptop have the same wallet that using multibit client 5.14

Do you mean multibit classic or multibit HD? Both of these are no longer supported as the team has abandoned the project, but an old multibit (classic) version has been outdated for more than a year. I remember that I had trouble moving my coins to HD 10 months ago, as it did not  allow you to choose fees manually which meant the transactions were being stuck for days. As you can see the situation doesn't look good since you can't extract the private key and move it to another wallet manually, you have to send the coins to a new address through the outdated multibit client. AFAIK the only way to do it now is to accelerate the transaction.

status: seen by 1 peer. Pending/unconfirmed

It seems this is the main problem now. The transaction doesn't get broadcasted at all and it's not visible on blockchain. You'd have to deal with this issue first before even having to worry about a low fee.
I can already tell you that it's going to be a pain to extract your coins from that wallet as it has already been like that in 2016 and now with the rising fees it has become even worse. Try rebroadcasting the transaction until it appears on blockchain.info

Thank you for response. I am using the multibit classic, this is the original installed on my laptop back in 2013 or 2014, the issue I can not broadcast is the because on the blockchain said the tx not exist
do you know site or tool I can re-broadcast.

Any other help will appreciate it.

[darkangel11]

Read this:
https://multibit.org/help/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

There are two main reasons why a transaction gets stuck on "Seen by one peer" and does not propagate through the Bitcoin network. These are:
You lost your network connection and the transaction did not get sent successfully to the peer (did not broadcast)
The peer received the transaction but "did not like it" (did not relay)

There are various reasons why a peer does not relay a transaction. In a rough order of frequency they are:

There are lots of tiny inputs (under 5432 satoshis) in your wallet and the transaction fires the anti-spam rules.
The fee is too small and the peer chooses not to relay it.
The transaction is a double spend. Doubles spends aren't relayed through the network.

You can remove the transaction that never propagated by doing a 'Tools | Reset Block chain and Transactions'.

IMO this is where your problem lies. I'd reset and try again until it gets accepted. I see no other way since you can't upgrade to a newer version and can't increase the fee. Once you get the transaction to appear in the blockchain you can accelerate it, but without this happening there's not much you can do since it's still stuck in your wallet.

[coinHasher123]

Read this:
https://multibit.org/help/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

There are two main reasons why a transaction gets stuck on "Seen by one peer" and does not propagate through the Bitcoin network. These are:
You lost your network connection and the transaction did not get sent successfully to the peer (did not broadcast)
The peer received the transaction but "did not like it" (did not relay)

There are various reasons why a peer does not relay a transaction. In a rough order of frequency they are:

There are lots of tiny inputs (under 5432 satoshis) in your wallet and the transaction fires the anti-spam rules.
The fee is too small and the peer chooses not to relay it.
The transaction is a double spend. Doubles spends aren't relayed through the network.

You can remove the transaction that never propagated by doing a 'Tools | Reset Block chain and Transactions'.

IMO this is where your problem lies. I'd reset and try again until it gets accepted. I see no other way since you can't upgrade to a newer version and can't increase the fee. Once you get the transaction to appear in the blockchain you can accelerate it, but without this happening there's not much you can do since it's still stuck in your wallet.

Thanks, I will try tonight

[coinHasher123]

Read this:
https://multibit.org/help/v0.5/help_support_sentBitcoinFromMultibitButTheyAreStuck.html

There are two main reasons why a transaction gets stuck on "Seen by one peer" and does not propagate through the Bitcoin network. These are:
You lost your network connection and the transaction did not get sent successfully to the peer (did not broadcast)
The peer received the transaction but "did not like it" (did not relay)

There are various reasons why a peer does not relay a transaction. In a rough order of frequency they are:

There are lots of tiny inputs (under 5432 satoshis) in your wallet and the transaction fires the anti-spam rules.
The fee is too small and the peer chooses not to relay it.
The transaction is a double spend. Doubles spends aren't relayed through the network.

You can remove the transaction that never propagated by doing a 'Tools | Reset Block chain and Transactions'.

IMO this is where your problem lies. I'd reset and try again until it gets accepted. I see no other way since you can't upgrade to a newer version and can't increase the fee. Once you get the transaction to appear in the blockchain you can accelerate it, but without this happening there's not much you can do since it's still stuck in your wallet.

Thanks, I will try tonight

UPDATE:

From multibit client 5.14 tried to reset blockchain and transaction for 5 times, still show zero balance
Upgrade multibit to 5.19 and tries 2 more times still zero balance  and the 3rd time the balance show up (0.1059325) but the last transaction no longer there (e08534c29b38b15221e5663250d779e5f548e2d4f636adf9dc32ec44254e9ea7)
So I think that transaction never got into the mempool and got dropped from the network

One thing I noticed the blockchain balance https://blockchain.info/address/158QPjBPmdcoK9p1toHaWyGiePNmkeTz8N  showing 0.10594026  and the multibit balance is 0.1059325 and the different is
0.00000776 in this transaction https://blockchain.info/tx/bdd2eb9ea6b74c9c0a2abacf019e3538497040296b6cf013430524111e29ad60 and has not confirm yet, why blockchain included the
0.00000776 if the tx still unconfirmed.

If I use multibit and send some btc to another address will the previous tx bdd2eb9ea6b74c9c0a2abacf019e3538497040296b6cf013430524111e29ad60  cause any problem.

Please helps


----------------------
UPDATE:

Problem solved,
I end up export private key from multibit and import in Bitcoin wallet and run command zapwalletes then rescan, balance show up correct, send another transaction out with higher fee and got confirm with 1 hour