@mackoj no, I hadn't heard of that before. Looks especially promising as the README says it even supports iOS. I would be very interested to see a proof of concept Swift package based on this. Even if it's not something NIO ends up using, this could be a nice alternative to something like vapor/crypto that relies on libssl installation.
libsodium is great. However, it is worth bearing in mind that it has a reduced feature set that mean that for a number of users it is unable to support their needs.
In general, if users are building a system that requires custom cryptographic infrastructure, my strong recommendation is to just pick up libsodium and use whatever it provides for that purpose. However, as a general-purpose cryptographic library it is just too restricted.
For example, libsodium provides the following symmetric cipher constructions:
AES256-GCM
ChaCha20 (including XChaCha and IETF variants, both separately and combined with Poly1305 as an AEAD construction)
Salsa20 (including XSalsa, not available as an AEAD construction)
That's it. No AES128, no AES modes other than GCM. For signatures, it provides Ed25519. For cryptographic hashing it provides BLAKE2b, SHA256, and SHA512: that's it.
In general, if you don't have a specific scheme you have to interop with, libsodium provides great constructions. Sadly it just can't be a solution to a lot of problems.