Satyra trips

The problem it solves

In today's online world, fake reviews distort trust. Satyra Trips solves this by enabling users to verify their physical presence at a location before posting a review. Built on top of Satyra Protocol, Satyra Trips uses mock Proof of Presence to showcase how verified reviews can rebuild trust in travel platforms. Users can search for restaurants, hotels, attractions, and post authentic reviews after a simple verification step, ensuring every review is linked to a real visit.

This app demonstrates how Satyra Protocol can power vertical applications in travel, food, commerce, and local discovery.

Key Features:

Search and discover places

Mock "Proof of Visit" verification before reviewing

Write and publish reviews with "Verified" badges

Public view of verified reviews with timestamps and wallet IDs

Challenges we ran into

During the development of Satyra Trips, one of the core challenges was architecting a seamless verification flow that could mimic real-world location proof in a lightweight MVP. Since access to actual GPS-based cryptographic proof or zero-knowledge location attestation was out of scope for the hackathon, we had to create a believable mock Proof-of-Visit system that still reflected the spirit of the protocol. Designing this system required balancing user experience with data integrity — ensuring that even with mock data, the demo captured how verifiable reviews could look in a real deployment.

Another obstacle was integrating dynamic browser interactions with Google Maps' DOM structure. Since we envisioned this as both a standalone mini-app and a future browser extension, identifying stable UI hooks within the Google Maps interface for future real-time detection was complex. We overcame this by modularizing our code and abstracting the verification flow to a component that could work both as a web-based mini-app and a browser extension integration.

Lastly, ensuring review data integrity even in a mock environment (without backend or smart contract support) pushed us to build a lightweight frontend-first data schema that could be extended later to include decentralized storage or on-chain attestation.