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 ↗Testnet activity is easy to count and hard to interpret. A useful diligence view asks who generated it, what they were trying to accomplish, and whether they returned without a prompt.
↗02Commit counts describe motion. Retention requires a path from learning to building, deployment, and maintenance—each with different evidence.
↗03A company, protocol, foundation, and token can hold different rights inside one project. The structure only makes sense when value creation and control are traced across them.
↗Hong Kong
HashKey Capital · Full-time
Master of Finance · Finance
2017–2020
Open to exchanges on APAC Web3, technical diligence, and market-entry constraints.