Interact-to-Earn Extension

Mixed Reality Glasses Module

This extension page breaks out the MR glasses track from Interact-to-Earn: how spatial ads appear, how rewards are calculated, and how users can control ad intensity in real time.

Launch MR MVP App Back to Interact-to-Earn Back to Home

Spatial Ad Zones

Ads are anchored to physical coordinates and rendered as persistent overlays through MR glasses. Brands can run city blocks, venue zones, or geo-fenced campaign layers.

Interact-to-Earn Rewards

Users receive WEAD token rewards for verified interactions such as dwell time, gaze completion, gesture interaction, and campaign quest completion.

User Controls

Users can set ad density modes (low, balanced, high), mute categories, and define time windows. Reward rates adjust dynamically to campaign demand and interaction quality.

Rollout Scope

  • Phase 1: Closed pilot with partner brands and controlled urban test zones.
  • Phase 2: Public beta with campaign dashboards and advertiser interaction analytics.
  • Phase 3: Open ecosystem with creator-built spatial ad templates and API access.

How to Connect MR Glasses

Path A — Fast Start (Browser / Simulator)

  1. Open the MR app: Go to /interact-to-earn/mr-app.
  2. Start Session: Click Start Session to create a backend XR session.
  3. Browser XR: If device/browser supports WebXR, click Enter XR. If not, simulator mode continues automatically.
  4. Load placements: App fetches active spatial placements and shows interaction controls.
  5. Interact + earn: Dwell, tap, gaze, quest actions are verified server-side and rewards are calculated.

Path B — Full Native Headset (Unity/OpenXR)

  1. Provision a device key: Admin creates a native bridge device via /api/xr/admin/native-devices.
  2. Use starter kit: Open /static/unity-openxr-starter/README.md and import the scripts in Unity.
  3. Configure: Set baseUrl, x-api-key, and placement ID in WeadXrBridgeConfig.
  4. Start native session: Client calls /api/xr/native/session/start.
  5. Stream telemetry: Client sends events to /api/xr/native/telemetry with idempotency keys.
  6. End session: Client closes with /api/xr/native/session/end; rewards remain server-verified.
Phones can act as control/simulator interfaces, but native headset integration does not require routing through a phone.

What WeAD Can See When Users Connect

  • Session metadata: session ID, mode (simulator/quest/webxr/native), start/end times, and duration.
  • Device context: capability flags and user-agent-style environment info for compatibility decisions.
  • Interaction telemetry: event type (gaze/tap/quest/etc), dwell time, confidence, placement/campaign IDs, reward decision.
  • Reward outcomes: granted/denied result, amount, currency, and event timestamps.
  • Operational analytics: placement fetches, session funnel events, and aggregate usage patterns.

What WeAD Does Not Need For Core Rewards

  • Raw camera video stream uploads.
  • Continuous raw sensor dumps beyond event-level telemetry.
  • Unbounded personal data unrelated to interaction verification.