Skip to content

Integrate fixed-set single-ciphertext synchronized decryption runtime #2460

Open

Description

@neogiacomo

Parent: #2456

Depends on: #2458, #2459, #2050

Scope

Dispatch through the E3 profile to SsSmudgingDecryptor or SynchronizedDecryptor. Initial synchronized execution supports one ciphertext and exactly T+1 designated parties. Proposed deterministic selection is the lowest canonical T+1 IDs of the published H-roster; ratify the rule in protocol review and use one owner for it.

  • Use v0.6.0's native power-basis ciphertext PRF context, canonical ordered set and directed keys. Bind Interfold messages/proofs separately to the canonical E3 domain, signer/party, profile, ciphertext and phase; the upstream PRF context is not E3 authentication.
  • Generate locally weighted synchronized shares with fresh local noise for an authorized decryption. Sum the complete matching set without reapplying Lagrange weights and add c0 once.
  • Persist enough context and generated-share state for replay/restart and specify idempotent retransmission/retry behavior; do not accidentally resample and emit additional shares after recovery.
  • Aggregator failover changes the coordinator, not the designated decryptors. Reject mixed sets, substituted parties, duplicate contributions, wrong ciphertext/level and cross-E3/profile shares.
  • If a designated party is unavailable, follow an explicit bounded failure/timeout policy; do not silently substitute another party. Reject a second ciphertext under the initial milestone.

Acceptance criteria

  • Fixed-set synchronized execution completes through the current actor/effect and canonical-key admission boundaries with feat(circuits): prove synchronized threshold decryption in C6/C7 #2050 proofs.
  • Tests cover all designated shares, missing/unauthorized/duplicate/mixed-context shares, aggregator failover with unchanged set, restart and retransmission.
  • Existing SS single-ciphertext execution still works through its profile.
  • The lifecycle and host-side noise/retry policy are documented and reviewed; ZK range checks are not represented as proofs of sampling freshness.

Delivery: keep each PR at 100 changed files or fewer, including generated artifacts.

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