Currently, we have the following crates desirable for a new release:
Some of these cryptographic crates will be blocked on how they use dependencies from monero-oxide's FCMP++ branch themselves unpublished, but that should be manageable...
dkg-evrf would also be eligible for publication after #794.
As all these issues are rather small, I'd like to get them out of the way once blake2 0.11 is done. That would still use ff, group 0.13, so these may have short lifespans, but I'm unsure when ff, group 0.13 will come out and would like to at least take advantage of digest 0.11.
All of these are blocked by #802 which applies to all future publications.
Currently, we have the following crates desirable for a new release:
std-shimssimple-request(Remove expectation ontokiofromsimple-request#682?)flexible-transcript(blocked on ImplementZeroizeOnDropfor the output ofbuffer_ct_variableRustCrypto/traits#2353 or equivalent, and the release ofblake2 0.11)multiexpff-group-tests(blocked by Zeroizing points is tricky #799)ciphersuiteciphersuite-kp256prime-fieldshort-weierstrassdalek-ff-groupminimal-ed448embedwards25519(Choice ofembedwards25519#798?)secq256k1schnorr-signaturesdkg(blocked bydkg::Interpolation::Constantmay panic if the interpolation factor for a non-present participant is requested #685)dkg-dealer(blocked bydkg-dealerlacks tests #792)musigpedpop(despite how it's been somewhat kicked out with Move thedleqlibrary into a distinct repository #597)dkg-recovery(blocked bydkg-recoveryis untested #795)modular-frost(blocked byAlgorithms assume they're called byAlgorithmMachine#684)schnorrkelbitcoin-serai(blocked on Extend testing inbitcoin-serai#803)alloy-simple-request-transportbuild-solidity-contracts(silly, as noted in Future ofbuild-solidity-contracts#800, but a dep ofethereum-schnorr-contract)ethereum-schnorr-contractSome of these cryptographic crates will be blocked on how they use dependencies from
monero-oxide's FCMP++ branch themselves unpublished, but that should be manageable...dkg-evrfwould also be eligible for publication after #794.As all these issues are rather small, I'd like to get them out of the way once
blake2 0.11is done. That would still useff, group 0.13, so these may have short lifespans, but I'm unsure whenff, group 0.13will come out and would like to at least take advantage ofdigest 0.11.All of these are blocked by #802 which applies to all future publications.