Transaction

22e8ea22800e1dba0bdd3e9fd9c2de55e5f14787a42e481317307e6bf7c842d3
Timestamp (utc)
2024-03-25 05:02:08
Fee Paid
0.00000016 BSV
(
0.00175228 BSV
-
0.00175212 BSV
)
Fee Rate
10.02 sat/KB
Version
1
Confirmations
96,692
Size Stats
1,596 B

2 Outputs

Total Output:
0.00175212 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM@<div class="post">Whatever mechanism is chosen, it had better not significantly slow down the network or client unless strong anonymity is required/requested.<br/><br/>I've tried I2P and Tor, and, for me, super-strong privacy isn't worth the performance cost.<br/><br/>Also, regarding forking the block chain by a network split:<br/><br/>It's only "really bad" if I can get away with double-spending some coins before the network merges again.<br/>If I'm buying valuable stuff, then the merchants will likely require 6 confirmations before releasing the goods, so I'd have to be able to keep the network split for an hour or more.<br/><br/>Merchants will likely have very-well-connected, long-running nodes.&nbsp; For example, the Bitcoin Faucet has 66 connections right now.&nbsp; If I wanted to try to implement a "fork the block chain attack" I'd have to somehow manage to insert my "cancer nodes" in between two merchants that I want to rip off (I'll end up ripping off one of the two, because eventually one of the two double-spend transactions will "win").<br/><br/>I don't know enough about network analysis to figure out how many cancer nodes you'd need to have a significant chance of getting in between two merchants with 60+ connections in a network of (say) 1,000 non-cancerous nodes, but I bet it is a very large number.<br/></div> text/html
    https://whatsonchain.com/tx/22e8ea22800e1dba0bdd3e9fd9c2de55e5f14787a42e481317307e6bf7c842d3