{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-05-08\n📝 Original message:\u003e\n\u003e  * Though there are many proposals floating around which could\n\u003e significantly decrease block propagation latency, none of them are\n\u003e implemented today.\n\n\nWith a 20mb cap, miners still have the option of the soft limit.\n\nI would actually be quite surprised if there were no point along the road\nfrom 1mb to 20mb where miners felt a need to throttle their block sizes\nartificially, for the exact reason you point out: propagation delays.\n\nBut we don't *need* to have fancy protocol upgrades implemented right now.\nAll we need is to demolish one bottleneck (the hard cap) so we can then\nmove on and demolish the next one (whatever that is, probably faster\npropagation). Scaling is a series of walls we punch through as we encounter\nthem. One down, onto the next. We don't have to tackle them all\nsimultaneously.\n\nFWIW I don't think the GFW just triggers packet loss, these days. It's\nblocked port 8333 entirely.\n\n * I'd very much like to see someone working on better scaling\n\u003e technology ... I know StrawPay is working on development,\n\u003e\n\nSo this request is already satisfied, isn't it? As you point out, expecting\nmore at this stage in development is unreasonable, there's nothing for\nanyone to experiment with or commit to.\n\nThey have code here, by the way:\n\n   https://github.com/strawpay\n\nYou can find their fork of MultiBit HD, their implementation library, etc.\nThey've contributed patches and improvements to the payment channels code\nwe wrote.\n\n\n\u003e  * I'd like to see some better conclusions to the discussion around\n\u003e long-term incentives within the system.\n\u003e\n\nWhat are your thoughts on using assurance contracts to fund network\nsecurity?\n\nI don't *know* if hashing assurance contracts (HACs) will work. But I don't\nknow they won't work either. And right now I'm pretty sure that plain old\nfee pressure won't work. Demand doesn't outstrip supply forever - people\nfind substitutes.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150508/431f2412/attachment.html\u003e"}