Transaction

140bdaca3f21d23960c48d0bec7232d61f6f3473bbaf70e60b261ef08c8a90c0
Timestamp (utc)
2024-03-29 04:00:01
Fee Paid
0.00000016 BSV
(
0.00438929 BSV
-
0.00438913 BSV
)
Fee Rate
10.52 sat/KB
Version
1
Confirmations
95,494
Size Stats
1,520 B

2 Outputs

Total Output:
0.00438913 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMô<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6811#msg6811">Quote from: lachesis on July 31, 2010, 01:45:23 PM</a></div><div class="quote">The "0x00" groups each represent one byte.</div><br/>Oops <img alt="Embarrassed" border="0" src="/static/img/emoticons/embarrassed.gif"/><br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6811#msg6811">Quote from: lachesis on July 31, 2010, 01:45:23 PM</a></div><div class="quote">breaking change</div><br/>I think the best way to phase in protocol bufferswould to avoid breaking changes to start with, instead start with protocol buffers for the local files (like the wallet), which would gain us a little bit of size on disk, ease of reading the wallet file in other software, and get some experience using protocol buffers. Then is the time to start phasing in protocol buffers for networking in my opinion.<br/><br/>Does the current version of bitcoin have any handling for ignoring chunks of a packet? If so, phasing in protocol buffers could be as simple as writing the current packet AND writing the protocol buffer (as an ignored field for older clients), then once enough people have upgraded get rid of the old encoding.</div> text/html
    https://whatsonchain.com/tx/140bdaca3f21d23960c48d0bec7232d61f6f3473bbaf70e60b261ef08c8a90c0