Trust me, no matter how many hackathons you’ve crushed, this blog’s got something new for you. If not, well, you’ve learned not to trust a stranger on X. Either way, you’re learning something! So go on, check it out: <pranshurastogi.medium.com/how-to-get-the-most-out-of-a-web3-hackathon-tips-tricks-b4f7d96b6abe>
📢 Lens fam! Never miss a beat again! 🕺💃
Get your Lens updates zapped straight to your brain (okay, just your device) with Push Protocol! 🚀📱
Opt in now and stay in the loop: <app.push.org/channels/0xef6426D522CfE5B7Ae5dB05623aB0Ef78023dBe0>
Hello Everyone !!
As the year is about to end, I have tried something new for me.
Tried creating 2 videos on Ecosystem and DevRel role in web3. Do check it out and your love ❤️ and feedback are highly appreciated.
👉 DevRel: [youtu.be/bIiewuAYo3Y?si…]
👉 Ecosystem Role: [youtu.be/TkXput4WxyA?si…]
zkSNARKs VS zkSTARKs 💪🏼
👉🏻 The intent of this post is not to tell you which is better but to create awareness of their properties so we can make a better choice while developing.
🤷🏼♂️I know a few terminologies over here might confuse you, like Trusted setup, toxic waste. So, refer to this blog to learn more: pranshurastogi.medium.com/mastering-zokrates-ethereums-privacy-toolkit-part-2-d12f0270771d
Please comment on the topic you are interested in; I'll try my best to simplify and make more resources around the same. 🙏🏽
Have you heard of Zero Knowledge Acronyms❓ It's important to familiarize ourselves with them and fill in any missing ones from the list. Additionally, let's take a moment to learn a brief one-line description of each.
-
CRS (Common Reference String): A common reference string is a shared parameter used in cryptographic protocols that ensures the consistency and security of the protocol.
-
ECC (Elliptic Curve Cryptography): ECC is a type of public-key cryptography that utilizes the mathematics of elliptic curves to provide secure communication and encryption.
-
NIZK (Non-Interactive Zero-Knowledge): NIZK refers to zero-knowledge proofs where the prover can convince the verifier of the truth of a statement without revealing any additional information.
-
PCP (Probabilistically Checkable Proof): PCP is a method of proof verification where a small, random subset of a proof is checked probabilistically to determine its correctness.
-
QAP (Quadratic Arithmetic Programs): QAP is a mathematical representation of computation that involves quadratic polynomials and is often used in zero-knowledge proof systems.
6. QSP (Quadratic Span Programs): QSP is a variant of Quadratic Arithmetic Programs that provides more flexibility and efficiency in constructing zero-knowledge proofs.
-
RISC (Reduced Instruction Set Computer): RISC is a type of computer architecture that uses a small and fixed set of simple instructions to improve performance and efficiency.
-
SNARG (Succinct Non-Interactive Argument): SNARG is a zero-knowledge proof that allows a prover to convince a verifier of the validity of a statement in a concise and non-interactive manner.
-
ZKP (Zero-Knowledge Proof ): ZKP refers to a cryptographic proof that allows one party to prove knowledge of a statement to another party without revealing any additional information.
Do comment if you know more. Also, if you want to learn about ZKP and ZoKrates, check out my Medium account:
LIVE 📣 PART 2 “Mastering ZoKrates: Ethereum’s Privacy Toolkit”
pranshurastogi.medium.com/mastering-zokrates-ethereums-privacy-toolkit-part-2-d12f0270771d
🔈Hello, everyone !! Tired of oversharing your data on the blockchain? It's time to add an invisibility cloak with the power of zkSNARKs and ZoKrates.
Part 1 of the series is "Mastering ZoKrates: Ethereum's Privacy Toolkit."
Feedback will be highly appreciated,
Stay tuned for the remaining part of the series.
pranshurastogi.medium.com/mastering-zokrates-ethereums-privacy-toolkit-part-1-dc91e6245cfc
3k+ audience learning about communication in web3.
Probably Nothing
Have you ever considered what you should include in a README? What does a perfect repo and Readme look like? As a BUILDER, it's very essential for us. Tag your friend who should read this or who participates in the hackathon -
1/ Project Description: A brief rundown of the project, including what it does, why it's special, and any cool tech it uses. Think of it as the project's dating profile .
2/ Installation Instructions: A step-by-step guide on how to set up the project, including any necessary "prerequisites" or "fine print." Think of it as the project's first date.
3/ Usage Instructions: A comprehensive guide on how to use the project, including any fancy tricks or hidden features. Think of it as the project's how-to manual.
4/ Screenshots or demos: A visual representation of the project in action, like a movie trailer or a music video. Think of it as the project's portfolio.
5/ Licensing Information: A legal disclaimer on how the project can be used, distributed, or modified. Think of it as the project's birth certificate.
6/ Contact Information: Need to get in touch? Contact information, is a way to get in touch with the project's creators, like an email address or social media handle.
7/ Changelog: Want to know what's new? Changelog a list of updates, bug fixes, and new features, like a diary or a scrapbook .
8/Roadmap: Future plans? Roadmap, a list of upcoming plans, future goals, and new ideas, like a bucket list or a vision board