<oembed><type>rich</type><version>1.0</version><author_name>npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_name><author_url>https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-01-19&#xA;📝 Original message:&gt;&#xA;&gt; I&#39;m a bit confused.  It&#39;s been a long time since I looked at protobuf (and&#xA;&gt; will have to dig into it soon), but I seem to recall it doesn&#39;t have any of&#xA;&gt; the determinism properties you guys just said.&#xA;&gt;&#xA;&#xA;It&#39;s not guaranteed no, which is why we store signed sub-messages as byte&#xA;arrays instead of typed submessages. In practice though, most&#xA;implementations do seem to serialise things the same way. I recall Python&#xA;used to be an odd one out, unsure if it still is.&#xA;&#xA;OK, I guess we can boil this down more simply. BIP 70 uses protocol buffers&#xA;because I designed it and implemented the original prototype (with lots of&#xA;input from Gavin and an earlier proposal by sipa). I used protocol buffers&#xA;because, beyond all their nice properties, I used to work at Google and so&#xA;was very familiar with them.&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150119/bbd8b7d4/attachment.html&gt;</html></oembed>