I am CTPO and co-founder at Gateway.fm, where we build infrastructure for institutions moving finance onchain.
My work sits at the intersection of Ethereum infrastructure, security, privacy, and regulated financial systems — execution clients, rollups, RPC systems, and privacy infrastructure for EVM chains. I have been working on Ethereum and blockchain infrastructure since 2017.
What changes when blockchain infrastructure has to serve real institutions rather than a protocol demo?
Still holds. Institutions don’t buy components — they buy one operated outcome. RFPs already arrive split into five or six parts; the more of those parts you can join into one accountable whole, the stronger the answer.
What changed. Privacy moved from a nice-to-have to the blocking requirement — which is why Open Privacy Suite became the current focus.
Useful for platform and infrastructure leads at banks and fintechs evaluating onchain rails.
How do you choose a privacy architecture without pretending privacy is one problem?
Still holds. Confidentiality and auditability have to coexist. A policy layer over standard JSON-RPC can preserve application interfaces; operator access and cross-network settlement still need their own controls.
What changed. I used to lead with the technology. What buyers actually need is a product — an orchestrated outcome, with a counterparty they can work with and hold accountable.
Useful for architects and compliance owners in regulated EVM environments.
Still holds. The internet-of-rollups vision is more relevant than ever — many chains, joined into one settlement fabric, each owned by whoever needs it. And it turned out to include the good old enterprise-blockchain thesis: Besu-style networks are joining the same fabric.
What changed. The selling point flipped. It isn’t performance — it’s sovereignty. Privacy went from optional to required. And interoperability is still the difficult choice.
LE FLAClocal-first FLAC player, no network permission
Contact
If your onchain project has turned into a five-vendor RFP — procurement, integration, support, privacy, data protection, all from different parties — reach out.
