Transaction

e3edd2175704f4ea9a2e984b27ca167d6dcd97a3e85d3cf7661574c30ad7d5e7
2024-03-22 12:51:13
0.00000041 BSV
(
0.00682191 BSV
-
0.00682150 BSV
)
10.24 sat/KB
1
70,953
4,002 B

2 Outputs

Total Output:
0.00682150 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¦<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1306.msg14525#msg14525">Quote from: Tritonio on September 29, 2010, 01:51:15 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1306.msg14524#msg14524">Quote from: nanotube on September 29, 2010, 01:42:32 PM</a></div><div class="quote">Hey, so i've been the recipient of a few of these microtransactions<br/>so now i have several transactions in my wallet that are now perpetually in the '0/unconfirmed' state<br/></div>They will get confirmed when someone that doesn't require fees include them in his/her block.<br/></div><br/>yes and.... at this point /all/ clients require fees for transactions &lt;0.01, do you have any reason to expect that this will change at any point in the future? i don't. so "never will get confirmed" seems a reasonable approximation to reality.<br/><br/><div class="quoteheader">Quote</div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1306.msg14524#msg14524">Quote from: nanotube on September 29, 2010, 01:42:32 PM</a></div><div class="quote">so the question is, if i send stuff, will it include those bitcoins in my sends, thus propagating the invalid chain? what is to be done here?<br/></div>There is no invalid chain just because someone didn't want to pay the fee. It will just take longer for them to get included in a block and until then they can be double spend if someone hasn't heard about them. BTW if nodes don't propagate transactions just because they don't like them it will be dangerous since it will be easier for someone to double spend bitcoins.<br/></div><br/>yes but the problem is that the client doesn't let the user choose which coins to spend, it does it all "automagically" behind the scenes. so how would a user know if he's sending confirmed coins or unconfirmed coins?<br/><br/><div class="quoteheader">Quote</div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1306.msg14524#msg14524">Quote from: nanotube on September 29, 2010, 01:42:32 PM</a></div><div class="quote">note also that this seems like a valid way to spam the network - send a bunch of microtransactions without the fee, so you can effectively multispend the same bit of btc and spam everyone's wallets with bogus microtransactions at no cost to you?<br/></div>You can also send the same 1BTC back and forth between two clients, using different addresses every time. If you do it fast enough you will probably be able to fill up the block that everyone is trying to generate and therefore make the network really slow and lower the chances for legitimate transactions to get into blocks... Also if you do it reeeealllly fast you could saturate the network for a long time, even after you exit the network. You will just leave the rest trying to fit hundreds of thousands of transactions into blocks... I don't know if there is any protection in the protocol from this kind of attacks... If not, they are quite easy to be done. We really need fixed transaction fees with the option to change your preferences on what is the fixed price you accept and what fee to include in your own transactions.<br/></div><br/>yes, but that's a separate issue. i'm really trying to figure out what, if anything, to be doing about the handful of never-to-be-confirmed transactions i have in my wallet, whether the client will prioritize sending other coins first or not, and if not... that means it's possible that i'll never be able to make a send transaction that will be confirmed, because the unconfirmed bits of coin will be included. which would in turn mean that my whole wallet is foobar.</div> text/html
    https://whatsonchain.com/tx/e3edd2175704f4ea9a2e984b27ca167d6dcd97a3e85d3cf7661574c30ad7d5e7