search

Multibit-Legacy / multibit-hd

Deprecated Bitcoin Wallet
https://multibit.org/blog/2017/07/26/multibit-shutdown.html
Other
169 stars 124 forks source link

Been sending a transaction for over 30 hours now.... #965

Open hoodsterman opened 7 years ago

hoodsterman commented 7 years ago

Hi! I sent a payment yesterday around 13:30, it´s still broadcasting over the network and it´s been seen by 17 peers... Earlier when i had this delayed, i have been able to fix by repair my wallet, but this i done everything and still nothing... I know delays not these day but it has never been this bad... i have also checked blockchain.info and it says its still unconfirmed... What can i do?

Danielerickson commented 7 years ago

I have the same issue. But I know what the problem is. I had unwisely set the fee payment low in preferences. The issue is I have been waiting 2 days now for the payment to go through. It is seen by 37 peers but still unconfirmed. How do I get the transaction to proceed or cancel it.

Danielerickson commented 7 years ago

00c7df9094ad2af407c332c024dd45e3d533a880f6a4d11c583d15862225aea3

hoodsterman commented 7 years ago

Did you find a solution, my friend? The thing is that i have never altered or changed the settings for the fee payment... It´s the exact same as always... My biggest problem is that i thought that it just was a minor glitch and hence, just work it self out within 24 h, (it´s happen before...) so i used the same damned adress for a another payment, so in 2-3 day the adress its gonna get voided... Thats the problem... Is there anyway to cancel it and get it back to my wallet...?

Danielerickson commented 7 years ago

I opened a ticket with Keepkey and while it is assigned no one has gotten back to me. I have read that the send transaction will delete itself and the funds return to my account but that has not happened yet. It has been more than 36 hours. My confidence in Multibit is lowering. I'm thinking that this is not ready for prime-time yet. I'll switch to a different wallet once this gets cleaned up.

Kcchouette commented 7 years ago

I switch to version 0.5.1 and now it's fixed for me