Our documentation has had a refresh! On http://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!
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 📜
A best-in-class developer experience must be paired with an equally good user experience, which is why we've been diving into Account Abstraction.
We loved this recent piece by
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.
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!
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:
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:
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.
📜
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!