prost VS bitbox02-firmware

The benchmark is not comparing apples to apples.

prost is the most widely used Protobuf implementation in Rust, maintained by the Tokio organization. prost generates structs and serialization/deserialization code for you.

easyproto according to GitHib Search is used only by two projects. easyproto provides primitives for serializing and deserializing Protobuf, and requires hand writing code to do both.

A fair comparison would be prost vs google.golang.org/protobuf, or easyproto vs parts of quick-protobuf.

In most cases you can make Go as fast as Rust, but from my experience writing performance-sensitive code in Go requires significantly larger time investment and overall requires deeper language expertise. Pebble (RocksDB replacement in Go by CockroachDB) is a good example of this, the codebase is littered with hand-inlined[1] functions, hand-unrolled loops and it's not[2] even using Go memory management for performance critical parts, it's using the C memory allocator and manual memory management.

[prost]: https://github.com/tokio-rs/prost

You could use Protocol buffers to define a message type, then use prost to generate encoding/decoding code for that type.

Thanks but that doesn't seems to support `json_mapping` , there is a draft available but not sure when it will get merged https://github.com/tokio-rs/prost/pull/558

Hi r/rust, I have a question regarding tonic-build (or prost-build).

Currently, I'm making some stuff by using protobuf via prost. Maybe you know, protobuf v3 treats all fields as optional, so it is pain to unwrap every nested field.

Note: one additional key feature currently missing from Prost is Proto2 extensions.

I'm looking at this, you can see a comparison when you scroll down: https://bitbox.swiss/bitbox02/

Bitbox02 - https://bitbox.swiss/bitbox02/

I also implemented BIP-85 just recently.

Here's the repository for the firmware of BitBox02: https://github.com/digitalbitbox/bitbox02-firmware

Complementary to that, you can also download the official release from https://github.com/digitalbitbox/bitbox02-firmware/releases and install it manually using command line tools, after verifying it is legit by reproducing it. Or build the app yourself after checking that the bundled firmware is correct.

At the bottom of this page, they concisely explain what they mean for each entry in the table and why they give that specific score. For this in particular, they consider the setup easier because you can backup to an (offline) SD card instead of writing it down manually.

I decided on this: https://shiftcrypto.ch/bitbox02/

There you go: https://github.com/digitalbitbox/bitbox02-firmware/pull/1069

The firmware code is open source and can be found here. The official releases are built from this code in a reproducible fashion. The community is able to verify that currently the only two ways of exporting the seed are via the 24 words displayed on the BitBox02 screen or onto a microSD card inserted directly into the device. If there are other unintended ways, it might be a bug, and should be sent to us as part of our bug bounty program.