The people who do the work.
No account managers, no hand-offs, no bench of juniors. The people you meet are the people who design and write the work, and we bring in specialists we have worked with before when a project calls for it.
Product direction, partnerships and how the work reaches people. A decade spent building and running one of Toronto's larger blockchain communities, and a design background that shows up in when questions get asked rather than in how things look. Also known as Lisan.
Edward runs the side of the work that decides whether anything gets used: who it is for, what they already believe, and what would have to be true for them to change how they operate. That instinct came from a decade of meetups, speaker series and five large-scale hackathons, which is a long time spent watching which technical arguments survive contact with people who do not care about the technology. He is the reason the research happens before the build, and the reason a direction gets tested against real users while changing it is still cheap.
- Product direction·
- Partnerships and ecosystem·
- User research
Architecture and delivery, from the contract layer to the interface. Fifteen years of software development, the last several on decentralised systems, including zero knowledge circuits and a keyless wallet built in 2019, before account abstraction was a category anyone had named.
Paul owns the architecture and the parts of it that are expensive to get wrong: contracts, circuits, and the seams between a chain and everything around it. He has built two-factor authentication for on-chain transactions, and the privacy-preserving mechanism behind private yield. Most of the work is deciding what not to build, then making the remainder simple enough to reason about while somebody is attacking it.
- Protocol and contract architecture·
- Zero knowledge systems·
- Application development
