{"type":"rich","version":"1.0","title":"William Casarin [ARCHIVE] wrote","author_name":"William Casarin [ARCHIVE] (npub1d7…93exj)","author_url":"https://yabu.me/npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exj","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2018-06-26\n📝 Original message:matejcik via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e writes:\n\n\u003e BIP174 is a ad-hoc format, simple to parse by hand; but that results\n\u003e in _having to_ parse it by hand. In contrast, protobuf has a huge\n\u003e collection of implementations that will do the job of sorting record\n\u003e types into relevant struct fields, proper delimiting of records, etc.\n\nseems a bit overkill for how simple the format is, and pulling in a\nlarge dependency just for this is a bit silly. Although making it\nprotobuf-compatible is an interesting idea, but I fear would be more\nwork than is worth? I haven't looked closed enough at the protobuf\nencoding to be sure.\n\n\u003e ...while at the same time, implementing \"protobuf-based-BIP174\" by\n\u003e hand is roughly equally difficult as implementing the current BIP174.\n\nas a data point, I was able to build a simple serializer[1] in about an\nafternoon. I would much prefer to use this lib in say, clightning (my\noriginal goal), without having to have the larger protobuf dependency.\n\nCheers,\n\n[1] https://github.com/jb55/libpsbt\n\n\n--\nhttps://jb55.com"}