Transaction

fc93f2e513d514e2a4d0c6a3c12d51b547b83473010a086bf2e326c0e3248f3e
Timestamp (utc)
2024-03-24 15:37:17
Fee Paid
0.00000016 BSV
(
0.01117532 BSV
-
0.01117516 BSV
)
Fee Rate
10.1 sat/KB
Version
1
Confirmations
97,472
Size Stats
1,583 B

2 Outputs

Total Output:
0.01117516 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM3<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/fc93f2e513d514e2a4d0c6a3c12d51b547b83473010a086bf2e326c0e3248f3e