Closed davxy closed 1 year ago
I currently require this for a hack I crufted up.
We need to have access to a Vec version of ThinVrfSignature (i.e. without the generic) and methods (i.e. sign_thin_vrf_vec).
Vec
ThinVrfSignature
If is ok for you I can easily prepare a PR to do that.
In my code I had to re-define the VrfSignature with something like:
VrfSignature
struct VrfSignature { proof: VrfProof, preout: Box<[bandersnatch_vrfs::VrfPreOut]>, }
I prefer to not directly include any other dependency. Thus would be nice to expose the serialization traits directly from here.
An alternative, e.g. if we want to give some defaults, we may provide to_bytes and from_bytes methods directly to the types I need to serialize.
to_bytes
from_bytes
We'll move to the type in https://github.com/w3f/ring-vrf/blob/master/dleq_vrf/src/traits.rs#L177 too I think since then you have workable traits for the keystore.
ThinVrfSignature components
I currently require this for a hack I crufted up.
We need to have access to a
Vec
version ofThinVrfSignature
(i.e. without the generic) and methods (i.e. sign_thin_vrf_vec).If is ok for you I can easily prepare a PR to do that.
In my code I had to re-define the
VrfSignature
with something like:Serialization traits
I prefer to not directly include any other dependency. Thus would be nice to expose the serialization traits directly from here.
An alternative, e.g. if we want to give some defaults, we may provide
to_bytes
andfrom_bytes
methods directly to the types I need to serialize.