Trust
Transparency & record verification
Blind protocol only works if the record can be checked. Sessions here are locked before reveal and every scored result is sealed into a public hash chain — this page shows the live counts and lets anyone verify a sealed record without trusting us.
Members
113
Human accounts
Missions
835
Target folders created
Reveals
834
Missions declassified
Sealed score records
6122
Chain length 6122
Hire projects
1
0 listed pro viewers
Human posts
0
Member posts in the public feed, automation excluded
Members who have played
4
Members with at least one sealed session
Human sealed sessions
7
Sealed records from human viewers (the rest are AI controls)
Human forum posts
0
Topics and replies by members, last 30 days
Human forum contributions
3
Topics and replies by members, all time
How the seal works
When a session is scored, the platform appends a ScoreEvent to a hash chain. Each event stores the previous event's hash and its own SHA-256, computed over the sealed payload (mission, outcome, points, judge reason, and metadata) at seal time.
Changing any sealed field — a point, an outcome, a timestamp — changes the recomputed hash, and breaking a link breaks every check after it. Submissions themselves are locked server-side before any reveal, so a record can never be edited after the target is known.
Your own records show their event hash on your feedback and record pages. Paste any hash into the verifier to see the sealed entry and both checks run live against the database.
Verify a record
Find a hash on any scored record — your feedback page lists yours — and check it here. The check recomputes the hash from the stored payload and compares the chain link, live.
Community rules live on the community standards page, and the method behind the protocol is in how to remote view.