<oembed><type>rich</type><version>1.0</version><author_name>npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef</author_name><author_url>https://nostr.ae/npub10plv6jx6pktpp5ezldnus6kj8ffg045g2kdjl78w23njrlveqy5s3pfaef</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-01-25&#xA;📝 Original message:That was essentially what we did in the end, we replaced the network&#xA;identifier (&#34;main&#34;/&#34;test&#34;) with the genesis block hash. The result is&#xA;never going to accidentally work with Bitcoin Core (nor vice-versa), but&#xA;is readily extensible to any other altcoins that want to use the&#xA;specification without requiring any sort of central registry.&#xA;&#xA;Ross&#xA;&#xA;On 24/01/15 13:19, Isidor Zeuner wrote:&#xA;&gt;&gt; For what it&#39;s worth, there was consideration of replacing protocol&#xA;&gt;&gt; buffers when modifying BIP70 to function with the altcoin I work on&#xA;&gt;&gt; (changes were required anyway in eliminate any risk that payment&#xA;&gt;&gt; requests could not be accidentally applied to the wrong blockchain).&#xA;&gt;&#xA;&gt; Why not serialize some kind of blockchain identifier with the&#xA;&gt; messages? Arbitrarily deviating from a given design choice just for&#xA;&gt; the sake of doing it differently may serve the goal of creating more&#xA;&gt; overall code diversity, but would not necessarily serve the quality of&#xA;&gt; the blockchain network where it is done for.&#xA;&gt;&#xA;&gt; Best regards,&#xA;&gt;&#xA;&gt; Isidor</html></oembed>