Skip to main content

Roadmap

WEFA's development follows a Cynefin-informed strategy: move from Complicated (many interdependent unknowns) toward Clear (standardized, repeatable best practices). V1 stabilizes the core loop as a predictable, testable system. V2 and beyond layer on complexity only after the foundation is proven.

V1 — Core Loop (Current)​

V1 delivers the complete plant-to-play loop as a local-first PWA that works offline and can be demonstrated in a single session.

Scope​

  • Onboarding: Passkey or wallet authentication, element selection, home biome setup, first creature generation
  • Plant care: Add plants via camera capture, daily photo care events, streak tracking, energy rewards
  • Creature system: Nurture creatures with earned energy, evolve through four stages (Seed, Sprout, Bloom, Elder), 9 base Massiah creatures across four elements
  • Gameplay: Tic-Tac-Toe with non-AR baseline and optional AR mode when WebXR is available, pass-and-play local multiplayer, creature-based game tokens
  • Attestations: EAS offchain attestations for care events, game results, and evolutions (self-attested L1)
  • PWA: Installable, offline-capable, service worker cached, works on iPhone SE through iPad Air
  • AR: WebXR on Android Chrome, non-AR 3D canvas fallback on iOS and desktop

Definition of Done​

A new player can onboard, add a plant, record care, earn energy, nurture and evolve a creature, play a game, and claim a reward — all in one session, with or without network connectivity.

V2 — Expansion (Planned)​

V2 broadens the system from a local proof-of-loop into a connected, community-driven platform.

Full Marketplace​

  • Player-to-player creature and card trading with provenance tracking
  • Community creature packs and game variants as purchasable or earnable content
  • Creator economy with remix lineage and contribution credits preserved via EAS

Multiplayer Scaling​

  • WebRTC peer-to-peer sessions via Yjs for real-time remote play
  • World tournaments with Unlock Protocol membership gating
  • Spectator mode for live community events

ZK Proofs​

  • Zero-knowledge correctness proofs for game results (Tic-Tac-Toe transcripts verified without revealing strategy)
  • ZK geofencing for location-based features without exposing exact coordinates
  • ZK membership proofs (Semaphore-style) for anonymous yet verified participation

Tokenbound Accounts (ERC-6551)​

  • Creatures as NFTs with their own wallets holding evolution history, earned badges, and game records
  • Composable creature identities that carry their full provenance across platforms

Advanced AR Anchoring​

  • Persistent AR anchors for Shrine locations and community gardens
  • Shared AR sessions where multiple players see the same creatures and game boards
  • Cloud-anchored AR experiences that persist between visits

Additional Games​

  • Ludo: longer social sessions with more reward hooks
  • Mancala: strategic, culturally resonant gameplay supporting learning outcomes
  • Chess: classic strategy with creature-themed pieces

WEFA World Physical Experiences​

  • Physical Shrine locations coordinating local plant care, nature play, and learning
  • Seasonal events tied to the WEFA lore map and real-world ecology
  • School and community partnerships with region-specific ecology modules

IoT Shrine Sensors​

  • NFC and Bluetooth-enabled physical Shrines for check-in and proof of presence
  • Plant sensors (soil moisture, light, temperature) as optional care event verification
  • Sensor data feeding into L3/L4 attestation trust levels

AT Protocol Integration​

  • "Sign in with AT" (Bluesky) for immediate social onboarding
  • Social feeds for discovery, match invitations, and achievement sharing
  • Identity linking between AT DID and EVM address for cross-platform portability

Cynefin Framing​

DomainWhat it means for WEFA
Complicated (V1 start)Many interdependent systems (AR, ECS, attestations, offline sync, creature generation) with unclear integration patterns. Requires expert analysis and careful sequencing.
Clear (V1 target)The core loop is standardized as best practice — predictable, testable, and repeatable. Any developer or agent can extend it by following established patterns.

The strategy: stabilize the inner loop (plant, reward, creature, game) as a clear, predictable system. Keep risky and variable edges (AR device compatibility, on-chain UX friction, sensor permissions, ZK circuits) as optional modules and stubs until the loop is running smoothly. Then progressively move V2 features from complicated to clear as each is proven.