{"type":"rich","version":"1.0","author_name":"npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","author_url":"https://nostr.ae/npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-05-06\n📝 Original message:Thanks Greg for the testing!\n\nNote that to those who are reviewing the doc, a few minor tweaks to\nwording and clarification have been made to the git version, so please\nreview there.\n\nOn 05/03/16 05:02, Gregory Maxwell wrote:\n\u003e On Mon, May 2, 2016 at 10:13 PM, Matt Corallo via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e Hi all,\n\u003e\u003e\n\u003e\u003e The following is a BIP-formatted design spec for compact block relay\n\u003e\u003e designed to limit on wire bytes during block relay. You can find the\n\u003e\u003e latest version of this document at\n\u003e\u003e https://github.com/TheBlueMatt/bips/blob/master/bip-TODO.mediawiki.\n\u003e \n\u003e Thanks Matt!\n\u003e \n\u003e I've been testing this for a couple weeks (in various forms).  I've\n\u003e been getting over 96% reduction in block-bytes sent. I don't have a\n\u003e good metric for it, but bandwidth spikes are greatly reduced. The\n\u003e largest blocktxn message I've seen on a node that has been up for at\n\u003e least a day is 475736 bytes. 94% of the blocks less than 100kb must be\n\u003e sent in total.\n\u003e \n\u003e In the opportunistic mode my measurements are showing 73% of blocks\n\u003e transferred with 0.5 RTT even without prediction, 87% if up to 4\n\u003e additional transactions are predicted, and 91% for 30 transactions (my\n\u003e rough estimate for the 10k maximum prediction suggested in the BIP.\n\u003e"}