Skip to content

spike: re-evaluate BBS (bbs-2023) under the documented gate — CFRG RFC + W3C REC + a bindable pairing library #73

Description

@luisgf

Value/Effort: medium / M for the re-evaluation; an implementation would be XL. The ROADMAP defers BBS behind an explicit gate: the CFRG drafts reaching RFC (bbs-signatures is at draft-10, Jan 2026, with the blind-BBS and per-verifier-linkability companions behind it), vc-di-bbs reaching Recommendation (Candidate Recommendation Draft 7 Apr 2026; charter target Apr 2027), and a trustworthy pairing library usable from Python (today: Rust pairing_crypto / zkryptium / docknetwork-crypto, none with Python bindings — a PyO3/maturin binding would be the entry).

Scope: when the gate conditions move, re-run the assessment and either (a) design the [bbs] extra (verify-first, unlinkable selective disclosure) or (b) re-defer with dated reasons in the ROADMAP. This issue is the tripwire so the decision is revisited deliberately, not by accident.

Metadata

Metadata

Assignees

No one assigned

    Labels

    spec-conformanceStandards coverage / conformance vectorsspikeTime-boxed investigation ending in a scope decision (ADR)

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions