We’ve spent $3.5M+ on audits, bug bounties, and contests to secure zkSync 2.0 — but there’s no such thing as too secure. Here are some added security measures we’ll take once zkSync 2.0 is open to the public.
1/6
1/6
We’re limiting the early flow of funds, which ensures that developers have an adequate amount of ETH for contract deployment and testing transactions while minimizing the risk of losing a large amount of value during the early stages of the system.
2/6
2/6
We’ve got a “speed bump” measure in place too — restricting withdrawals to 10% of TVL per day, limiting the consequences of any security breach. This way, we can respond quickly, stopping the attacker from completely draining the system's resources.
3/6
3/6
But all of this is pointless if we can’t respond quickly. For a quick response, we’re using @OpenZeppelin's Defender; a comprehensive monitoring system with alerts and automatic responses for critical situations.
4/6
4/6
All these security measures are made to protect projects and users during the network’s early stages. Full Launch Alpha is around the corner so we’re doing everything we can to safeguard funds. It’s our top priority.
5/6
5/6
Want to know more?
Check out last week’s #securingthemission where we walk through the delicate balance between multi-layered security, trustlessness and gradual decentralization.
6/6
Check out last week’s #securingthemission where we walk through the delicate balance between multi-layered security, trustlessness and gradual decentralization.
https://twitter.com/zksync/status/1617916959139696642?s=20&t=hTre-ZSLHcQ3ChH-fvKBmg
6/6
• • •
Missing some Tweet in this thread? You can try to
force a refresh
