schnorr_fun v0.13.0 release#249
Merged
Merged
Conversation
nickfarrow
approved these changes
May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release branch bumping
schnorr_funto v0.13.0 andsecp256kfunto v0.12.1.schnorr_fun/Cargo.toml: 0.12.0 → 0.13.0secp256kfun/Cargo.toml: 0.12.0 → 0.12.1 (only#[must_use]additions onHashAdd— non-breaking)schnorr_fundep pin:"0.12"→"0.13"(secp256kfun pin left at"0.12"since 0.12.1 satisfies)CHANGELOG.md: new## schnorr_fun v0.13.0sectionWhat's in v0.13.0
A security audit of
chilldkg(#247, #248) produced a batch of fixes and anAPI rework. Highlights — see CHANGELOG.md for the full list.
Security
Certifier::receive_certificatealways verifies signatures (fixes silent acceptance of unverified VRF certs on duplicate registration)CertifiedKeygenno longer serializable (closes attacker-chosen-gamma path throughvrf_security_check)SecretShareReceiver::finalizerejects unexpected cert-map entries (no VRF beacon pollution)receive_secret_sharevalidates share index and encryption keyAggKeygenInputandSharedKeydecoding fixedAPI breaking
Contributoris type-parameterized by role (ShareReceiver/AuxContributor); wrong-role calls become compile errors. Unifiedgen_keygen_input.verify_agg_inputis per-role; theShareReceivervariant atomically pairs the share. Incertpedpop, the share is gated behindSecretShareReceiver::finalize.cert_bytes()binds the receiver-encryption keys and aux contributor keys via the verifier's local state; coordinator-supplied keyset substitution fails certification.finalizeparameter. Both move onto the contributor atgen_keygen_inputtime.Coordinator::add_inputandmissing_fromuse aPartyenum.&'static strerrors replaced with typed enums; broad errors split into per-function variants."BIP DKG/pop message"matching the BIP DKG draft (wire-incompatible with old PoPs).