I’m excited to share ZKsync’s 2025 technical roadmap with the broader community.
This is a group effort between the various teams building the elastic network, including governance. Please give this a thorough read and share your thoughts on our 2025 product focus.
As the founder, I think now is a great moment to reflect on our journey and outline the priorities for 2025 to ignite a meaningful discussion for the upcoming year. I look forward to your thoughts and comments.
Extremely curios how ZKs architecture will evolve in the current web3 landscape and how it will differentiate itself from the major L2s.
As a neutral delegate I hope we can all play a smol role in the discussions and help steer ZK towards the path of mutual collaboration with the EVM family.
Thanks for the reply! I appreciate the resources you shared, but I’m actually looking for more technical details specifically around the zk gateway. I want to understand how communication will actually happen under the hood, the role the zk gateway plays, and what new zk circuits or architecture are being implemented to enable faster communication between elastic chains—especially if it’s meant to be quicker than the usual Ethereum block times.
Any additional technical documentation or deep dives on the zk gateway setup would be super helpful!