I am pleased to share that the Blackbox v0 prototype testing event has now concluded. This was a highly beneficial exercise that drew on the expertise of 6 community testers for focused feedback and review to guide the next stage of iterations towards a market-ready product.
This event was conducted through the Spark programme, and myself and @toastmanAu are grateful to the Spark committee for their support and advice.
You can find the full report and binaries on GitHub using the following links
I will share a short executive summary of the key takeaways from this event.
Blackbox Prototype Testing
Blackbox is being developed as an all-in-one point-of-sale (POS) terminal for merchants that supports familiar fiat workflows while preparing for crypto-native payment rails, such as Fiber Network, as they become viable in retail environments. Crypto-supporting POS terminals still occupy a tiny proportion of the overall market. Furthermore, crypto payments infrastructure and merchant/user experience are far from mature. Blackbox offers a comprehensive solution at a time when regions are embracing a more crypto-friendly approach to payments.
Development and testing
Over the latter half of 2025, an early prototype of Blackbox was conceived and developed. As features and functionality were added, it became clear that feedback to focus development priorities was essential. This would help inform the next stage of refinement towards real-world users. This testing programme was therefore conceived as a diagnostic exercise to identify what already works, where friction arises, and which improvements are most needed or would yield the most benefit.
Scope and approach
Testing was deliberately lightweight and expert-led. Six testers were selected based on relevant experience across hardware, software systems, blockchain development, and UI/UX. Each tester received a physical Blackbox V0 device, setup instructions, and a structured feedback pack informed by established human–computer interaction principles. Testing was coordinated on Discord and feedback was collected with combined qualitative commentary with numerical ratings across software, UI/UX, hardware, and usability heuristics.
The intention was to prioritise depth and quality of insight rather than statistical coverage. Given the early state of the prototype and the small sample size, numerical ratings were treated as directional rather than definitive, with qualitative feedback forming the primary basis for interpretation.
Key findings
Several aspects of the system were positively validated at a prototype level.
The hardware was shown to be sound. Testers consistently described the device as stable, well-assembled, and thermally reliable, even during extended use. Power reliability and heat management performed well, and no systemic hardware faults were identified. This provides a good foundation when refining for ergonomics and convenience.
Core functionality also performed reasonably well. Exchange-rate calculations, data persistence, invoice generation, and record accuracy were generally trusted by testers. While crashes and freezes were observed under certain conditions, recovery was fast and no data loss was reported. Taken together, this establishes a credible functional baseline for further performance enhancements. The biggest areas of critique centered around improving UI flows, intuitiveness, system feedback and error handling. Testers noted that improvements were required in enhancing visual hierarchy, removing ambiguity in workflows, reducing system response times, and improving the on-screen keyboard.
Recommendations
Thanks to the diligence and enthusiasm of the testers, we were able to produce a comprehensive list of improvements to target for the next phase of development, which is included in the report. A summarised version is as follows:
- Simplify core workflows (setup, payments, sales, inventory) to reduce unnecessary steps and reliance on implicit user knowledge.
- Make system state consistently visible through clearer loading, success, and error feedback across all interactions.
- Refine enclosure ergonomics, including edges, surface finish, width, and scanner placement, to improve comfort during regular handling.
- Improve stability and responsiveness during longer sessions and under variable network conditions.
- Strengthen visual hierarchy so primary actions are immediately clear and non-interactive elements are not misleading.
Operational reflections
From an operational perspective, the testing process itself worked well. The ability to deploy over-the-air updates during the testing window allowed issues to be addressed quickly without halting progress. Coordinating testers through a shared Discord channel proved effective for logistics and issue reporting. Difficulties were encountered with delays from international shipping of the units, as well as sourcing printer components that had gone out of stock. Our experiences in that regard, as well as our recommendations for other early stage hardware products, are included as an appendix to the report. Hopefully this will provide valuable insight to others on a similar path.
Next steps
Over the coming months, work will be undertaken to implement the feedback received as we advance from the prototype to a viable product. Additionally, implementation of fiat payment, along with close collaboration with the Fiber team to scope readiness for Fiber Network integration, will be priorities to fully realise the vision of Blackbox.
Closing remarks
This testing phase reinforced our view that early, structured evaluation is essential for hardware-led products. It provided certainty about the key areas needed for improvement, and validation for the base premise. Once again, we would like to thank the Spark team for helping to facilitate this process and for providing valuable feedback throughout.
以下为中文版本（支持 Markdown）：
我很高兴地分享，Blackbox v0 原型测试活动现已顺利结束。本次测试是一项非常有价值的工作，汇集了 6 位社区测试者的专业经验，提供了聚焦且深入的反馈与评审，用以指导 Blackbox 朝向市场就绪产品的下一阶段迭代。
本次活动是在 Spark 计划 的支持下开展的，我本人以及 @toastmanAu 在此对 Spark 委员会给予的支持与建议表示诚挚的感谢。
完整报告与可执行文件（binaries）可通过以下 GitHub 链接获取：
下文将简要分享本次测试的核心结论与关键收获。
Blackbox 原型测试
Blackbox 的目标是成为一体化的商用收款终端（POS），在支持商家熟悉的法币支付流程的同时，为未来加密原生支付网络（如 Fiber Network）在零售场景中的落地做好准备。目前，支持加密支付的 POS 设备在整体市场中仍占极小比例，同时加密支付基础设施及商户 / 用户体验也尚不成熟。在越来越多地区对加密支付持更友好态度的背景下，Blackbox 提供了一套具有前瞻性的综合解决方案。
开发与测试背景
在 2025 年下半年，Blackbox 的早期原型被构思并逐步开发完成。随着功能和特性的不断增加，我们逐渐意识到，必须通过系统化的反馈来聚焦开发优先级，以便更好地指导下一阶段面向真实用户的优化。因此，本次测试被设计为一次“诊断性评估”，旨在识别哪些部分已经运行良好、哪些地方存在使用阻力，以及哪些改进最为迫切或能带来最大收益。
测试范围与方法
测试采用了刻意保持轻量化、但以专家为主导的方式。我们根据硬件、软件系统、区块链开发以及 UI/UX 等相关经验，筛选并邀请了 6 位测试者。每位测试者均收到一台实体 Blackbox V0 设备、安装与使用说明，以及一套基于成熟人机交互（HCI）原则设计的结构化反馈资料。
测试通过 Discord 进行协调，反馈数据以定性评论与定量评分相结合的方式收集，覆盖软件、UI/UX、硬件以及可用性启发式指标。
本次测试更注重洞察的深度与质量，而非统计覆盖面。鉴于原型仍处于早期阶段，且样本数量有限，数值评分仅作为方向性参考，而非决定性结论；分析与解读主要基于定性反馈。
关键发现
在原型层面，系统的多个方面得到了积极验证。
硬件基础表现稳健。 测试者普遍认为设备结构扎实、组装可靠、运行稳定，即便在长时间使用下也未出现明显的热管理问题。供电稳定性和散热表现良好，未发现系统性硬件缺陷。这为后续围绕人体工学与使用便利性的优化奠定了良好基础。
核心功能表现总体可信。 汇率计算、数据持久化、账单生成以及记录准确性等关键功能均获得了测试者的基本信任。尽管在某些条件下观察到崩溃或卡顿，但系统恢复迅速，且未发生数据丢失。整体而言，这为后续性能优化建立了可信的功能基线。
最主要的改进意见集中在 UI 流程、直观性、系统反馈与错误处理方面。测试者指出，需要进一步改善视觉层级、减少流程中的歧义、缩短系统响应时间，并优化屏幕键盘的可用性。
改进建议
得益于测试者的投入与专业性，我们得以形成一份详尽的改进清单，并已收录于完整报告中。其要点概括如下：
- 简化核心流程（如设置、支付、销售、库存管理），减少不必要的步骤以及对隐性用户知识的依赖。
- 通过更清晰的加载、成功与错误提示，使系统状态在所有交互中始终保持可见。
- 优化外壳的人体工学设计，包括边缘处理、表面材质、机身宽度及扫描器位置，以提升日常操作的舒适度。
- 提升在长时间使用及复杂网络条件下的稳定性与响应速度。
- 强化视觉层级，使主要操作一目了然，并避免非交互元素产生误导。
运营层面的反思
从执行角度来看，本次测试流程整体运作良好。测试期间能够进行 OTA（空中更新），使问题得以及时修复而不影响整体进度。通过共享的 Discord 频道来协调测试者，在物流安排与问题反馈方面也被证明是高效的。
当然，我们也遇到了一些挑战，包括国际运输导致的设备延迟，以及部分打印机组件缺货等问题。相关经验与教训，以及我们针对其他早期硬件项目的建议，已作为附录纳入报告中，希望能为走在类似道路上的团队提供参考价值。
下一步计划
在接下来的数月中，我们将逐步落实本次测试中收集到的反馈，推动 Blackbox 从原型走向可行产品。同时，法币支付功能的集成，以及与 Fiber 团队的紧密协作、以评估并规划 Fiber Network 的集成可行性，也将成为重点工作，以全面实现 Blackbox 的愿景。
结语
本次测试再次印证了：对于以硬件为核心的产品而言，尽早开展结构化评估至关重要。它不仅帮助我们明确了最需要改进的关键领域，也验证了 Blackbox 的基本设想方向。我们再次感谢 Spark 团队在整个过程中提供的支持与宝贵反馈。
This kind of pragmatic approach is exactly what can lead to real-world adoption.