ZKsync Türkiye Topluluğu

Today we reduced the size of the Matter Labs team. This was my decision, and I want to explain it. In 2024 we began building for regulated financial institutions. That work became Prividium, and the entire company is now committed to one goal: building the infrastructure that brings enterprises and regulated financial institutions onchain, with privacy at its core. As that work has progressed, we have learned a great deal about where our customers need it to go. Meeting that direction calls for a different mix of skills and roles than the phase before it, and some of what made sense earlier is not what we need now. That is the reason for today's changes. It hurts, because this is not about the effort or talent of the people leaving, who I deeply respect. They are some of the strongest engineers, designers, and operators I have worked with. Everyone leaving has been offered financial support, and we are helping with the transition wherever we can. If you are hiring, you can request access to our opt-in talent list here: docs.google.com/forms/d/e/1F… To everyone leaving: thank you for what you built here, and for the standard you set. Alex

Yuval continues to frame ZK as a "black box" that could somehow "corrupt" systems. This is a fundamental misunderstanding; the reality is the exact opposite: ZK adds a layer of incorruptibility on top of traditional financial systems. Enterprises don't need ZK primarily for privacy, as they already operate inside tightly controlled security perimeters. What ZK provides is far more important: cryptographic guarantees of execution correctness and operational integrity. Non-ZK chains featuring privacy, such as Canton, restrict data visibility but don't allow network-wide verification of correct execution. Participants can only verify transactions they're directly involved in. Everything else is accepted implicitly based on trust in a small set of privileged actors: domain operators, mediators, sequencers, and governance entities. This introduces non-negligible systemic trust and integrity risks. Yes, individual stakeholders can veto invalid transactions they personally participate in. But global invariants (supply integrity, absence of double-spends, correct enforcement of authorization rules, etc.) are only as strong as the security of those privileged actors. If enough of their keys or systems are compromised, invalid state transitions can be committed and appear indistinguishable from legitimate history to everyone else. This is not a theoretical edge case. With incresingly sophisticated AI-assisted attacks, long-term credential harvesting, and supply-chain compromises, attackers don't need to act immediately. They can patiently accumulate access across operators, mediators, and complicit participants, then execute coordinated violations. Because execution is not universally verifiable, such attacks can be buried inside the transaction history, with no public or cryptographic way for outsiders to detect that smart contract rules or issuance constraints were violated. In contrast, ZK-based enterprise frameworks, such as @ZKsync Prividium, take a strictly stronger approach. They retain the same enterprise controls: private deployments, internal authorization flows, selective disclosure to regulators, issuer approval, and perimeter security. But on top of all that, they add cryptographic validity proofs that are required for every block or state transition. Even if operator keys are compromised, attackers cannot produce an invalid state transition unless they can also generate a valid proof of correct execution. In other words, ZK doesn't replace traditional security controls—it hardens them. It ensures that compromised credentials alone are not sufficient to violate system rules. Thus, even if a zero-day vulnerability were ever discovered in the ZK proving system itself, security would not collapse to zero. The system would merely temporarily fall back to the same institutional and operational safeguards used by non-ZK systems like Canton. But when ZK operates as designed, it delivers what Canton fundamentally cannot: mathematical proof that rules cannot be violated. Canton's ceiling is ZK's floor.