{"type":"rich","version":"1.0","author_name":"npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","author_url":"https://nostr.ae/npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-22\n📝 Original message:On Mon, Jun 22, 2015 at 8:10 PM, Martin Schwarz \u003cmartin.schwarz at gmail.com\u003e\nwrote:\n\n\u003e Gavin,\n\u003e\n\u003e in 2022 your proposal (BIP as well as code) crosses the 32MB maximum\n\u003e message size limit. In order to avoid deployment of code that\n\u003e deterministically\n\u003e fails fatally in 2022, I'd propose to stop the doublings at 32MB for now\n\u003e and fix\n\u003e the message size limit in the mean time.\n\n\nThere is an exception in the code for \"block\" messages.\n\nhttps://github.com/gavinandresen/bitcoinxt/commit/c81898ec46e4962daf975e352931b848026fdc34#diff-7ec3c68a81efff79b6ca22ac1f1eabbaR3548\n\nThis means 2MB limit for all other messages.  \"block\" messages are limited\nto the max block size for 2 hours into the future.\n\nI think setting it to a week into the future might be better, since it is\nonly a DOS protection.  This would guarantee that message sizes are\nreasonable.  The size check would still be done anyway.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150622/2457767e/attachment.html\u003e"}