From: Isidor Zeuner <cryptocurrencies@quidecco.de>
To: Ross Nicoll <jrn@jrn.me.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
References: <54BD7024.5070008@jrn.me.uk>
	<CANEZrP3ZdFcQsP+EWgTYQDccFZbrZFTk+xi-YdWPCJzMRH79pA@mail.gmail.com>
In-Reply-To: <54BD7024.5070008@jrn.me.uk>
Message-Id: <20150124131934.C9E6FE2A9B0@quidecco.de>
Date: Sat, 24 Jan 2015 14:19:34 +0100 (CET)
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for
 encoding?
Precedence: list

> For what it's worth, there was consideration of replacing protocol
> buffers when modifying BIP70 to function with the altcoin I work on
> (changes were required anyway in eliminate any risk that payment
> requests could not be accidentally applied to the wrong blockchain).

Why not serialize some kind of blockchain identifier with the
messages? Arbitrarily deviating from a given design choice just for
the sake of doing it differently may serve the goal of creating more
overall code diversity, but would not necessarily serve the quality of
the blockchain network where it is done for.

Best regards,

Isidor