I propose adding optional hash algorithm selection to sodium_crypto_kx_* functions, allowing developers to choose between BLAKE2b (current default), SHA-256, or other standardized KDFs. This would improve interoperability with systems like Web Crypto API that use different key derivation approaches, while maintaining backward compatibility. A parameter like $options['hash'] could specify the algorithm, making Libsodium more flexible for cross-platform cryptography without sacrificing security.