Transaction

f0b8cb12c01a94a80a3c09db590bccdfbfc8d26fe9d0376c3d62eff5e4b81b11
2024-03-25 18:45:13
0.00000015 BSV
(
0.01124096 BSV
-
0.01124081 BSV
)
10.26 sat/KB
1
73,732
1,461 B

2 Outputs

Total Output:
0.01124081 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¹<div class="post">Yeah, I2P is much easier to automate in that regard. I could setup some .onions manually and post them to the list to be used as seeds. I have always-on nodes that can just be tied to Tor with minimal effort.<br/><br/>I used to be a big advocate of Tor, but after I started using I2P I found it to be much, much better in a lot of ways. Biggest improvement is speed. <img alt="Wink" border="0" src="/static/img/emoticons/wink.gif"/>&nbsp; Too bad they wrote it in Java.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=22.msg113#msg113">Quote from: satoshi on January 20, 2010, 10:05:28 PM</a></div><div class="quote">I've been thinking about that for a while. &nbsp;I want to add the backend support for .onion addresses and connecting to them, then go from there.<br/><br/>There aren't many .onion addresses in use for anything because the user has to go through a number of steps to create one. &nbsp;Configure TOR to generate a .onion address, restart TOR, configure it with the generated address. &nbsp;Perhaps this is intentional to keep TOR so it can't be integrated into file sharing programs in any sufficiently automated way.<br/><br/></div></div> text/html
    https://whatsonchain.com/tx/f0b8cb12c01a94a80a3c09db590bccdfbfc8d26fe9d0376c3d62eff5e4b81b11