Skip to content

Synchronized decryption on fhe.rs v0.6.0 alongside SS #2456

Open
3 of 8 issues completed
Open

Description

@neogiacomo

Goal

Add synchronized threshold decryption using fhe.rs v0.6.0, alongside the existing secret-shared smudging-noise (SS) protocol.

Agreed delivery boundary

  • First land the fhe.rs upgrade and SS API adaptation on main, independently of synchronized integration. Each PR must change at most 100 files, including generated files; split work into reviewable PRs as needed.
  • Select exactly one protocol per E3 through its parameter profile; derive the internal protocol enum from that profile. Preserve SS behavior and its initial single-ciphertext limit.
  • Initial synchronized support decrypts one ciphertext, using a fixed designated set of exactly T+1 parties. Proposed rule: lowest canonical T+1 IDs from the published H-roster, subject to protocol review. Aggregator failover retains that same set.
  • Reuse compatible implementation from the cryptographer's commit, including encrypted SK-share PRF-key packing (residue + bit*q). Adapt it to the v0.6.0 APIs and PRF transcript; do not import the old transcript unchanged.
  • fhe.rs owns cryptographic APIs. Interfold owns E3 authentication, circuit/proof bindings, configuration identity, durable state and orchestration.
  • Designated-set replacement/recovery and multiple synchronized ciphertext decryptions are separate design follow-ups, outside the initial delivery gate.

Existing tracking reviewed

Milestone completion

Both protocols work through their selected profiles, with cross-protocol rejection, canonical E3/party/ciphertext bindings, replay/restart coverage, real-crypto end-to-end proof verification and a reviewed compatibility/rollout plan. Upstream unit tests alone are not Interfold qualification.

Implementation and design children are linked below. Follow-up designs do not block the initial fixed-set/single-ciphertext milestone.

Initial milestone

Separate follow-up designs

Activity

  1. self-assigned this
    on Nov 9, 2026
  2. neogiacomo commented on Nov 12, 2026

    @neogiacomo
    ContributorAuthor

    Progress update (2026-11-12)

    Initial milestone: 2 of 6 done. #2459 is unblocked; no PRs are open yet for the remaining sub-issues.

    Done

    #2457: fhe.rs v0.6.0 on main with SS preserved (#2464, merged 2026-11-09)

    • fhe.rs is pinned to v0.6.0 (30cce841) across the workspace, template and guest locks; the upstream synchronized-decryption default feature is disabled.
    • SsSmudgingDecryptor replaces the removed decryption APIs, and the SS single-ciphertext limit is enforced in share calculation and C6.
    • No parameter, circuit, artifact, VK or contract changes.
    • Follow-up fix(bfv): select the C7 quorum for surplus decryption shares #2475: native reconstruction selects the same lowest-ID T+1 shares as C7 and recursive folding, so a C6 retry that yields surplus shares no longer fails.

    #2458: protocol-specific BFV profiles and configuration identities (#2481–#2489, merged 2026-11-12)

    • One protocol enum derived from the parameter profile. A synchronized insecure-64/minimum profile is defined but disabled; SS parameter tuples are unchanged.
    • A versioned configuration identity binds protocol, exact threshold and DKG parameter bytes, committee ordinal, N/T/H and statement version, so equal threshold tuples can't alias different protocols or DKG statements.
    • Each request snapshots its profile and configuration ID. Both are carried through C0–C7 proof generation, canonical keys, batch verification and recursive folding; disabled profiles are rejected before any witness or artifact access.
    • Contract and node admission require the exact profile-bound identity (crypto metadata format 2). Historical threshold-only identities stay readable for indexing only.
    • Recovery re-derives the identities before hydrating saved work and fails closed on a mismatch.
    • Breaking: storage and keyshare schema 9, sortition and node-fold recovery 2. Upgrade with zero active E3s following docs/architecture/upgrades.md#bfv-profile-cutover; mixed versions are not supported.

    Next

    Follow-up designs, not blocking the milestone: #2462 has an initial design in Notion (linked in the issue); #2463 has no activity yet.

    Open points

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ciphernodeRelated to the ciphernode packagecryptographyConcerned with cryptography

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions