Transaction

33bd07bb9740326a03d460213ca9f1cdc3d75acbfe0ec80ed16841763a2fb42e
Timestamp (utc)
2024-03-26 08:34:36
Fee Paid
0.00000013 BSV
(
0.01008194 BSV
-
0.01008181 BSV
)
Fee Rate
10.72 sat/KB
Version
1
Confirmations
93,601
Size Stats
1,212 B

2 Outputs

Total Output:
0.01008181 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÀ<div class="post">Hello,<br/><br/>I have had another idea. <img alt="Tongue" border="0" src="/static/img/emoticons/tongue.gif"/><br/><br/>It would be very cool to be able to have TOR and I2P seeds. For example: I could run BT within TOR-land on a .onion address. A client could connect their BT to TOR and have it seed from a .onion address and use it as a connected peer. (Likewise for I2P: someone could run a .i2p service that is -- well -- BC).<br/><br/>I might setup a couple of nodes in this fashion and post the tunnels on this forum. I already run a lot of I2P and TOR nodes so adding BC to the mix is quite trivial.<br/><br/>I support the idea of making BC compatible with TOR and I2P to increase the privacy of the system. I mean: why re-invent the wheel? There are thousands of mix network nodes just sitting there that can be used to enhance BC. <img alt="Cheesy" border="0" src="/static/img/emoticons/cheesy.gif"/><br/><br/>Cheers!<br/><br/></div> text/html
    https://whatsonchain.com/tx/33bd07bb9740326a03d460213ca9f1cdc3d75acbfe0ec80ed16841763a2fb42e