Opens profile photo
Follow
Scroll 📜
@Scroll_ZKP
The native zkEVM | Join us on Discord: discord.gg/scroll
linktr.ee/scroll_zkpJoined February 2021

Scroll 📜’s Tweets

Our documentation has had a refresh! On guide.scroll.io, you'll find: - User documentation - Faucet, bridge, and rollup details - A brand new developer guide - Contract deployment tutorials - Existing integrations We can't fit it all in a tweet, so go explore!
Image
27
568
That's all we have to share for this week! As always, thanks for supporting us as we build the future of L2 in the open, together. Have a good weekend 📜
8
121
Show this thread
We made a lot of improvements to our ZK architecture, lowering our prover memory requirement from 870GB to 275GB, nearly a 68% improvement. Getting our system requirements as low as possible allows for the democratization of the decentralized prover network.
8
207
Show this thread
Systems are being set up and prepped for future deployment on Goerli. More details Soon™ We've also made progress on an improved v2 bridge design which should result in a smoother experience!
Embedded video
GIF
2
94
Show this thread
For nearly two years, we've been heads-down building a bytecode-compatible zkEVM in public. Today, we're increasing that transparency even further by introducing regular weekly updates. Here's what we were up to this week:
24
723
Show this thread
Giving back to the ecosystem is essential, which is why we participated in the Alpha Grants Protocol funding round, which focused on funding Ethereum ecosystem development and open-source software. Here are the projects we picked to support this round:
7
348
Show this thread
Following our successful Temperature Check with the Uniswap DAO, we're eager to get feedback from the community and continue 's mission of bringing financial applications to as many people as possible.
3
116
Show this thread
Many open optimization problems in the ZK space remain, and we're continuing to push the boundaries by perpetually iterating and improving all aspects of our design. 📜
4
154
Show this thread
After a batch is filled, the batch's data is submitted to L1. From here, a prover submits a proof for the batch, and then the set of blocks corresponding to the proof is verified. This allows for more efficient use of prover resources, especially when blockspace demand is low!
3
113
Show this thread