Bake in VRF functionality (eliminating support for disabling VRFs)
kevinlewi opened this issue · comments
The default behavior is to enable VRFs. But this causes funky logic which could ideally be simplified. For instance, here, a client is supposed to pass a VRF public key and AkdLabel if VRF is enabled, but if VRF is disabled, then these two fields can just be empty.
Let's simplify this by not allowing for consumers of the library to disable VRFs (since I think it should be considered a core privacy feature anyway). This would involve getting rid of the VRF feature (so that it can't be disabled).