Just received my first Web3 swag, and it’s from @Alchemy !!!🤩. Always wished for this, and it truly means a lot! Huge thanks to @angelinarusse for the swag, and the positivity you spread every day!!💙. Feeling incredibly grateful and hoping to work with the amazing team soon!!✨

The ZK revolution isn't just about scaling transactions; it's about scaling trust. By fusing Ethereum's strong identity with computational privacy, we can finally scale with privacy, building an ecosystem on trust. It’s not just scaling. It’s scaling with privacy. 🔒.

A perfect example is @aztecnetwork 🟪. Their design has you create a proof on your device (client-side), which is then bundled by a powerful network of Provers. The goal is to decentralize this network for a truly censorship-resistant L2.

This raises a crucial question: Who actually generates the ZK proof? 🤔. If one entity does all the heavy computational lifting, they could potentially censor users. This is the core decentralization challenge that all serious ZK systems must solve.

Benefit 2: Saving Gas ⛽. Verifying a signature involves complex math. By doing this in a ZK circuit, all the heavy lifting happens on your own machine (offchain). The smart contract onchain only needs to perform one, simple, and much cheaper task: verifying your tiny ZK proof.

Benefit 1: Confidentiality & Privacy 🔐. This is the biggest win. You can prove you have the authority to do something without revealing your specific address. Your onchain actions are decoupled from your public identity.

So, here is the key difference:. 🔷 Solidity ecrecover: Runs ON-CHAIN. Verification is PUBLIC. The contract sees your identity. 🔷 Noir ecrecover: Runs OFF-CHAIN. Verification is PRIVATE. The contract only sees a "thumbs up" proof.

Inside the ZK circuit, the Noir code defines a set of constraints. It proves a statement is true without revealing the inputs. The assert line is the most important part. It ensures the final output the "ZK proof" is only valid if the check succeeds.

The ZK solution? Go private. Instead of public verification, you prove your signature's validity inside a ZK circuit, a "private room." . @NoirLang is the language for the instructions, and libraries like ecrecover-noir provide the blueprints.

This total transparency is a problem for privacy❌. You don't always want your signature on every document to be visible to the world. Imagine if every contract you ever signed was posted on a public bulletin board with your name attached. That's how the public blockchain works.

Solidity's ecrecover is a precompile, meaning it's a fast and standard on-chain function. Any contract can use it. But the key is that the verification happens out in the open. The signed document and the identity of the signer are public knowledge. 🗣️.

Now, what is ecrecover?. Think of it as a handwriting expert. It looks at a signed document and compares it to the public ID card. It can definitively say, "Yes, the person with this public ID is the one who signed this.". It recovers the signer's identity. 🔍.

When you "sign" a message in crypto, you're using your unique handwriting (private key) to sign a specific digital document. This creates a unique Signature. It's mathematical proof that you, and only you, approved that specific document. 📝.

Let's start with a simple analogy for an ECDSA signature. 🔷 Your Private Key is your unique, personal handwriting. Only you can produce it. 🔷 Your Public Key is like your signature on a public ID card. Anyone can see it to verify against.

How does a smart contract know it's really you?. Through your ECDSA signature. The tool it uses is called ecrecover library. But this process is totally public. What if we could prove who we are privately?🤫. Let's explore how we do this with Zero-Knowledge proofs. 🧵.

Day 80 of #100DaysOfCode . Started Section 3: ZK Pangram from @CyfrinUpdraft of Noir and ZK circuits course. Refreshing the core ZK concepts along the way!!

ZK all the things.

Day 79 of #100DaysOfCode . Revisited ECDSA, ecrecover, signature malleability, and how ZK proves offchain and verifies onchain. A recap to let it all sink in!!.

Day 78 of #100DaysOfCode . Learned about ECDSA, ecrecover, and signature malleability from @CyfrinUpdraft. Built ZK ECDSA circuit that proves a signature without revealing who signed it!. Huge thanks to @CiaraNightingal , ZK is getting more interesting!.

Built a ZK ECDSA circuit using @NoirLang - ecrecover library👽. Proves someone signed a message without revealing who, what, or how. That's ZK magic 🔐. Verified the proof offchain, and generated the Solidity verifier contract for onchain verification. Thanks to @CiaraNightingal

Privacy isn't a feature. It's a basic human need!!. Not everything onchain needs to be visible to everyone, all the time. @aztecnetwork is building a world where privacy is the default - not the exception. And that matters. A lot!!.