I build infrastructure and developer surfaces for crypto systems that need to be understood, not just used.
My work spans protocol engineering, real-time data systems, ecosystem education, and product interfaces because technical systems only matter when people can reason through them.
Currently at Architect0, after building at Rover1, representing Polkadot in Southeast Asia2, and co-founding OpenGuild3.
perpetual exchange engineering
These experiences shaped a few working beliefs. They are not rules, but defaults I keep returning to when a system, team, or product starts to feel too clever for its own good.
The most honest view of a protocol is usually not the pitch deck or the interface. It is the path an event takes through the system: where it is produced, how it is transformed, what gets dropped, and what can still be explained after the fact.
A workshop, a bootcamp, a clear example, or a patient answer can unblock more builders than another abstraction. Ecosystems compound when knowledge moves with low friction, and the best DevRel work feels like reducing latency in the human layer.
A clean product is not one that hides complexity by pretending it does not exist. It is one that lets people touch the right amount of complexity at the right moment, without losing the shape of the system underneath.