<oembed><type>rich</type><version>1.0</version><author_name>npub1c6ytpr5fshkjp2hptfqrvfxy6qkkcgre9fv9va8qyq7h4fs03ehs4fz7ln</author_name><author_url>https://nostr.ae/npub1c6ytpr5fshkjp2hptfqrvfxy6qkkcgre9fv9va8qyq7h4fs03ehs4fz7ln</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-06-22&#xA;📝 Original message:Gavin,&#xA;&#xA;in 2022 your proposal (BIP as well as code) crosses the 32MB maximum&#xA;message size limit. In order to avoid deployment of code that deterministically&#xA;fails fatally in 2022, I&#39;d propose to stop the doublings at 32MB for now and fix&#xA;the message size limit in the mean time. Since the message size fix requires&#xA;a 2nd hard fork anyway, your current 8GB limit could be re-instateted in that&#xA;2nd fork as well. Even if you disagree, I&#39;d suggest to address the topic in the BIP.&#xA;&#xA;best regards,&#xA;Martin</html></oembed>