Check a vote count yourself

A few minutes after each hour ends, Durbar seals that hour's vote records with a hash: a fingerprint of the records that includes the hour before. Changing any earlier record changes every hash after it. The nominee list is sealed in too, with every change made after voting opened.

Check it

1. 1Open the contest's public page and choose Verify the count.
2. 2Each hour that had votes is listed with its Hash, its Records and its Net votes, with every void and its reason. Quiet hours are sealed too, but left off the list.
3. 3Choose Check the chain in this browser. Your browser works out every hash again. Once the count is public, it also adds up each nominee's votes beside the published count.
4. 4To check with your own tools, choose Download the records.

The seals are public from the start. The records themselves are published once the count is public, so a contest that shows results only at the close publishes them then. Until then the page gives the number of hours and the latest hash, and the download holds every hash. A private count publishes hashes alone, but voids and reversals are always public, with their vote numbers.

Anchors

A chain alone can be rewritten and sealed again by someone with full control of Durbar's systems. So each new hash is also signed, added to a public feed, and emailed to whoever can publish the contest, for each hour that held records. Keep those emails: a copy outside Durbar is what shows a later rewrite.

What this can't tell you

• Who voted or who paid, or that each vote came from a different person.
• That every vote made it in, or that the votes were honest.
• Anything about a rewrite by someone who holds both the signing key and the feed, if nobody kept a copy. No outside timestamping service holds these yet.