Background & Biography
Berengoltz came to digital assets through cybersecurity. Before Fireblocks, he worked at Lacoon Mobile Security and then Check Point Software Technologies following Check Point’s acquisition of Lacoon in 2015. A Fireblocks company presentation identifies his earlier responsibilities as director of research at Lacoon and director of mobile at Check Point, alongside research-and-development work at Safend. This progression placed him close to the practical problems of protecting software, credentials and devices used by businesses.
The company’s founding account links its direction to an investigation of cryptocurrency-exchange breaches in 2017. Independent reporting by Calcalist describes Shaulov and Berengoltz examining the incident while working at Check Point, then bringing Ofrat into the new venture. Their conclusion was that digital-asset operations required security designed into the transaction process. Fireblocks emerged publicly in June 2019 with $16 million in funding and a platform aimed at institutions moving assets between wallets, trading venues and counterparties.
His title has evolved with that business. Older company material calls him vice president of research and development, while Fireblocks’ current executive roster identifies him as chief technology officer and co-founder. Michael Shaulov remains CEO and Idan Ofrat is chief product officer, so the founders’ responsibilities should not be conflated. Berengoltz’s professional profile identifies Israel as his base, consistent with later reporting on the engineering founders; the United States is also an important organizational and regulatory market for Fireblocks.
Notable Contributions
Fireblocks’ central engineering proposition is that institutions need a controlled way to use blockchain assets, as well as a place to store them. Its direct-custody documentation describes multiparty computation, or MPC, in which several parties participate in producing a signature without bringing a complete private key together during signing. It combines that approach with hardware-isolated environments and operational controls. Berengoltz’s significance is his technical leadership within this architecture, rather than an unsupported claim that he invented MPC or personally authored every component.
The platform’s recovery design illustrates why implementation matters. Fireblocks describes a backup package that allows customers to recover keys and move assets using software outside the platform. Such an arrangement addresses dependence on a technology provider, but it still requires correct setup, custody of recovery material and tested procedures. For institutional users, the useful question is whether the complete operating process remains workable when a device, employee or service becomes unavailable.
Publishing research and implementation code is another important strand. In August 2023, Fireblocks made its MPC-CMP implementation and wider MPC library publicly available under a limited licence, allowing researchers and auditors to examine the code. Its announcement also pointed to a bug-bounty program and implementations using Intel SGX and AWS Nitro. The distinction between an inspectable protocol, a particular software implementation and the permissions in its licence is important: public availability is valuable evidence, but it does not establish unrestricted reuse or eliminate security risk.
That same month, the Fireblocks cryptography team disclosed the BitForge family of vulnerabilities affecting certain MPC protocols and implementations. Berengoltz used the announcement to emphasize the need to maintain wallet infrastructure and work with security specialists. Zengo independently confirmed collaboration with Fireblocks, remediation and that no Zengo users were affected. This is a documented example of research contributing to another provider’s defenses; the discovery belongs to the research team, and it should not be described as a successful theft from the affected customers.
The research program continued with MPC-BAM, announced in December 2024 as a two-party ECDSA protocol. Fireblocks framed the work around tradeoffs among communication, computation and the number of interaction rounds needed to produce signatures. Those are consequential engineering choices when security must coexist with responsive financial services. Publication of a protocol nevertheless differs from verification that a particular customer system has deployed it, and performance descriptions need to remain tied to their stated test conditions.
Berengoltz has also participated directly in technical-policy advocacy. He signed an August 2025 industry letter asking the US National Institute of Standards and Technology to accelerate guidance for threshold-signature schemes. The signatories included researchers and representatives from financial, technology and security organizations. Their proposed timetable was a request to the standards body, not proof that a standard had been adopted or that a Fireblocks product had received government certification.
His August 2026 essay on AI in financial infrastructure adds a more personal account of his priorities. He argued that rare errors and unusual operating conditions matter especially when software can affect money, and described a push toward a more AI-native platform. He also announced the arrival of Tymely founders Ohad Rozen and Roy Penn in AI leadership roles. The essay is evidence of his stated direction and hiring priorities, rather than an independent assessment of the reliability of those systems.
Why Katharos.ai Follows Pavel Berengoltz
Katharos.ai follows Berengoltz because his work sits where cryptographic design meets a financial institution’s daily responsibilities. A mathematically sound signing scheme must coexist with approvals, recovery, software updates and the people operating it. Fireblocks’ research disclosures and published architecture provide specific material against which to assess those requirements. His standards advocacy also shows how technical adoption can depend on the rules and benchmarks used by institutional buyers.
The business model requires equally careful distinctions. New York’s financial regulator lists Fireblocks Trust Company, LLC as holding a limited-purpose trust charter dated August 2024. That is an entity-specific regulatory fact, separate from the wider software platform and its direct-custody arrangements. Following Berengoltz therefore means examining which technology is used, who controls the assets and which legal entity owes the customer a duty, rather than treating the Fireblocks name as a single answer to all three questions.
Areas to Follow
- Independent examination of MPC implementations, remediation quality and the practical limits of security claims. - Recovery procedures and operational resilience across different deployment models. - Threshold-signature standardization, separating industry requests from completed standards and certifications. - AI-assisted operations, including authorization boundaries, exception handling and measurable reliability. - The division of responsibility among Fireblocks software, its trust company and partner custodians as payment and tokenization uses expand.
Reporting Scope
This profile covers Berengoltz’s public professional background, current technical leadership and selected documented developments through 6 October 2026. Corporate research is credited to the responsible teams. Product descriptions and personal commentary are attributed to their publishers, and no claim of immunity from failure is made. Israel denotes the verified professional base; it is not an assertion about citizenship or private residence.
Areas of Influence
Exchanges & Infrastructure is the principal category because his work concerns the systems used to secure and operate digital assets. Investment & Founders reflects his role in building Fireblocks, rather than a claim about a personal investment portfolio. Stablecoins & Payments captures the relevance of that infrastructure to institutional money movement. His standards work is industry participation in technical policy, not a public regulatory appointment.
Katharos.ai publishes this profile for information, based on the sources listed. Inclusion is not an endorsement of the individual, their organizations, or any investment product.
Source notice: Information and images are attributed to the external sources listed. Katharos.ai does not endorse the subjects or claims described and does not independently certify the authenticity of every source statement or image.