|
Title: very small output? Post by: Micon on November 17, 2013, 06:30:49 AM https://blockchain.info/tx/89b558e5190bdfe1ad98356624890750c8420d0192df1c43ec4885ef38bf725f
Confirmation Warnings This transaction has a very small output and is none standard Anyone see this before? Fee included Title: Re: very small output? Post by: DannyHamilton on November 17, 2013, 02:53:26 PM https://blockchain.info/tx/89b558e5190bdfe1ad98356624890750c8420d0192df1c43ec4885ef38bf725f Confirmation Warnings This transaction has a very small output and is none standard Anyone see this before? Fee included It happens when you try to send a transaction that includes an output smaller than approximately 0.00005 BTC. The most recent version of the reference client refuses to relay transactions that include such small outputs. Title: Re: very small output? Post by: Kouye on November 17, 2013, 03:16:06 PM What I don't understand is how is it possible that this tx has several inputs from the same address? ???
Title: Re: very small output? Post by: DannyHamilton on November 17, 2013, 03:22:53 PM What I don't understand is how is it possible that this tx has several inputs from the same address? ??? They received several payments to the same address. Each payment is a separate input when you spend them later. This is why the recent updates to the reference client block the relay of extremely small outputs. If you receive many extremely small outputs, they each must be stored separately as part of the UTXO set, significantly increasing the UTXO size. then they each have to be included separately as inputs later when spending them, which can lead to excessively large (in terms of bytes) transactions. As such, the transaction fees necessary to spend such tiny outputs can end up being larger than the sum of the outputs themselves. Title: Re: very small output? Post by: Kouye on November 17, 2013, 03:34:08 PM They received several payments to the same address. Each payment is a separate input when you spend them later. This is why the recent updates to the reference client block the relay of extremely small outputs. If you receive many extremely small outputs, they each must be stored separately as part of the UTXO set, significantly increasing the UTXO size. then they each have to be included separately as inputs later when spending them, which can lead to excessively large (in terms of bytes) transactions. As such, the transaction fees necessary to spend such tiny outputs can end up being larger than the sum of the outputs themselves. Once again, thank you for the cristal clear answer. For some reason I assumed the balance of an address was merged into a single "input", but I understand how not possible it is, now. |