{"type":"rich","version":"1.0","author_name":"npub1c6ytpr5fshkjp2hptfqrvfxy6qkkcgre9fv9va8qyq7h4fs03ehs4fz7ln","author_url":"https://nostr.ae/npub1c6ytpr5fshkjp2hptfqrvfxy6qkkcgre9fv9va8qyq7h4fs03ehs4fz7ln","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-06-22\n📝 Original message:Gavin,\n\nin 2022 your proposal (BIP as well as code) crosses the 32MB maximum\nmessage size limit. In order to avoid deployment of code that deterministically\nfails fatally in 2022, I'd propose to stop the doublings at 32MB for now and fix\nthe message size limit in the mean time. Since the message size fix requires\na 2nd hard fork anyway, your current 8GB limit could be re-instateted in that\n2nd fork as well. Even if you disagree, I'd suggest to address the topic in the BIP.\n\nbest regards,\nMartin"}