Binary Serialization Formats

Sounds really like you used them for the wrong use case. If you are in need of a binary compact serialization, they are not prefect (is there any) but fair enough.

it's a proprietary binary serialization. However nothing revolutionary, just comparable to thrift and protobuf.

Why do we need more random serialization formats?

Why bencoding and not BSON or CBOR or any of the other serialization options?

I'm not sure why ASN.1 isn't more popular for a zero-copy encoding system

Does your protocol provide any advantages over bincode?

Why reinvent binary serialization when you could use ASN.1, or any of the thousand binary serialization formats that pre-date protobufs?

You may want to take a look at Protocol Buffers or the new Ion format by Amazon; the latter can seamlessly switch between binary and human-readable.

I created a binary serialization format and library that is comparable to json but binary. It uses 1-byte tags to give type information, which often already contains the value (in case of 0,1,true,false,null,empty string, empty list, empty object, single letter string or one of the last 32 interned strings) very similarly to msgpack. But it has the advantage, that strings are interned, which does about the same for performance as a runtime schema-based thing like Avro, but is more generic. Also,

Check out MessagePack.https://msgpack.org/