KNOWLEDGEBASE
OASIS

Company Prototypes

3 min read·Article 02 / 09

Company documentation treats Oasis RelicVerse as a platform in its own right — an immersive geo-based treasure-hunt platform — and no available source describes it as a reference build or demonstration of a separate OasisCore product. This page describes what internal documentation records about the platform and the hunts designed on it.

01Oasis RelicVerse

RelicVerse is described in company materials as a geo-located AR and physical experience platform that merges augmented reality with location-based services, blending digital interaction with real-world spaces and rewards. Internal architecture notes give it a more specific role: a hybrid of AR, narrative, and puzzle design that hosts relic hunts, the RelicVerse catalogue, and immersive storylines. Its documented public domain is relicoasis.com.

The documented feature set is aimed at a particular set of hard problems. Anyone can describe a treasure hunt; the hard parts are proving presence without being trivially spoofable, releasing clues on a schedule that holds a fourteen-day arc together, and settling rewards under real scarcity rules. Those are the parts the platform's documentation emphasises, rather than a map with pins on it.

02The Gatekeeper's Veil

Internal platform documentation names The Gatekeeper's Veil as the flagship hunt and records a September 2025 launch. It is documented as shipping with the anti-cheat behaviour the platform depends on: GPS verification, spoof detection, and multi-factor solve validation rather than a single answer check.

That combination is the substantive claim being demonstrated. A hunt that only checks answers can be completed by one participant and shared to everyone else within minutes, which destroys both the leaderboard and the scarcity of the reward. Verifying position, checking movement plausibility, and binding each claim to one participant and one hunt is what keeps the result meaningful.

No results from this hunt appear in any source available. Participation, completion rate, and any client or partner involvement are unrecorded and must come from Nate before this page can say anything about outcome.

03Scheduled hunts

Documentation records six hunts scheduled across global cities, naming New York, London, Tokyo, Cairo, Beijing, and Mexico City. The catalogue behind them is recorded as more than one hundred relics spanning sixty-nine categories and twenty-two tiers.

Read that as a designed programme rather than a delivery record. Nothing in the available material confirms which of those six were built, which were scheduled, and which remain planned. A city list is a plausible thing to design ahead of demand, and presenting it publicly as delivered work is exactly the kind of claim that fails on the first specific question from a prospect.

04Status caveat

Internal platform records mark Oasis as production-targeted with a documentation-based status flag, meaning the status reflects what project documentation asserts rather than an independently verified live check. The DigiFX public roadmap, separately, lists OasisCore as a planned Phase 03 item. These two statements need to be reconciled before any of this page's material is used in a sales context.

Need custom diagnostic analysis?

Contact our support engineers directly to initiate bespoke technical resolution.

CONNECT SUPPORT