Community-Powered Beta Testing for Tonkeeper

Tonkeeper is partnering with xcrwd.io — a community-powered testing platform built on TON — to launch a structured public beta testing program. The program opens early access builds to real users, collects structured bug reports, and feeds that feedback directly into the development cycle.

What Is xcrwd?

xcrwd (pronounced "xcrowd") is a decentralized QA platform built on The Open Network. Its model is straightforward: projects post testing tasks, community members complete them and submit reports, and valid submissions are reviewed and rewarded. The platform uses on-chain verification to track participation and ensure report authenticity — all activity is tied to TON wallets, making contributions traceable and reward-eligible without a centralized intermediary.

For Tonkeeper, this means a transparent pipeline: a tester submits a bug report through xcrwd, the Tonkeeper team reviews it, and if valid, it gets logged in the public changelog. The tester's contribution is on record, linked to their wallet.

What the Program Covers

The beta testing program runs across both iOS and Android versions of Tonkeeper. Testing scenarios include:

Core wallet flows — sending, receiving, and swapping tokens
DeFi integrations — connecting to protocols through the in-app browser
NFT display and management
Tonkeeper Pro features — multi-account support, two-factor authentication, gasless transactions
Edge cases and device-specific behavior (older OS versions, low-memory devices, non-standard screen sizes)

Edge cases in the last category are often the most valuable reports. Internal QA teams typically test on current hardware under normal conditions. Community testers using older phones, slower connections, or unusual system configurations surface issues that wouldn't otherwise appear before release.

How Reports Become Fixes

When a valid bug report is submitted through xcrwd, it goes through a review queue. The Tonkeeper engineering team evaluates:

Reproducibility — can the issue be reproduced with the steps provided?
Severity — does it affect core functionality, or is it a UI inconsistency?
Uniqueness — has this already been reported or is it a known issue?

Reports that pass review are added to the development backlog and, once fixed, referenced in the public changelog. This gives testers a direct line of sight from their report to the shipped fix — something that's rare in traditional beta programs.

Multiple bugs caused by the same underlying issue count as one report. The program doesn't reward volume of reports — it rewards quality and reproducibility.

How to Join

Participation is open to anyone. No technical background is required — you need only a Telegram account, a device running Tonkeeper, and attention to how the app behaves.

Open @tonkeeper_xcrwd_bot on Telegram
Answer a short set of onboarding questions (device type, OS version, Tonkeeper usage frequency)
Wait for approval — the xcrwd team reviews applications to maintain report quality
Once accepted, you receive access to testing builds and submission guidelines

Builds distributed through the program are pre-release versions of Tonkeeper — they may contain bugs that aren't present in the public App Store or Google Play releases. This is expected, and reporting those bugs is the point.

Writing a Useful Bug Report

The quality of a report determines whether it can be acted on. A useful bug report includes:

Steps to reproduce — the exact sequence of actions that triggers the issue, starting from the app's home screen
Expected behavior — what should have happened
Actual behavior — what actually happened
Device and OS — model, operating system version, Tonkeeper version
Screenshot or screen recording — especially for visual bugs or crashes

Reports that say "the app crashed" without reproduction steps are difficult to act on. Reports that say "when I tap Send on an NFT transfer while connected to 3G and the screen rotates mid-transaction, the app freezes at the confirmation screen" are immediately actionable.

Why Community Testing Works

Internal QA processes are bounded by team size and test environment homogeneity. A community of testers across different countries, devices, carriers, and usage patterns covers a surface area that no internal team can match. This is the principle behind programs like Google's Bug Hunters program and HackerOne's coordinated disclosure model — scale and diversity produce coverage that depth alone cannot.

For Tonkeeper specifically, the global Telegram user base means the app runs across an unusually wide range of devices and network conditions. Community testers who use the app daily in their real environment are the best source of real-world reliability data.

Sources & further reading:
xcrwd.io — community testing platform on TON
@tonkeeper_xcrwd_bot — apply to join the program
Google Bug Hunters — example of large-scale community QA

Your feedback contributes directly to the future of Tonkeeper.

Download Tonkeeper: tonkeeper.com
Download Tonkeeper Pro: tonkeeper.com/pro
Follow: en · ru · فارسی · 中文 · uz · twitter