Transaction

a4e61e86efc3776fcd67f20be960e54837f01f52a6ce6a4ad3a2a00a7ded7ce2
Timestamp (utc)
2024-03-21 20:25:41
Fee Paid
0.00000016 BSV
(
0.00551191 BSV
-
0.00551175 BSV
)
Fee Rate
10.1 sat/KB
Version
1
Confirmations
104,413
Size Stats
1,583 B

2 Outputs

Total Output:
0.00551175 BSV
  • j"19HxigV4QyBv3tHpQVcUEQyq1pzZVdoAutM3<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6547#msg6547">Quote from: martin on July 29, 2010, 11:29:31 PM</a></div><div class="quote">Some people have been suggesting that protocol buffers might be larger than the custom written packet layout. I suspect that actually it would be *smaller* due to some of the clever encoding used in protocol buffers. <br/></div>I agree that it could be smaller; not necessarily because of clever encoding, but because it would allow us to drop reserved bytes and the like.<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=632.msg6547#msg6547">Quote from: martin on July 29, 2010, 11:29:31 PM</a></div><div class="quote">To resolve this, I think a test is in order, I shall encode a wallet file/network packet using protocol buffers and compare the size the packets in the current scheme. However, I have no idea what's in a packet, what data is stored in a packet, and in what format?<br/></div>That would be the hard part, of course. If you want to test with the version packet (not really ideal, since it's only sent once per connection), I've decoded that fully:<br/><a href="http://bitcointalk.org/index.php?topic=231.msg6250#msg6250">http://bitcointalk.org/index.php?topic=231.msg6250#msg6250</a></div> text/html
    https://whatsonchain.com/tx/a4e61e86efc3776fcd67f20be960e54837f01f52a6ce6a4ad3a2a00a7ded7ce2