#009

Purpose

To operationalize backend referral tracking for early community growth efforts while strengthening mid-game resilience through Tapzi’s custom-built session recovery architecture and optimizing signature logic for reduced compute and gas.

Key Highlights

👥 Referral Attribution Engine (Phase 1, Beta-Only)

• Core backend logic activated: unique referral codes now attach to player records via URL campaign parameters.
• Logged metadata includes: referral code, source handle, registration time, and timestamp of first match entry.
• Attribution layer fully in-house—supports future expansion into milestone-based incentives and fraud prevention.
• Referrer–referee links are immutable at registration and stored with session-hardened hashes for auditability.

🧩 Frontend Referral Preview (Not Public Yet)

• Onboarding screen stub includes referral banner and passive code detection from deep links.
• UI copy and flow undergoing internal QA; full launch deferred to post-metrics tuning in Q4.
• Ref confirmation and invite tracking pages drafted but gated pending stability validation.

📡 Mid-Match Recovery Logic Upgrade

• Game engine now maintains persistent Session UUID tied to match ID and device signature.
• Upon reconnect (e.g., WiFi drop, app reload), game state is restored from last validated move, with no user action needed.
• 45-second timeout buffer enforces fairness while improving reliability across mobile networks.

🔐 Signature Optimization Pass

• Redundant game state hashes and repeated signature submissions compressed at both frontend and backend.
• Reduces transaction payload size and speeds validation without weakening result integrity.
• Concurrent replay hash mismatches are now gracefully rejected with rollback-safe logic.

📊 Session Stability Telemetry Activated

• Match lifecycle now includes connection state logging (session start, ping failures, reconnect attempts).
• Device/browser hashes used to correlate errors—anonymized and privacy-compliant.
• Logs streamed into ELK/Grafana stack for disconnect trend visualization and QA benchmarking.

Why It Matters

• Referral infrastructure is a strategic growth engine—tracking now live to validate virality and community incentives.
• Mid-game recovery strengthens Tapzi’s reliability narrative, particularly in competitive or staked scenarios.
• Optimized signature handling reduces validation cost and server load, scaling us closer to public beta performance targets.
• Real-world telemetry feeds technical and product teams for clearer prioritization and better tuning over time.

Open Issues

• Referral logic still vulnerable to multi-account edge cases; anti-abuse logic not yet enforced.
• Simultaneous reconnects from multiple devices may create forked match state (under test).
• Replay viewer doesn't annotate reconnect/resume events yet—limits post-match transparency.
• Signature pipeline not yet validated at high latency or degraded mobile network conditions.

Fixed

• Match abandon no longer triggered by mobile network switching (e.g., WiFi ↔ 5G).
• Backend settlement now handles missing one-sided submissions more gracefully, using recovery timeout logic.
• Referral attribution bug fixed: session-local data no longer overwrites correct referral from URL tracking.

Next Steps

• Launch referral attribution dashboard with cohort analytics, match conversion tracking, and retention curves.
• Integrate session telemetry into Grafana dashboards for live monitoring of stability and recovery trends.
• Annotate disconnect/reconnect events in replay logs for audit/debug purposes.
• Start closed referral campaign with handpicked Discord testers for early performance signal.