2007 Mock-Election Website

Timeline of Punchscan Election Procedures

Election Specification
July 11th, 2007		 The ballot template is created. The number of contests and candidates as well as the type of race (first past the post, etc) is specified (ElectionSpec). Ballot Template [PDF]
ElectionSpec.xml
Meeting One
Commitments to Punchboard
July 11th, 2007		 The number of ballots to create and additional details are specified (MeetingOneIn). The Punchboard is created from trustees passwords. Commitments to the Punchboard are posted (MeetingOneOut). MeetingOneIn.xml
MeetingOneOut.xml
Meeting Two
Pre-Election Audit Challenge
July 12th, 2007
(End of Day)		 At the end of the day, the stock market was sampled to randomly choose ballot serial numbers to be unsealed for the pre-election audit (Meeting2In). Meeting Two of the trustees is held, their passwords recreate the Punchboard and the challenged ballots are unsealed and published (Meeting2Out). MeetingTwoIn.xml
MeetingTwoOut.xml
Pre-Election Audit
July 12-18th, 2007 		The data revealed during Meeting Two may independently verified (i.e. audited) using the Audit Tool. See Chapters 2 and 3 of the VoComp submission for more details about the pre-election audit.

Instructions:

  1. Download the audit data to your computer: [MeetingOneIn.xml, MeetingOneOut.xml, MeetingTwoIn.xml, MeetingTwoOut.xml]
  2. Run the online audit tool.
  3. When prompted, specify the path to the aforementioned audit data files.
  4. Select "Pre-Election Audit"
  5. After a moment, the auditor will give you feedback about the audit. If the audit was successful (all commitments checked out, etc) the audit tool will report "the audit was successful." If the commitments did not check out, it will indicate so. If interested, try changing the commitments in MeetingOneIn.xml and see if the auditor detects it.
  6. If you encounter an error such as "illegal key size or default parameters," you may need to update your Java crypto extension.
 Audit Tool
Online Application
[Source Code]
Voting
July 16th, 2007		 Voters cast their votes.
Meeting Three
July 16th, 2007
(End of Day)		 Once the polls close on voting day, all (encrypted) ballots cast during the voting period are assembled (Meeting3In). The trustees meet for the third time, mix and decrypt the ballots yielding the election results (Meeting3Out). The results of the election are tallied and posted. MeetingThreeIn
MeetingThreeOut
Online Receipt Check
July 16-18th, 2007		 Once the results have been posted, voters may look up their ballot receipt online using the receipt checker to verify that what they hold in their hand (their ballot receipt) matches what's being shown on screen (i.e. what was used in the tally). Receipt Checker
Meeting Four July 17th, 2007
(End of Day) 		At the end of the day, the stock market is sampled to randomly choose one half of the decryption transformation (either left or right) to be revealed for each ballot (Meeting4In). Meeting Four of the trustees is held, their passwords recreate the Punchboard and the challenged decryption transformation are unsealed and published (Meeting4Out). MeetingFourIn
MeetingFourOut
Post-Election Audit
July 17-18th, 2007 		The data revealed during meeting four may be independently verified (i.e. audited) using the Audit Tool. See Chapters 2 and 3 of the VoComp submission for more details about the post-election audit. Audit Tool
Online Application
[Source Code]

punchscan.org - 2007