Verified attendanceVerified attendanceAugust 22, 2026
One moment — every entry is being re-checked here, in your browser.
Download the record and choose it in the box below to compare it with this page, or run the checker on your own computer. The record contains no personal information, and the checker never contacts VenuScan.
The checker is a small script for Node.js. In a terminal, in the folder where you saved both files:
It will say the entries’ contents were not checked — that is expected for this public record, which holds only the hashes. It confirms the entries are complete and in order and match the published root; the organiser’s full export, run the same way, also checks the contents.
| # | How | Entry hash | Time |
|---|---|---|---|
| 1 | Scanned | 347824c41caad9e5cb911261… | 7:09 p.m. |
| 2 | Scanned | cbcc02cf4ef7efdb92d3ae52… | 6:38 p.m. |
| 3 | Scanned | c4f427ea94d6bc9dea68d0f7… | 7:35 p.m. |
| 4 | Scanned | dd7eafbb16dad41e0293f284… | 7:04 p.m. |
| 5 | Scanned | b546c2dc51e7e8496c369478… | 6:33 p.m. |
| 6 | Scanned | 44e7545c289cc73f9a114b5a… | 7:30 p.m. |
| 7 | Scanned | 70066f63e344d426f08e9fb9… | 6:59 p.m. |
| 8 | Scanned | 2929ea6179e210099f02a547… | 6:28 p.m. |
| 9 | Scanned | 0cbac341392a3f9f2d900f95… | 7:25 p.m. |
| 10 | Scanned | e29a105718ff61e073bdbf0c… | 6:54 p.m. |
| 11 | Scanned | f01e54d36f4d95665e523fad… | 6:23 p.m. |
| 12 | Scanned | b3d0eaafd0fe9210aea72202… | 7:20 p.m. |
Showing 12 of 102. All 102 are embedded in this page and included in the check above.
Times are shown in the event’s local time (America/Toronto). A refused scan is listed only when the code belonged to a known ticket; a code that matched nothing is not recorded here. A refused scan does not mean the person was turned away — they may have been admitted on a later scan, which is counted above.
It proves that no entry was reordered, removed or slipped in. Each entry’s hash includes the one before it, so changing any entry breaks every hash after it, and the published root above stops matching.
On its own it does not prove that the details inside an entry — including how each person was counted — were never edited. This page is sent only the hashes, never the underlying fields; that keeps it free of personal data, and it is also the limit of what it can check. The number of entries and their order are proven here; the split into scanned tickets, staff check-ins and refused scans is read from the record as stored, and compared with the split recorded when the event closed. The event organiser’s full audit export, run through the same checker, rebuilds every hash from the field values themselves and fails if any one of them was changed.
It does not prove that a person walked through a door. It shows what the door system recorded at the time — which is why each entry carries how admission happened, and why “let in by staff” is counted separately from scanned tickets.
It is a record, not a vault. Someone with direct access to the database could still change entries, and could even redo the sums so the chain adds up again. What they cannot do is make a changed record produce the root that was already published on August 30, 2026 — so keep a copy of that root, or of the record download, and any later change shows up as a mismatch against your copy.
This page contains no personal information. Ticket holders appear in the record only as a keyed pseudonym, which is never published here and becomes permanently unresolvable if the event’s key is destroyed under a privacy request.