<oembed><type>rich</type><version>1.0</version><author_name>npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_name><author_url>https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2012-09-10&#xA;📝 Original message:On Monday, September 10, 2012 3:07:52 PM Matthew Mitchell wrote:&#xA;&gt; Here is a BIP draft for improving the block relaying and validation so that&#xA;&gt; it can be done in parallel and so that redundancy can be removed. This&#xA;&gt; becomes more beneficial the larger the block sizes are.&#xA;&gt; &#xA;&gt; https://en.bitcoin.it/wiki/User:MatthewLM/ImprovedBlockRelayingProposal&#xA;&#xA;Most of the problem with block propagation lies in implementation, not &#xA;protocol... Distributing missing transaction on an as-needed basis is a &#xA;possible improvement at the protocol level, but there hasn&#39;t (AFAIK) been any &#xA;research into whether the little benefit outweighs the cost yet. In any case, &#xA;I don&#39;t see why 6 new messages are needed instead of simply adding a single &#xA;new type to getinv?</html></oembed>