Calascibetta Romain

Ok, I think it's time to take my time again on curve25519, I just talked with @samoht about this implementation (for others purposes) and I just read some comments about...

Focus on API and, like `digestif`, provide a C binding and an OCaml implementation. I need to figure out which implementation in C I will use. About `coq-fiat`, I have...

`callipyge.0.2` (implementation of curve25519 in OCaml) is just released. People are able to implement OMEMO in OCaml now 👍 !

see ocaml/opam-repository#18558

It can be interesting to implement it with `filter` to be able to transmit less objects between peers (such as only commits for instances).

Thanks, I will cut a release as soon as I can.

I don't really understand why we need to functorize this part, I mean, the only usage of such functor is the application here: https://github.com/mirage/ocaml-git/pull/441/files#diff-da0d4644201b7c89b6726ed7efd021a38cb025220a7a33159f19d6d376062dccR119-R121 The best should not be a...

> I want to experiment with reusing State in the protocol v2, which has a different definition of Capability module In that case, I would like to prefer to merge...

I can confirm that this issue exists with [`paf-le-chien`](https://github.com/dinosaure/paf-le-chien) which is a file-descriptor leak (see this issue on our `opam-mirror` unikernel: https://git.robur.io/robur/opam-mirror/issues/5). I first thought about the need for a...

So the PR seems fine as is, I need to go to some details but these commits should be proposed into another PR: 09a28e4 f24b46e & c65712c