[bisq-network/bisq] Serialisation format for Bisq 2 (Misq) (Discussion #5927)

Alva Swanson notifications at github.com
Sun Dec 19 14:38:10 CET 2021


I looked at all the mentioned ideas. The most flexible approach would be to create a custom TLV format, but we do not have the required resources, as you said. From the others, Cap'n Proto looks the most promising, but I would still prefer Protocol Buffers. Deserialization bugs usually lead to arbitrary code execution. One of these in the wire format (network layer) would be disastrous. In my opinion, we should select Protocol Buffers even if it's not the fastest one. But please keep in mind that I am probably biased because I have only worked with Protocol Buffers so far.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5927#discussioncomment-1843240
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/bisq/repo-discussions/5927/comments/1843240 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211219/a254e326/attachment.htm>


More information about the bisq-github mailing list