In order to make zkSync 2.0’s exclusive features more easily accessible to developers, we’ve released new SDKs in Java, Python and Go. Details below 🧵 #scalingthemission
(1/4)
Expanding the programming languages our SDKs are available in enables us to support a broader range of use-cases – like mobile or hardware-specific applications – from development teams building on zkSync 2.0.
We will continue to expand our SDKs into other languages and are eager to see the growing list of innovative projects building on zkSync 2.0. Comment below to let us know what other languages you’d like to see SDKs for.
(4/4)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
The mission continues. Friday was a historic moment for Ethereum scaling, but we’re not slowing down, and projects continue to join the zkEVM revolution by launching on our platform. Here are another five updates from our fast-growing ecosystem. #jointhemission
🧵(1/7)
@MEXC_Global announced that they now support ETH deposits and withdrawals via zkSync.
@ZigZagExchange explained why zkSync 2.0 has got everyone talking, and why our cutting-edge technology will change the industry in ways we've never seen before.
Baby Alpha is here! We are proud to announce that today we hit our Baby Alpha milestone and have begun the march to Fair Onboarding Alpha and Full Launch Alpha.
There are only 7 days to zkSync 2.0 on mainnet. We will be releasing SDKs in a few languages and we'd love your feedback on which other languages you want available. Quote tweet us if you want to help contribute. #1000truedevs
(1/4)
Aside from the most basic and expected Javascript (Typescript) SDK, we will release SDKs in Rust, Java, Swift, Go, and Python. Why is this important? RT and share your feedback below. #1000truedevs
(2/4)
As Layer 2 evolves, we'll see more use-cases, go beyond browser-based dApps and see a rise in mobile native dApps and dedicated hardware for specific apps. What innovative dApps do you want to see in our ecosystem? RT and share your feedback below. #1000truedevs
Will you be attending Lisbon Blockchain Week 2022? We are, and can’t wait to connect with you in Lisbon, Portugal.
Where you will find us 🧵(1/5)
@ETHLisbon Hackathon (Oct. 28- 30th | Academy of science)
ETHLisbon is an Ethereum-focused hackathon bringing together the best Web 3.0 builders. Join us for 3 days of non-stop building and sign up for our bounty, which is open to everyone.
There are only 10 days remaining on the #marchtomainnet. Yesterday we achieved a significant milestone, integrating our provers into the system and achieving an end-to-end system running on testnet.
But why do we need a prover? 🧵 (1/5)
To inherit layer 1 security, there must be a way that we can reconstruct the layer 2 state transitions directly from Ethereum. Differently from optimistic rollups (that rely on game theory), zkRollups rely on pure math to attest that state transitions are valid.
(2/5)
On our L2, a set of contracts will organize the transactions into batches & generate proofs for them. Those proofs are sent to a smart contract on L1 to verify that they are valid, ensuring that no transactions inside a batch were altered or contained invalid information.
Today, we’re extremely excited to announce that we have successfully completed Milestone 3: Proof Merging. With the integration of validity proofs, zkSync 2.0 is officially the world’s first-ever zkEVM running on a public testnet.
Many dev teams have been waiting for this: public verification of the validity proofs generated by the rollup & the final piece for the Alpha version of the system. As users transact with zkSync 2.0, these proofs provide a guarantee of the correctness of program execution.
(2/5)
We’ve had fully functional circuits in our dev environment for a while, but this milestone will enable everyone on our testnet to experience our ZK Prover which is fully operational with proof generation, aggregation & verification on-chain happening on the public testnet.