Fuji.Trade
The team publicly acknowledged the issues I reported and confirmed fixes for transaction execution and wallet signing.
Open to freelance, contract and remote work
I find the bugs before your users do.
QA engineer for teams and businesses building Web3, AI, SaaS and mobile products. I test the journeys that carry your revenue and trust, and I report every finding so your team can fix it fast.
4+Years testing
500+Bugs reported
45+Releases tested
CriticalFuji.Trade · Web & Mobile
Wallet signature text is unreadable on the approval screen
- Where
- Transaction approval
- Actual
- Unreadable characters shown instead of the signing message
- Impact
- Users may reject legitimate transactions and lose trust
Fixed. Confirmed by the development team.
A real finding from the Fuji.Trade case study
Results
What happened after I reported
MITA (Livie)
I tested new features, verified fixes and ran regression checks across several release cycles of this social mobile app.
JagSim
The team reproduced the first two trading issues and invited me to discuss a broader, comprehensive QA audit.
Selected work
Products tested before users found the problems
Each case study shows what I tested, what I found, how severe it was and what changed.
Web3 Trading
Fuji.Trade
Release-readiness QA on a decentralized trading platform: wallet signing, authentication and trade execution.
- Wallet signature text unreadable on approval
- Trade execution delay after submit
- MetaMask login stuck on mobile Chrome
3 critical1 highRead case study
Web3 Invoicing
Invoix (Solana)
Independent QA assessment of a Solana invoicing app. Found a critical RPC failure blocking invoice creation.
1 critical1 mediumRead case study
Trading Web App
JagSim
Client QA audit of a trading simulator: 8 issues across order flow, live data, charts and market state.
- Crypto market shows stock-hours message
- Stale BTC price after returning to the app
- MAX button shows inconsistent amounts
2 high3 medium3 lowRead case study
Web3 Wallet
KuCoin Web3 Wallet
Independent exploratory testing of a Web3 wallet's onboarding and navigation, publicly acknowledged by the team.
Acknowledged publicly by the teamRead case study
AI Web App
Engrama
Independent QA review of an AI product's onboarding, accessibility and mobile experience.
- App subdomain unreachable
- Signup button leads to a dead page
- Mobile form fields misaligned
2 critical1 mediumRead case study
Web3 Prediction Market
Socrates
Founder-led QA engagement on a Web3 prediction market, covering user flows, usability and product feedback.
Worked directly with the founderRead case study
Mobile Social App
MITA (Livie)
Multi-release QA on a social mobile app: calls, live rooms, games, a metaverse world, shop, token transfers and referrals.
Tested across multiple releasesRead case study
Web3 Mobile App
Satoshi Network
Feature validation across a Web3 app, website and Telegram bot: mining, staking, vault, shop, referrals and token transfers.
Feature and release testingRead case study
Web3 Gaming
SugarSenpai
Exploratory and functional testing of an early-stage Web3 game, delivered as structured QA feedback.
Early-stage product reviewRead case study
How I report
Every finding is ready for a developer to act on
No vague "it's broken" tickets. Each report carries what an engineer needs to reproduce, judge and fix the problem.
SeverityCritical, High, Medium or Low, so the team knows what blocks release.
StepsClear reproduction steps that work the first time.
EvidenceScreenshots and environment details: device, browser, wallet.
ImpactWhat it means for users, trust and the business.
Fix adviceA recommendation, plus a re-test once it ships.
What I do
Testing across the stack your product runs on
Exploratory testing
Hands-on investigation of real user journeys to find what scripts miss.
Functional testing
Checking that each feature does what it should, end to end.
Regression testing
Making sure new releases do not break what already worked.
Mobile and web testing
Real devices, browsers and wallets, not just one setup.
API testing (Postman)
Validating requests and responses behind the interface.
Release readiness
A clear view of risk before you ship.
Shipping something soon? Let's test it first.
I typically reply within 24 hours.