<oembed><type>rich</type><version>1.0</version><author_name>npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_name><author_url>https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-07-17&#xA;📝 Original message:A couple of half-baked thoughts:&#xA;&#xA;On Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley &lt;keziahw at gmail.com&gt; wrote:&#xA;&#xA;&gt; If there&#39;s support for this proposal, I can begin working on the specific&#xA;&gt; implementation details, such as the bloom filters, message format, and&#xA;&gt; capability advertisment, and draft a BIP once I have a concrete proposal&#xA;&gt; for&#xA;&gt; what those would look like and a corresponding precise cost/benefit&#xA;&gt; analysis.&#xA;&gt;&#xA;&#xA;I&#39;d encourage you to code up a prototype first (or at the same time), in&#xA;whatever programming language / networking library you&#39;re most familiar&#xA;with.&#xA;&#xA;Maybe not even using the existing p2p protocol; there could be a&#xA;mining-only very-fast-block-propagation network separate from the existing&#xA;p2p network.&#xA;&#xA;Combining your optimizations with &#34;broadcast as many near-miss blocks as&#xA;bandwidth will allow&#34; on a mining backbone network should allow insanely&#xA;fast propagation of most newly solved blocks.&#xA;&#xA;-- &#xA;--&#xA;Gavin Andresen&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140717/16478b5f/attachment.html&gt;</html></oembed>