Tony Arcieri
Tony Arcieri
@baloo can you mark this as ready if you think it's past the draft stage?
In #1413 I suggested we should potentially split out the OID database into its own crate like `const-oid-db` so we can get `const-oid` to v1.0 more easily while still having...
I would mostly like to get to `const-oid` v1.0 because upgrades are extremely painful and it’s a somewhat foundational crate. I think we’re there aside from questions like this about...
Going to stick with an owned `ObjectIdentifier`. We'll see if people end up complaining about the added bloat.
For a crate name, `verifiable-random-function` would fit our naming scheme
Yes, traits from the `signature` crate could be used instead if we want. If the only thing that's really needed is a trait for `VRF_proof_to_hash`, we could potentially just add...
Since `signature` is a post-1.0 crate I think it would be nice to prove it out in a separate crate. It could eventually be merged.
FYI: the `vrf` crate seems to be getting regular updates, so I didn't attempt to contact them
When using big integers as backing storage for cryptographic keys, there are many times it can be helpful to know the bit size of the key. [Here are some real-world...
A function might be a bit more helpful, since the size can be determined at runtime: https://github.com/search?q=repo%3ARustCrypto%2FRSA+bits%28%29&type=code FWIW we’re looking at adding a runtime-selected fixed-width integer type to `crypto-bigint` for...