Thread by @zksync

Ethereum is a dark forest. Immutable smart contracts, financial incentives, and anonymity create an environment that forces us beyond standard security practices. Here’s how you onboard a billion users without compromising security. #securingthemission

1/7

The complexity of building a zkEVM includes the possibility of low-frequency bugs with big impact potential. That’s why zkSync has many layers of protection built into the system. Some of these security layers will fade out as the protocol moves toward full decentralization.

2/7

Instead of relying solely on one security measure, such as zero-knowledge cryptography, we implement multiple layers of protection, known as the "defense-in-depth" or "Swiss cheese model," to prevent and minimize the impact of potential breaches.

3/7

We started by implementing as many security features as we could, including centralized options such as emergency protocol freezing, a list of onboarding projects, and the ability for instant upgrades.

4/7

As trust in the system grows, zkSync will gradually reduce reliance on Matter Labs and eliminate centralized security features. For example, features like instant upgradeability will be transitioned to a decentralized security council formed of Ethereum-aligned individuals.

5/7

An example of how we phase out the security precautions is the roadmap to zkSync 2.0 Full Launch Alpha:

Phase 1: Baby Alpha (nobody but Matter Labs can interact)
Phase 2: Fair Launch Alpha (someone can interact)
Phase 3: Full Launch Alpha (everyone can interact)

6/7

Ultimately, the only forms of protection will be mathematical algorithms, computer code, and the support of the community. The security of zkSync is the responsibility of Matter Labs today, but in the future, the community will be the gatekeepers of the protocol’s security.

7/7