Infrastructure
Developer experience, reliability, permission boundaries, and operating cost
+I look at blockchain infrastructure, compliant financial applications, and developer tools across APAC. The work moves from product signals through technical and commercial diligence to token, equity, and market-entry choices.
Three entry points, one connected verification path.
Developer experience, reliability, permission boundaries, and operating cost
+Institutional decision chains, regulatory perimeters, and integration conditions
+Time to first value, retention paths, and ecosystem connections
+Move from signal quality to an executable structure, leaving evidence at each checkpoint.
Who returns, and which workflow resists substitution?
Where is the claim verified, and how are permissions distributed?
Who owns the decision, and which constraint blocks adoption?
Do value flow, token, equity, and governance align?
Common diligence questions translated into observable signals, interview prompts, and unresolved items.
All field notes ↗A live product turns architecture claims into operating evidence. The work shifts toward recurring use, incident response, support load, and the assumptions that no longer fit.
↗02Interest can be abundant while procurement stays still. Compliance, custody, integration, budget, and ownership determine whether an institutional user can proceed.
↗03Architecture diagrams and audit reports begin the inquiry. Confidence grows when claims connect to code, deployments, incidents, and team response.
↗Hong Kong
HashKey Capital · Full-time
Master of Finance · Finance
2017–2020
Open to exchanges on APAC Web3, technical diligence, and market-entry constraints.