Oasis is delivered through the web browser on a participant's own device, so the primary hardware requirement is a phone with a camera, GPS, and a modern browser. Physical hardware enters at the site end, where installed stations can anchor a hunt to a specific object or place.
01Participant devices
The platform is documented as a web application using WebXR and browser-based AR alongside a mapping layer, which means the capability set the participant's device must supply is straightforward: satellite positioning accurate enough to satisfy a geofence, a rear camera for AR overlay and photo validation, motion sensors for AR tracking, and a network connection good enough to load assets in the field.
That last point is the one most often underestimated when planning an activation. A hunt location with poor cellular coverage will fail on asset delivery long before it fails on anything clever, and dense urban environments degrade GPS accuracy in ways that interact badly with tight geofences. Both are site-survey problems rather than platform problems, and both are cheaper to find during scouting than on launch day.
DigiFX has not published a supported-device matrix. Until it does, treat device support as something to confirm per engagement rather than to assume.
02Site hardware and relic stations
The ecosystem's NFC and terminal documentation describes a networked terminal cluster deployment model, and names RelicVerse stations as one of its use cases alongside multi-location deployments and merchant networks. In that model multiple terminals share configuration, are monitored centrally, coordinate rate limiting, and can share an offline queue.
The tag model in that documentation is worth understanding because it constrains what a physical relic can be. Tags are treated as secure identifiers only. They do not store balances or secrets. A tag links a physical artefact, described as a card, coin, puzzle item, or relic badge, to a wallet in the ledger, and the authoritative state stays server-side. Practically, that means a stolen or cloned tag does not carry value with it, which is the correct design for objects left in public places.
The reader hardware named in that documentation targets PC/SC-compatible devices, with a USB reader as the primary development unit, and supports common tag families. Terminals are described as running as a background service on a small computer such as a single-board machine, workstation, or kiosk, with a standalone variant suited to puzzle labs, event booths, and admin stations.
03What is confirmed and what is not
The distinction to hold onto: the browser-and-phone path is how the documented Oasis platform works. The NFC station path is documented in the ecosystem's coin and terminal specification, which names RelicVerse as a use case, but no source confirms a station has been deployed for a live hunt. Treat stations as an available architecture rather than as shipped infrastructure until DigiFX states otherwise.