Background
Chief Technology Officer at OVAAL. Architecting the neutral control plane for programmable finance: the production SDK and APIs, the compliance execution path, and the multi-rail orchestration that lets regulated EU and MENA fintechs add programmable accounts, money movement and settlement under their own authorisation. ERC-4337 AA wallets and crypto are one proven rail in that stack, not the whole picture. The integration timeline is a design target, typically scoped at 4 to 8 weeks; actual rollout depends on scope, regulatory responsibilities and provider onboarding, and we have not yet published a case retro. Background spans backend systems engineering, programmable-finance protocol work, and fintech compliance integration. More on the team and mission is on the about page.
What the CTO writes about
- Architecture decisions. Non-custodial-by-default, one SDK surface, versioning as contract, compliance inline in the execution path. Why these choices make the integration timeline real.
- ERC-4337 in production. Passkey onboarding, session-key scoping, paymaster policy, recovery flows that actually work for compliance review.
- Trade-offs. What the architecture gives up. When partners should pick a specialist instead.
Articles
- The architecture behind a fast control-plane integration (CTO walkthrough)