What Taynik receives
Reveal content during creation, and reported coordinates plus accuracy during a protected unlock check. Scan attempts may be counted for creator activity.
From ordinary camera to location-confirmed reveal.
Wormhole keeps the familiar first step—a phone camera scan—then makes the location check explicit before protected content opens.
Example arrival · Rooftop P7
01 / Camera
Carrier foundPublic scanner opens
02 / Location
Inside the cellVenue match confirmed
03 / Reveal
Four deliberate steps. No hidden jump.
The visitor always sees when camera and precise location are being requested.
- 01
Choose the place and reveal
Search an address, use your current location, or move the map pin. Wormhole shows the exact rectangular location cell before you publish a short Text or HTTPS Link reveal.
- 02
The normal camera opens the scanner
A Classic carrier looks and behaves like an ordinary scannable code. The first scan opens the public Wormhole scanner in the phone’s browser—no app install required.
- 03
One more scan confirms the carrier
The visitor taps Start scanner, allows precise location and camera access, then points at the same carrier again. A coarse first GPS fix can improve while the scanner stays open.
- 04
The browser opens the reveal
When the reported position matches the protected cell, the server releases a per-code secret and decryption completes in the visitor’s browser. Outside the cell, the same carrier stays locked.
wormhole.taynik.net/scan
One more scan
Allow precise location, start the scanner, and point at the carrier again.
Location confirmed
Opening the reveal…
The carrier is public. The reveal is place-bound.
Wormhole does not hide the scanner URL or rely on a private app. The protected layer and location check create the different outcome.
Links are shown as explicit Open buttons after unlock. Wormhole never auto-redirects or fetches an arbitrary external destination.
Reported fix · 18 m accuracyInside exact cell
Across the streetOutside · stays locked
- Cell
- P7 · Venue
- Dimensions here
- ≈114 × 153 m
- Sample latitude
- 41.8819° N
Location confirmedThe signal found you.
A rectangle, never a made-up radius.
Each code is bound to an exact geohash rectangle. Its width changes with latitude, so the creator shows the actual bounds and local dimensions before publishing.
Browser accuracy is different: it is an uncertainty radius around the reported position. Genuine-device boundary smoothing is bounded to 25 m; it does not turn the cell into a circle.
Clear boundaries make a better experience.
What Wormhole cannot prove
Who the visitor is, whether GPS was spoofed, or high-stakes attendance and safety claims. Design around those limits.
Practical questions
Before you place the first code.
Does it open from the normal phone camera?
Yes. Classic is the default carrier. The normal Camera app opens Wormhole’s public scanner, and the second scan reads the protected layer.
Can someone forward a screenshot?
They can forward or print the carrier, but the protected reveal still depends on the scanning phone reporting a position inside the chosen cell.
What if GPS is weak indoors?
Phone GPS varies around dense buildings and indoors. Choose a broader cell when needed, allow precise location, and test the finished print at the real place on current iOS and Android devices.
Is this proof that a specific person attended?
No. Location can be spoofed, and Wormhole does not identify the visitor. It is creative proof of place, not high-stakes proof of identity, safety, or legal presence.
Make a temporary code for this exact spot.
The guided demo uses the same image decoder and accuracy-aware location path as the production scanner.