Transaction

2bf81afd7a2d6b19e2358f335327cda271cdfad2b96e1c14ccd8bbb31b8dca72
Timestamp (utc)
2024-03-28 12:12:50
Fee Paid
0.00000015 BSV
(
0.00569975 BSV
-
0.00569960 BSV
)
Fee Rate
10.35 sat/KB
Version
1
Confirmations
93,486
Size Stats
1,449 B

2 Outputs

Total Output:
0.00569960 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM¬<div class="post">The current sending by IP is not very useful: it connects to the IP, so you'd like to use TOR for anonymity, but then it can totally be eavesdropped and man-in-the-middled.<br/><br/>The future plan for sending to an IP is to make it a bitcoin address plus IP, like:<br/><br/>1auaDZCFYqaGx4FKS5WenNfurk2SkoDu4h&lt;someseparatorcharacter&gt;1.2.3.4<br/>or<br/>1auaDZCFYqaGx4FKS5WenNfurk2SkoDu4h&lt;someseparatorcharacter&gt;domain.com<br/><br/>I need suggestions for the separator character.&nbsp; ":" is a candidate, but IPv6 has : in it and that might get confusing.&nbsp; Something that's allowed in url parameters would be nice.<br/><br/>I want to use SSL for the connection, using the bitcoin address' public key as the cert.&nbsp; You would be certain you're connected to who you thought, and safely encrypted.&nbsp; The bitcoin address would not be used for the transaction, only for authentication.&nbsp; A new generated bitcoin address would be sent through the SSL connection.<br/><br/>Since it's authenticated, it would then be safe to allow the IP address to be a domain name.&nbsp; Some care taken that if a proxy is used, it uses socks4a instead of DNS lookup.</div> text/html
    https://whatsonchain.com/tx/2bf81afd7a2d6b19e2358f335327cda271cdfad2b96e1c14ccd8bbb31b8dca72