Transaction

9890be2b4e9b122c7a9cfbcab0bbc0c8317fe33900ad089057c154e9a4a8b0c1
Timestamp (utc)
2024-03-27 16:43:50
Fee Paid
0.00000013 BSV
(
0.00732256 BSV
-
0.00732243 BSV
)
Fee Rate
10.02 sat/KB
Version
1
Confirmations
93,757
Size Stats
1,297 B

2 Outputs

Total Output:
0.00732243 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post">Actually... prioritizing free transactions based on both amount and their "age" should make this attack toothless.<br/><br/>The basic idea is that if you're spamming lots of small free transactions, you'll be creating lots of brand-new "pennies" (you'll take an old 50BTC generated transaction, then split off a penny and get a penny and 49.99 change.&nbsp; Then split that 49.99 to get another penny, and so on and so on).<br/><br/>Sorting pending free transactions so that larger-value transactions and free transactions with inputs deep in the block chain ("old money") are given priority would let normal transactions go through.<br/><br/>The spammy transactions would still take up network bandwidth and disk space; if that becomes a problem, nodes could just ignore small, new transactions (not relay them) and let the nodes that are doing the spamming queue up and rebroadcast the transactions.&nbsp; They'd trickle into the network eventually, and in the meantime the spammer's bit-pennies would be tied up.<br/></div> text/html
    https://whatsonchain.com/tx/9890be2b4e9b122c7a9cfbcab0bbc0c8317fe33900ad089057c154e9a4a8b0c1