Skip to SEVA content
Pre-release

Assessment only. Not yet suitable for any live election. Deployment and operation require authorized SparkGlim Security and Technical Teams.

Pre-release · source-reviewed design

Make the record inspectable.

How sealed configuration, hash-linked records, signatures and replay controls support SEVA’s intended integrity model.

Integrity requires a trustworthy record and a way to challenge it. SEVA has source-level controls for preserving that record; complete verification and trusted operational anchors still need to be established.

A sealed configuration reference

Election configuration has a canonical hash, and ballot handlers compare requests with the stored seal. This can identify stale configuration. It does not replace tests proving that every contest rule, lifecycle transition and authorized ballot style is enforced across the complete workflow.

Linked, append-only records

Audit and bulletin components link entries with SHA-256. Database rules reject ordinary updates and deletions on ballot records. These mechanisms support tamper evidence relative to trusted checkpoints; they do not make a privileged deployment impossible to alter or create a public-consensus ledger.

Single-use token accounting

The cast transaction records a token-derived nullifier with a unique election key before appending the ballot. Reusing that spent token is rejected. Unique-token control must be paired with tested voter eligibility, concurrent issuance, replacement-card policy and staff procedures before claiming one person, one vote.

Signed artifacts and independent checks

Ed25519 signing and manifest-verification components identify signed artifacts. They do not establish that a signed tally is correct. The integrated Go verifier still lacks complete ballot-proof and tally checks; independently trusted publication, proof validation and reconciliation are required before stronger integrity claims.

Request consultation

Scope before commitment

Assessment only. Not yet suitable for any live election. Deployment and operation require authorized SparkGlim Security and Technical Teams.

Country context guides the consultation. It does not establish jurisdictional approval, regulatory compliance or product availability.