Expand more on choice of serde backend

key-share/src/lib.rs

@@ -97,9 +97,12 @@ use serde_with::As;
 /// It's unlikely, but at some point, we might introduce a breaking change into the serialization format. In this case,
 /// we'll announce it and publish the migration instructions.
 ///
-/// Not every serde backend is supported. We strongly advise using either [`serde_json`](https://docs.rs/serde_json/),
-/// if verbose/human-readable format is needed, or [`ciborium`](https://docs.rs/ciborium/latest/ciborium/), if you'd
-/// like to opt for binary format. Other serialization backends are not tested and disadvised to use.
+/// Not every serde backend supports features that we use to ensure backwards compatibility. We require that field names
+/// are being serialized, that helps us adding new fields as the library grows. We strongly advise using either
+/// [`serde_json`](https://docs.rs/serde_json/), if verbose/human-readable format is needed, or
+/// [`ciborium`](https://docs.rs/ciborium/latest/ciborium/), if you'd like to opt for binary format. Other serialization
+/// backends are not tested and may not work or stop working at some point (like [bincode](https://github.com/dfns/cggmp21/issues/89) did)
+/// or be not backwards compatible between certain versions.
 ///
 /// If you need the smallest size of serialized key share, we advise implementing serialization manually (all fields of
 /// the key share are public!).