Jim,
i solved this issue by changing the client. I've imported the keys to bitcoin-qt and now everything works like it should. When the transaction fee isn't high enough the client suggests a higher fee and the transaction gets confirmed.
You should work on this, loved Multibit....
Zackie
Topic: Mulbit 0.5.9 Issue : unable to send coins [finally solved] (Read 1028 times)
Hi jim,
looks like it's also a Multibit issue. The client picks the micropayments randomly (like any other client) without suggesting a higher fee (like original bitquoin-gt does) due the size. I'm not able to see the size BEFORE sending the transaction.
Is it possible to solve this issue somehow? Is it possible to cancel an unconfirmed transaction? Or add a higher fee?
Zackie
looks like it's also a Multibit issue. The client picks the micropayments randomly (like any other client) without suggesting a higher fee (like original bitquoin-gt does) due the size. I'm not able to see the size BEFORE sending the transaction.
Is it possible to solve this issue somehow? Is it possible to cancel an unconfirmed transaction? Or add a higher fee?
Zackie
Hi jim618,
after reading about 1000 articles on this forum and studying the transaction details, I don't think it's a multibit problem anymore. I think the coins weren't old enough when I first tried to send them. The next day I was able to send them in small chunks between 0.5 an 5 BTC. But not all transactions went trough. Some are still unconfirmed, but seen by 4 peers. Those were put together of many, many mircropayments, which made the block very big an the priority low.
Do you know how long it will take to confirm such a transaction? It's about 45 hours old by now...
Beste regards, zackie
edit:
https://blockchain.info/de/tx/819a6d058f5c4bb8caa261e6a6b4b98cbe77129186bc667d9433f1e43d3bf461
The transaction has 25530 bytes in the block. 27.000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee.
So why does the transaction not get confirmed?
after reading about 1000 articles on this forum and studying the transaction details, I don't think it's a multibit problem anymore. I think the coins weren't old enough when I first tried to send them. The next day I was able to send them in small chunks between 0.5 an 5 BTC. But not all transactions went trough. Some are still unconfirmed, but seen by 4 peers. Those were put together of many, many mircropayments, which made the block very big an the priority low.
Do you know how long it will take to confirm such a transaction? It's about 45 hours old by now...
Beste regards, zackie
edit:
https://blockchain.info/de/tx/819a6d058f5c4bb8caa261e6a6b4b98cbe77129186bc667d9433f1e43d3bf461
The transaction has 25530 bytes in the block. 27.000 bytes in the block are set aside for the highest-priority transactions, regardless of transaction fee.
So why does the transaction not get confirmed?
It sounds like it was sent to the initial bitcoind ok then but not passed on.
Nothing waiting or increasing the fee (or a combination) should help make your transaction more appealing to the miners yes.
Nothing waiting or increasing the fee (or a combination) should help make your transaction more appealing to the miners yes.
Your fee might be too low for the size of the transaction. 0.0001 BTC only buys you a thousand bytes worth of 'relay fee' if you have small/ young inputs.
If you look in the help, in the Support section, there is a topic with more help on this.
If you look in the help, in the Support section, there is a topic with more help on this.
Yes, you're right. I have young inputs (not small). So I have to wait or increase the fee? I get a "transaction sent successfully" message, not the "insufficient funds" message mentioned in the help.
Your fee might be too low for the size of the transaction. 0.0001 BTC only buys you a thousand bytes worth of 'relay fee' if you have small/ young inputs.
If you look in the help, in the Support section, there is a topic with more help on this.
If you look in the help, in the Support section, there is a topic with more help on this.
Hi jim618,
maybe you can help me out? I have a strange problem with Multibit 0.5.9.
I have exactly 11.30795649 coins in my wallet. After sending 11 BTCs, i have exactly 0.30785649 (-0.0001 BTC transaction fee) coins remaining in my pocket but only 0.0009136 available for spending. Neither the sent 11 BTCs, nor the adress i've sent them to appears in the blockchain.
After reseting the blockchain and transactions I have the 11.30795649 in my wallet, completely available for spending. I tried different
amounts of BTC an even with version 0.4.23! Same problem... But I was able to send BTC's in the past.
What happened here?
Best regards,
Zackie
maybe you can help me out? I have a strange problem with Multibit 0.5.9.
I have exactly 11.30795649 coins in my wallet. After sending 11 BTCs, i have exactly 0.30785649 (-0.0001 BTC transaction fee) coins remaining in my pocket but only 0.0009136 available for spending. Neither the sent 11 BTCs, nor the adress i've sent them to appears in the blockchain.
After reseting the blockchain and transactions I have the 11.30795649 in my wallet, completely available for spending. I tried different
amounts of BTC an even with version 0.4.23! Same problem... But I was able to send BTC's in the past.
What happened here?
Best regards,
Zackie
Jump to: