Counts you can check
Each night, BhuMat publishes a short fingerprint of that day's counts in a public GitHub repository. This page explains how it works. BhuMat is in its test phase until 14 August 2027, so these seals cover test data.
How a seal works
Count
Each night, BhuMat counts that day's polls, LokMat votes, JanMat ballots and JanMat participation receipts.
Fingerprint
Those counts are turned into a short fingerprint, called a seal. Each seal also lists the previous seal, so the seals are linked in order.
Publish
The seal is saved as a file in a public GitHub repository named bhumat-seals, so anyone can read it.
Check
If past counts were changed later, the fingerprint would no longer match the published one, so the change could be detected.
What is in a seal, and what is not
What a seal file holds
The day, the number of polls, LokMat votes, JanMat ballots and JanMat receipts, the seal itself, the previous seal, and the version of the code that made it.
What it does not hold
It holds counts only. It does not show who voted or what anyone chose.
What a seal cannot do
A seal helps show that past counts were not quietly changed. It does not prove that every vote came from a real person, and no system is perfectly secret or perfectly safe. The process is still being refined during the test phase.
Check your own vote
After a LokMat vote you get a short receipt code. On the Proof page in the app, enter it to see your vote in the nightly count. Your name is never shown.