The problem Micro Quark. solves

Why do we need a proof verification and aggregation layer:

With EIP-4844 in action, data publishing costs for rollups will decrease significantly. Ethereum has a limited gas per block, and not all (zero knowledge) verifying systems are optimized by Ethereum. Hence, proof verification on Ethereum is costly. With the increasing adoption of Zero-knowledge in web3, the significant cost would be the proof verification cost on Ethereum.

Aggregated proofs allow the verification of multiple proofs as a single proof instead of verifying them individually. With proof aggregation, multiple proofs can be verified as a single proof on Ethereum, reducing gas costs for proof verification.

Proof generation would require a lot of time and have high hardware requirements. But proof verification will take a few milliseconds.

The Quark MRU:

Quark MRU is a fast, Zero Knowledge proof(ZKP) verification & aggregation layer.

Zero Knowledge proofs will forever influence human progress, like cryptography securing the internet. ZKPs are going to secure the internet in the next decade or less.

The quark MRU will support verifying any ZKPs related to web3 or general purpose. All the proofs verified by the Quark MRU are posted periodically on Ethereum as aggregated proof.

Use cases unlocked:

Cheap and fast verification for Zero-knowledge rollups/L2s and Zero-knowledge bridges.

A generic proof verification system to build any zkDapp/zkRollup.

Interoperability for Zero-knowledge rollups.

Challenges we ran into

• Stackr is in private beta, so accessing and using Stackr for development involved a bit of debugging. But yeah, debugging is fun, as always.

• While posting to Avail DA, we missed posting a few blobs due to issues with nonce. But we started batch posting data as blobs, and it worked.