# #012

#### November *21, 2025**:-** Beta Launch, Stats UX Improvements & System Reliability Sprint*

### Purpose

To support Tapzi’s live beta rollout with improved player-facing analytics, reinforce platform observability, and resolve reliability issues surfaced under early public load conditions.

***

### Key Highlights

🎉 Tapzi Beta Is Live\
The Tapzi platform is now available for public testing at[ tapzi.io/game](https://www.tapzi.io/game). Early participants can stake TAPZI, play verified skill-based games, and experience the foundational version of our fair-play economy.

📊 Player Dashboard Metrics Enhanced

* New frontend components deployed for win/loss streaks, time-to-move stats, and abandonment rates.
* Stats UX improved with hover tooltips, timezone alignment, and visual feedback for missing data.
* Stats queries cached at edge nodes to reduce latency during peak usage.

📉 Real-Time Replay Event Overlay (Admin)

* Replay viewer now annotates disconnects, reconnects, timeouts, and result changes as timeline flags.
* Supports moderator clarity in disputes and improves trust score auditing.

🧩 GraphQL Proxy Introduced for Analytics API

* Optimized telemetry delivery by batching and deduplicating event calls across sessions.
* Reduces backend pressure while maintaining real-time observability for player lifecycle metrics.

🧠 Anti-Bot Flag Feedback Integration

* Players notified (non-intrusively) when their account behavior triggers integrity checks.
* Adds transparency and opens user dialogue to reduce false positives.<br>

***

### Why It Matters

* Launching the beta validates Tapzi’s smart contract integration, real staking UX, and core gameplay experience in production.
* Stats and match telemetry empower players to self-assess and improve over time—crucial for skill-based ecosystems.
* Replay event annotations enable scalable moderation without sacrificing dispute integrity.
* Balancing performance and analytics helps scale the platform responsibly with a lean dev team.<br>

***

### Open Issues

* Some leaderboard queries causing cache-stale data under race conditions.
* Mobile beta testers occasionally fail to receive replay annotations due to viewport clipping.
* Bot detection feedback UI not yet localized—English only.<br>

***

### Fixed

* Tournament delay notifications now queue correctly across all device sizes.
* Graph jitter eliminated in stats timeline when viewing more than 10 matches.
* Referral event duplication bug resolved on high-speed reconnections.<br>

***

### Next Steps

* Expand beta access via whitelist codes and Discord invite-only flow.
* Launch public bug bounty for replay event viewer and staking mismatch edge cases.
* Add mobile-first dashboard version with collapsible stats view.
* Begin rollout of early performance badges and achievement display logic.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tapzi.io/tapzi-dev-release/012.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.