Bitcoin Forum
September 24, 2017, 09:16:03 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: [Support] I sent some bitcoin FROM MultiBit but they are stuck.  (Read 3941 times)
jim618
Legendary
*
Offline Offline

Activity: 1708



View Profile WWW
March 30, 2013, 11:17:10 AM
 #1

What is the symptom ?
You sent some bitcoin from MultiBit but the bitcoin is stuck and never confirms. The bitcoins never arrive.
In the 'Transactions' tab the transaction is shown with a square ("Seen by 1 peer") or, very rarely, a triangle ("Seen by 0 peers").


What does a status of a square or triangle mean ?
When you press the 'Send' button, MultiBit broadcasts your transaction to a single bitcoind peer. It then listens on all its other connections to check that the transaction has been broadcast successfully. If you see a square or triangle in the transaction status then this means that the broadcast and propagation through the Bitcoin network was unsuccessful.


What can you do about it ?
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:

1) You lost your network connection and the transaction did not get sent successfully to the peer. If you suspect this is the cause, do the following:
1.1) Close MultiBit.
1.2) Fix your network connection and try it out using a browser.
1.3) Restart MultiBit and it will re-transmit any transactions that were unsuccessfully sent previously. It can sometimes take a couple of minutes to send a transaction and for it to propagate through the Bitcoin network.


2) The peer received the transaction but "did not like it". In this case it will not pass it onto other bitcoind instances. Your transaction thus never propagates across the Bitcoin network and the recipient will not receive it. It also will not appear on sites such as blockchain.info.

There are various reasons why a peer does not propagate a transaction. In a rough order of frequency they are:
2.1) There are lots of satoshi sized inputs in your wallet and the transaction fires the anti-spam rules.
2.2) The fee is too small and the peer chooses not to relay it.
2.3) The transaction is a double spend. Doubles spends aren't relayed through the network.
2.4) Some other reason - this is not a definitive list.

You can get an idea of the size of the transaction you created by doing a right click on the transaction and choosing 'Show Transaction Details'. In the box 'Raw transaction' you can see a text representation of the transaction. A typical fee for a transaction is 0.0005 or 0.001 BTC per kB of transaction.

You can remove the transaction that never propagated by doing a "Tools | Reset blockchain and transactions" and resetting the blockchain to the day before before the transaction's date.

To spend a large number of very small amounts of bitcoin can be difficult as they are practically worthless. It is more art than science as you have to avoid the anti-spam rules and convince a miner to include your big transaction in a block.
You can try:
1) Increasing the fee that you use in the 'View | Preferences"
2) Letting the inputs age a while. The newer the transactions you try to spend the 'spammier' they are seen to be.


MultiBit HD   Lightweight desktop client.                    Bitcoin Solutions Ltd   Bespoke software. Consultancy.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!