{"type":"rich","version":"1.0","author_name":"npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","author_url":"https://nostr.ae/npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-07-17\n📝 Original message:A couple of half-baked thoughts:\n\nOn Thu, Jul 17, 2014 at 5:35 PM, Kaz Wesley \u003ckeziahw at gmail.com\u003e wrote:\n\n\u003e If there's support for this proposal, I can begin working on the specific\n\u003e implementation details, such as the bloom filters, message format, and\n\u003e capability advertisment, and draft a BIP once I have a concrete proposal\n\u003e for\n\u003e what those would look like and a corresponding precise cost/benefit\n\u003e analysis.\n\u003e\n\nI'd encourage you to code up a prototype first (or at the same time), in\nwhatever programming language / networking library you're most familiar\nwith.\n\nMaybe not even using the existing p2p protocol; there could be a\nmining-only very-fast-block-propagation network separate from the existing\np2p network.\n\nCombining your optimizations with \"broadcast as many near-miss blocks as\nbandwidth will allow\" on a mining backbone network should allow insanely\nfast propagation of most newly solved blocks.\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140717/16478b5f/attachment.html\u003e"}
