{"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:2012-09-10\n📝 Original message:I actually implemented parts of the header+ v\u003ctx\u003e stuff in a branch with\nmy bloom filter stuff, you can see it here:\nhttps://github.com/TheBlueMatt/bitcoin/commits/bloom%2Brelayblock\nIts pretty stupid and would be pretty easy to DoS/get it stuck/etc, but\nin theory it works.  I don't see much reason why we'd need anything\nsignificantly more complicated, but maybe there is a use-case I'm\nmissing?\n\nMatt\n\nOn Mon, 2012-09-10 at 11:14 -0400, Gregory Maxwell wrote:\n\u003e On Mon, Sep 10, 2012 at 11:07 AM, Matthew Mitchell\n\u003e \u003cmatthewmitchell at godofgod.co.uk\u003e wrote:\n\u003e \u003e Here is a BIP draft for improving the block relaying and validation so that\n\u003e \u003e it can be done in parallel and so that redundancy can be removed. This\n\u003e \u003e becomes more beneficial the larger the block sizes are.\n\u003e \u003e\n\u003e \u003e https://en.bitcoin.it/wiki/User:MatthewLM/ImprovedBlockRelayingProposal\n\u003e \n\u003e Why does this focus on actually sending the hash tree?  The block\n\u003e header + transaction list + transactions a node doesn't already know\n\u003e (often just the coinbase) is enough."}