Skip to content
sealed-lattice

Selected direction

verify direct encrypted ballots

  1. Install sealed-lattice.
  2. Use the current verification helpers for development and integration work.
  3. Track the direct encrypted ballot path: proof, aggregation, replay, finality, and target decryption.
  4. Keep production election use out of scope until the complete direct path is implemented, measured, audited, and certified.
Runtime Node and browsers ES modules with bundled WASM verification
Current direction direct encrypted ballots BGV ballots, public aggregation, mobile replay
Package sealed-lattice One supported npm import path
Status not production-audited Use for development and verification tooling

sealed-lattice

Direct BGV-encrypted ballot direction for mobile verification.
Get started Browse the API reference Read safety boundaries

Selected direction

The active construction is direct BGV-encrypted ballots, public ciphertext aggregation, deterministic mobile evaluator replay, target finality, and target-bound threshold decryption.

Direct encrypted ballot path

Each voter publishes one encrypted ballot. Verification must check the ballot proof, select the first valid ballot per voter, and recompute the encrypted ballot aggregate from public ciphertexts.

The evaluator is checked by deterministic mobile replay. Only the finalized and replay-matched C_target can be decrypted.

Current limits

The direct proof, aggregation, and browser evidence are internal development evidence. They are not supported-phone evidence, production readiness, or a complete public voting API.

Ballot proof soundness, zero-knowledge accounting, public proof transport, sparse target projection, mobile replay, and target-bound decryption remain open.

Use the package

Start with installation and the public root import. Complete voting entry points remain unavailable until the direct path is implemented and verified.

  1. Install the package. Use npm install sealed-lattice or pnpm add sealed-lattice.
  2. Import from the root. Use sealed-lattice for the supported public API.
  3. Verify current public evidence. Use the current helpers for development verification and package integration.
  4. Keep the current limits explicit. Ballot generation, casting, aggregation, evaluator replay, target-bound decryption, and result release are not complete public APIs yet.

Read next

Use the guides and generated reference to confirm the current package behavior before integrating it.

Get started Install the package and understand the current direct-path boundary.
API reference Browse the generated reference for exported functions and types.
Security and non-goals Read what the current package does and does not claim.
Development workflow Run the local checks, docs build, browser tests, and package smoke tests.