Jan Philipp Fritsche
1.1K posts

Jan Philipp Fritsche
@JphFritsche
Founder @Bermudabayzk | Strategy Director of @SecurityOak | Macro-Finance (PhD) | Regulation | Crypto | before @ecb, @DIW_Berlin


Under worst-case conditions, Ethereum finality can take a long time. But in practice, enough confirmations arrive in under 13 seconds to treat transactions as final. Bridges, CEXs, and L2s could accept deposits MUCH faster by counting confirmations, not blocks.






The next challenge is enabling institutions to settle assets and cash across chains without exposing sensitive data or creating new settlement risk. Linea and @bermudabayzk show that private, atomic and verifiable settlement is possible. Blog post ↓ linea.build/blog/atomic-dv…

── Dappcon 2026 Speaker ── Banks have been told privacy and auditability are opposites. They're not. 🎙 Dr. @JphFritsche · @bermudabayzk ↳ "Enabling Institutional Adoption: Privacy, Auditability and Verification" Jan will give a talk on how zero-knowledge proofs and selective disclosure dissolve the trilemma holding institutions back from public blockchains — making systems that are private by default, auditable on demand, and verifiable on proof, without retreating to permissioned chains.



He brings a rare combination: Web3 cybersecurity, empirical research on regulation, and entrepreneurship. Jan Philipp Fritsche (@JphFritsche) is co-founder of @bermudabayzk, the institutional privacy layer for the EVM, and Strategic Director of @SecurityOak, the Web3 cybersecurity firm behind 600+ audits across the Ethereum Foundation, Arbitrum, Cosmos, and many more. His earlier work tracked the implications of financial and economic policy for money markets, derivatives, and systemic risk, with a focus on financial infrastructure, as a researcher at the ECB, the European Parliament's Monetary Expert Panel, Deutsche Bank, the Bundesbank, and DIW Berlin. He also hosts MetaMarkets, a podcast exploring the interface of regulatory and technical matters in Europe. Join us in Berlin: luma.com/pb46re0a


Update from ZachXBT. What does this mean for privacy protocols?




