<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sneha Kumari on Medium]]></title>
        <description><![CDATA[Stories by Sneha Kumari on Medium]]></description>
        <link>https://medium.com/@audaciousSneha?source=rss-691daebab485------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_RadJMzYd3y3ssu2ZT--Dg.jpeg</url>
            <title>Stories by Sneha Kumari on Medium</title>
            <link>https://medium.com/@audaciousSneha?source=rss-691daebab485------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:43:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@audaciousSneha/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Case Study: 30 Days of Solidity by Web3Compass — Rethinking Developer Adoption in Web3]]></title>
            <link>https://medium.com/@audaciousSneha/case-study-30-days-of-solidity-by-web3compass-rethinking-developer-adoption-in-web3-4e2a5c3a96d0?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e2a5c3a96d0</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Thu, 22 May 2025 05:44:28 GMT</pubDate>
            <atom:updated>2025-05-22T05:48:34.057Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study: 30 Days of Solidity by Web3Compass — Rethinking Developer Adoption in Web3</h3><h3>Intro: From EdTech to Ecosystem — A DevRel’s Reality Check</h3><p>After three years in the space as a contributor, then a DevRel, running 40+ workshops across India, Singapore, Pakistan, Philippines, Thailand, and Indonesia for ecosystems like Ethereum, Aptos, Sui, Fuel, and Starknet, I’ve seen one thing everywhere: everyone’s struggling with developer adoption. The funny part? Most teams still call it an “<strong>onboarding</strong>” problem, like getting someone to scan a QR code at your booth is the same as getting them to build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pd7nzgrK8GxYSjiHBMrUDw.png" /><figcaption>Being on stage is my favourite thing to do! Build, Teach, Repeat</figcaption></figure><p>When I started with <a href="https://www.web3compass.xyz/"><strong>Web3Compass</strong></a>, I decided to do things differently. Sure, people mocked me — “<em>Who even uses YouTube or LinkedIn anymore?</em>” But if you want to win hearts (or elections) in India, you don’t show up speaking French. You speak the language people understand. Same goes for developer adoption: meet devs where they are, not where you wish they’d be.</p><p>With that, let’s talk about the real problem…</p><h3>The Problem: “Onboarding” ≠ “Adoption” (And No, More Pizza Won’t Help)</h3><p>Let’s face it: if developer adoption could be solved by throwing more pizza parties, mixers, and yacht bashes, every protocol would be thriving, and we’d all have six-pack abs from all the free food. But here’s the not-so-secret truth — most of these “onboarding” events pad vanity metrics. Sure, you can run 100 events and hand out enough swag to clothe a small country, but does anyone stick around after the confetti settles? Not really, and this is why most edtech platforms have now turned into event companies(No offense)</p><p>The real issue isn’t getting devs to show up once for a slice of pizza or a selfie at a conference. The issue is getting them to actually use your product, build cool stuff, and come back for more (without bribing them with t-shirts and NFTs). Many developers attend these events, learn the basics, and then disengage, overwhelmed by the complexity of the space or lacking clear next steps. The prevailing focus on short-term visibility and incentives overlooks the deeper issue: how to make developers stick, build, and grow within an ecosystem. In short, awareness is easy, adoption is hard.</p><h3>What We Did: 30 Days of Actual Building with 0 budget for incentives/marketing.</h3><p>At Web3Compass, we decided to hit the nerves; we didn’t go for cheap dopamine but to get it the hard way. No incentives, no hackathon cash grabs, no “learn-to-earn” schemes — just a good old-fashioned challenge. Enter: <strong>30 Days of Solidity</strong>.</p><ul><li><strong>Build from Day 1:</strong> No “orientation” sessions or endless keynotes. You get a challenge, you build, you repeat. Check out the entire <a href="https://www.web3compass.xyz/challenge-calendar"><strong>calendar</strong></a>.</li><li><strong>24-Hour Challenge Windows:</strong> You have one day to tackle each challenge. After that, we drop both a text and a video solution (<strong><em>yes, we made 30 YouTube videos — our editors are still recovering</em></strong>). Check out the channel here: <a href="https://www.youtube.com/@TheWeb3Compass"><strong>https://www.youtube.com/@TheWeb3Compass</strong></a></li><li><strong>No Hand-Holding:</strong> You raise a PR, you get feedback, you move on. The only thing we spoon-fed was knowledge.</li><li><strong>Public Accountability:</strong> We encouraged (<em>read: peer-pressured</em>) everyone to share their progress. Blogs, X threads, you name it. If Duolingo can guilt-trip you into learning Spanish, why can’t we do the same for smart contracts?</li><li><strong>Realistic Expectations:</strong> We knew only about 10% would make it to the end. That’s fine. We’d rather have 10 new, passionate builders than the same old faces hopping from chain to chain for the next airdrop.</li></ul><h3>The Results: Turns Out, Consistency Beats Confetti</h3><ul><li><strong>150+ joined at launch,</strong> 25 more jumped in mid-way (some with zero tech background — absolute legends).</li><li><strong>Highest streak:</strong> 27 days. No incentives, just pure, unadulterated curiosity and grit.</li><li><strong>Community Content Explosion:</strong> One participant, Shivam (<a href="https://www.linkedin.com/in/shivamkumar2002/"><strong>LinkedIn</strong></a>), wrote 30 blogs (yes, one per day), and 10+ folks religiously posted daily X threads. Who needs viral yacht parties when you have viral code?</li><li><strong>YouTube:</strong> 450+ subscribers, 7,000+ views in a month. We’re not MrBeast, but hey, not bad for Solidity tutorials.</li><li><strong>50+ PRs to be merged.</strong> Individually, it would be 600+, meanwhile, other ecosystems are still fighting over who gets to submit the prettiest GitHub repo for the Electric Capital report.</li><li><strong>Season 2?</strong> Oh, it’s coming. The DMs won’t stop. <a href="https://www.web3compass.xyz/challenge-calendar"><strong>Registrations are live on the website.</strong></a></li></ul><p>But the real win? Creativity. Grit. People are building in public, supporting each other, and learning. Not just another city tour with the same slides and selfies.</p><h3>What Participants Said</h3><p>The real impact of 30 Days of Solidity? Let’s hear it straight from the builders themselves.</p><p><em>From DMs to YouTube comments, the feedback speaks for itself — real progress, real learning, and a community that’s genuinely excited to keep building.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jI-FTxR_vG1Xu_gYJuQvaw.png" /></figure><h3>What’s Next: Beyond the Noise (and the Nachos)</h3><p>We’re doubling down. Season 2 is in the works, expanding in China, LATAM, Indonesia, and more, and this time we’re aiming to connect our new builders with real protocols and projects — actual next steps, not just another learning loop. We’ve also rolled out “Proof of Build” (case study coming soon), because why stop at one experiment?</p><p>We’ll be tracking more stats, onboarding more protocols, and yes, probably making even more YouTube videos (send coffee) and onboarding people from across the globe. An all-women community is joining us for Season 2.</p><h3>Key Stats (Because Numbers &gt; Hype)</h3><ul><li><strong>Total participants:</strong> 145+</li><li><strong>Highest streak:</strong> 28 days</li><li><strong>Pull requests to be merged:</strong> 50+(counting each day individually, it would be 600+)</li><li><strong>YouTube subscribers:</strong> 450+</li><li><strong>Forks: </strong>31 (<a href="https://github.com/The-Web3-Compass/30-days-of-solidity-submissions">https://github.com/The-Web3-Compass/30-days-of-solidity-submissions</a>)</li><li><strong>YouTube views:</strong> 7,000+</li><li><strong>Community blogs:</strong> 30+</li><li><strong>Daily X threads:</strong> 10+ participants</li></ul><h3>Takeaways (Or: Why You Should Rethink Your Next “Mixer”)</h3><ul><li>Developer adoption is a marathon, not a pizza party.</li><li>Incentives are nice, but intrinsic motivation and community are better.</li><li>Public accountability works — nobody wants to be the only one not posting their progress.</li><li>Focus on new builders, not just the usual suspects.</li><li>If you want real adoption, skip the confetti and start merging PRs.</li></ul><p><strong>TL;DR:</strong> You can keep throwing parties, or you can build something that lasts. We chose the latter — and it turns out, developers did too. Reach out to @audaciousSneha on <a href="https://x.com/audaciousSneha">X</a> or <a href="https://t.me/audaciousSneha">Telegram</a> to chat more on what’s next for Web3Compass and how we can work together :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e2a5c3a96d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Constant Chase]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@audaciousSneha/the-constant-chase-81030c49309b?source=rss-691daebab485------2"><img src="https://cdn-images-1.medium.com/max/600/1*abMr5rmsHD-1rfqZCn8i_g.png" width="600"></a></p><p class="medium-feed-snippet">It&#x2019;s a Saturday evening, I don&#x2019;t feel like working on anything right now, not prepare for that interview which is lined up, not work on my&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@audaciousSneha/the-constant-chase-81030c49309b?source=rss-691daebab485------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@audaciousSneha/the-constant-chase-81030c49309b?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/81030c49309b</guid>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Wed, 19 Mar 2025 14:35:32 GMT</pubDate>
            <atom:updated>2025-03-19T14:35:32.060Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[⁠The Hidden Cost of Dream: Notes from an Expat’s Diary❤️]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@audaciousSneha/the-hidden-cost-of-dream-notes-from-an-expats-diary-%EF%B8%8F-7aa5cc882680?source=rss-691daebab485------2"><img src="https://cdn-images-1.medium.com/max/2600/1*al49NfLnjOuB59a3BSlM2A.jpeg" width="4284"></a></p><p class="medium-feed-snippet">Experience the emotional journey of a young Indian expat in Singapore as she navigates loneliness, and the true meaning of home.</p><p class="medium-feed-link"><a href="https://medium.com/@audaciousSneha/the-hidden-cost-of-dream-notes-from-an-expats-diary-%EF%B8%8F-7aa5cc882680?source=rss-691daebab485------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@audaciousSneha/the-hidden-cost-of-dream-notes-from-an-expats-diary-%EF%B8%8F-7aa5cc882680?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aa5cc882680</guid>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[dreams]]></category>
            <category><![CDATA[expat-life]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Thu, 24 Oct 2024 17:06:59 GMT</pubDate>
            <atom:updated>2024-10-25T07:51:00.861Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Let’s Get Rusty #2: Building a Guessing Game ]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@audaciousSneha/lets-get-rusty-2-building-a-guessing-game-8d30836f5717?source=rss-691daebab485------2"><img src="https://cdn-images-1.medium.com/max/1600/1*aV2kxl_14JnZjPZefiaU3w.jpeg" width="1600"></a></p><p class="medium-feed-snippet">Hey Rustaceans-to-be!</p><p class="medium-feed-link"><a href="https://medium.com/@audaciousSneha/lets-get-rusty-2-building-a-guessing-game-8d30836f5717?source=rss-691daebab485------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@audaciousSneha/lets-get-rusty-2-building-a-guessing-game-8d30836f5717?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d30836f5717</guid>
            <category><![CDATA[rust-programming]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Mon, 14 Oct 2024 10:08:39 GMT</pubDate>
            <atom:updated>2024-10-14T10:08:39.101Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Let’s Get Rusty #1: Your First Rust Adventure! ]]></title>
            <link>https://medium.com/@audaciousSneha/lets-get-rusty-1-your-first-rust-adventure-532b60a1c590?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/532b60a1c590</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[challenge]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Fri, 04 Oct 2024 12:58:20 GMT</pubDate>
            <atom:updated>2024-10-04T13:14:00.054Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Learn Rust programming from scratch! This beginner-friendly guide walks you through writing your first ‘Hello World’ program in Rust. Perfect for developers transitioning to Rust, or anyone starting their journey in systems programming. Explore the power of Rust with our Let’s Get Rusty series.”" src="https://cdn-images-1.medium.com/max/1024/1*aV2kxl_14JnZjPZefiaU3w.jpeg" /></figure><h4>Hey Rustaceans-to-be!</h4><p>Remember that feeling when you want to post something on LinkedIn but have no idea what to write about? Well, that’s exactly how this series was born! I’ve been diving into Rust while juggling my web3 adventures (and trust me, keeping up with web3 is a full-time job in itself 😅).</p><h4><strong>Why This Series is Different 🌟</strong></h4><p>I’m writing this from the trenches — as someone who’s learning Rust right now. You know those “dumb questions” you’re too embarrassed to ask? Yeah, I’m asking them all! And those weird errors that make you question your life choices? I’m collecting them like Pokemon cards!</p><p>Want to join my journey of confusion and clarity? Hit me up on X/Telegram: @audaciousSneha (Yes, I’m living up to the audacious part! 😎)</p><h4>Let’s Build Something! 🏗️</h4><p>While I’m following The Rust Book (our holy grail), I’m skipping the installation part because surprisingly, that’s the only thing that worked first try! But if you’re stuck, remember — your friendly neighborhood Sneha is just a Telegram message away!</p><h4>Step 1: Setting Up Our Project 📁</h4><p>First things first — let’s create a folder for all our Rust projects:</p><pre><br># Creating a common folder for all our rust projects<br>mkdir rust_examples<br>cd rust_examples<br><br># Making a seperate folder inside rust_examples for hello world<br>mkdir hello_world<br>cd hello_world<br>```</pre><h4>Step 2: Creating Our First Rust File 📝</h4><p>Now, let’s create our source file. We’ll call it main.rs</p><blockquote><strong>Important Note:</strong> In Rust, when you’re using more than one word in your filename, the convention is to use an <strong>underscore</strong> to separate them. For example, use hello_world.rs rather than helloworld.rs. The file extension is .rs - that&#39;s how we tell our computer this is a Rust file!</blockquote><h4>Step 3: Writing Our First Rust Code ✍️</h4><p>Let’s write our first program. Open main.rs in your favorite text editor and type:</p><pre>fn main() {<br> println!(“Hello, World!”);<br>}</pre><h4>Step 4: Compilation and Running 🚀</h4><p>Now for the exciting part! Let’s get this code compiling and running:</p><pre># First, compile the program<br>rustc main.rs</pre><blockquote>Nerd Alert: That new ‘main’ file that appeared? It’s not just any file — it’s an executable binary! Think of it as the superhero version of your code that your computer can understand. On Windows, it’ll wear a `.exe` cape!</blockquote><p>Now we need to run the main file that was generated:</p><pre># Then run it<br>./main</pre><p>Voila, your output is ready</p><pre>// Output <br>Hello, World!</pre><h4>Let’s see what happened behind the scenes</h4><p>Now, let’s look at our tiny but mighty program:</p><pre><br>fn main() {<br> println!(“Hello, World!”);<br>}<br></pre><p>Even though it’s just two lines, there’s more magic here than meets the eye! Let’s break it down:</p><h4>1. fn main()</h4><p>This is our main function, and it’s super important in Rust. Here’s why:</p><ul><li>fn tells Rust we&#39;re declaring a function</li><li>main is a special name - it&#39;s the entry point of every Rust program</li><li>The empty parentheses () mean this function doesn&#39;t take any parameters</li><li>Your program <em>must</em> have a main function, or it won’t run. It’s that simple!</li></ul><h4>2. println!</h4><p>This is what we call a macro in Rust, and you can spot it by the exclamation mark:</p><ul><li>It’s not a regular function (that’s why it has the !)</li><li>Macros are like code generators — they expand into more code during compilation</li><li>println! specifically handles printing text to the console</li><li>The ! isn&#39;t just for show - it&#39;s how Rust distinguishes macros from regular functions</li></ul><h4>3. The Curly Braces {}</h4><p>These are pretty straightforward:</p><ul><li>They define the body of our function</li><li>Everything between them is what runs when the function executes</li><li>In this case, they contain our single println! statement</li></ul><h4>4. Extra Details Worth Knowing</h4><ul><li>The semicolon ; at the end of the println! line is required - Rust is strict about this</li><li>The double quotes &quot;&quot; contain the text we want to print</li><li>Unlike some other languages, main() in Rust doesn’t need to explicitly return anything</li></ul><blockquote>Quick Tip: If you forget any of these components, Rust’s compiler will let you know with a helpful error message. It’s like having a very direct friend who always tells you exactly what you did wrong!</blockquote><h4>Challenge Mode: Level Up Your Hello World! 🎮</h4><p>Ready to flex those Rust muscles? Here are some fun challenges to try with your Hello World program. Each level builds on what you’ve learned!</p><h4>🏆 Level 1: Personal Touch</h4><pre>// Modify your program to print your name<br>fn main() {<br> println!(“Hello, [your name here]!”);<br>}</pre><p><strong>Mission</strong>: Make it your own! Change the message to include your name. <strong>Bonus Points</strong>: Add an emoji to your message!</p><h4>🏆 Level 2: Multiple Lines</h4><pre>fn main() {<br> println!(“Hello from”);<br> println!(“multiple”);<br> println!(“lines!”);<br>}</pre><p><strong>Mission</strong>: Make your program print the greeting across three different lines. <strong>Bonus Points</strong>: Add some ASCII art!</p><h4>🏆 Level 3: Basic Variables</h4><pre>fn main() {<br> let message = “Hello, World!”;<br> println!(“{}”, message);<br>}</pre><p><strong>Mission</strong>: Store your message in a variable first, then print it. <strong>Bonus Points</strong>: Try creating two different message variables and print them both!</p><h4>🏆 Level 4: User Input</h4><pre>use std::io;<br><br>fn main() {<br> println!(“What’s your name?”);<br> let mut input = String::new();<br> <br> io::stdin()<br> .read_line(&amp;mut input)<br> .expect(“Failed to read line”);<br> <br> println!(“Hello, {}!”, input.trim());<br>}</pre><p><strong>Mission</strong>: Make your program ask for the user’s name and then greet them! <strong>Bonus Points</strong>: Add some input validation to make sure they actually entered something!</p><h4>🌟 Boss Level Challenge</h4><pre>fn main() {<br> let greetings = [“Hello”, “Hola”, “Bonjour”, “Ciao”, “こんにちは”];<br> <br> for greeting in greetings {<br> println!(“{}, World!”, greeting);<br> }<br>}</pre><p><strong>Mission</strong>: Make your program say Hello World in multiple languages! <strong>Bonus Points</strong>: Add a 2-second delay between each greeting (hint: look up std::thread::sleep)!</p><h4>Tips for the Challenges 💡</h4><ul><li>Always compile and test after each change</li><li>Don’t worry if you get errors — they’re part of learning!</li><li>Save different versions of your code as you complete each challenge</li><li>The Rust compiler error messages are super helpful — read them carefully</li></ul><h4>Got Stuck? 🤔</h4><ul><li>Check the Rust documentation</li><li>Message me on Telegram (@audaciousSneha)</li><li>Try breaking the problem into smaller parts</li></ul><h4>Show Off Your Solutions! 🌟</h4><p>Completed a challenge? Share your solution on LinkedIn or Twitter! Tag me and use <strong>#LetsGetRusty</strong> to show off your progress!</p><p>Remember: These challenges are about learning and having fun. There’s no “wrong” solution as long as your code compiles and runs!</p><h4>What’s Next? 🚀</h4><p>Stay tuned for more adventures in our “Let’s Get Rusty” series! Next time, we’ll explore something even more exciting (and probably encounter some more entertaining errors along the way)!</p><p>Remember: There are no dumb questions in programming — only opportunities to learn something new while having fun!</p><p>Until next time, keep coding and stay audacious! 🦀✨</p><p>— -</p><blockquote><strong>P.S.: If you found this helpful or just enjoyed my terrible coding puns, give it a share! Let’s build this Rust community together!</strong></blockquote><blockquote><strong>Follow me for more Rust adventures and web3 shenanigans! Also feel free to let me know how can I make this article better, or point out a mistake, if any!</strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532b60a1c590" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Not So Dreadful Monday!]]></title>
            <link>https://medium.com/@audaciousSneha/the-not-so-dreadful-monday-05807b5fd291?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/05807b5fd291</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[mondays]]></category>
            <category><![CDATA[thoughts]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[gratitude]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Mon, 26 Aug 2024 06:03:26 GMT</pubDate>
            <atom:updated>2024-08-26T06:03:26.975Z</atom:updated>
            <content:encoded><![CDATA[<p>Yet another weekend has passed. It’s a Monday morning that most people dread; the intensity keeps on increasing till we have it all figured out. But the question is, does anybody ever figure it all out? I have been watching my parents live each day with the same enthusiasm: no rest Sundays, no fear of sulky Mondays, and no mid-week blues. Or maybe they did feel all of it, but they had a bigger purpose in front of them: “Their Children.” To give them the best life, to earn for them, to make the best food, to take them on vacation during their vacations — but when did they have one?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*15tCoqYct_tjymYX" /><figcaption>Photo by <a href="https://unsplash.com/@nofilter_noglory?utm_source=medium&amp;utm_medium=referral">Tim Goedhart</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Ok, too many thoughts here. Coming back to my Monday, it is one of those days when I woke up extra motivated as if I would win the world. To be honest, I wanted to start my day earlier than this, and I could have, but the “winning the world” thought and the “lazy me” thought — where I should prioritize sleep of 8 hours — were in a debate that took me another 40 minutes. But I got out of bed finally. I opened my laptop and started coding. In the rest of the hour, I was already feeling so much better than the rest of my days.</p><p>How weird is it that one hour of deep work can give you the sense of satisfaction that you need to get going each day, but you fail to do it? Every day, at least once, I have a peekaboo session with this thought where I tell myself: “The amount of time you keep sulking and ranting about your life or waste it doing nothing but just making plans — if you make use of even 10% of the time, you would be way ahead.” But wait, ahead of what? What is this constant chase ahead? I know a lot of you must be thinking: “Getting ahead of our current self, getting better each day, blah blah!” And I agree with most of it, but have you ever taken a pause and thought, “What if there is no ahead? What if this is the best? What if the plans that the universe has for you start with this version, and it is testing you whether you live it to the fullest to deserve better, or is it that you are lost in the constant hunt?”</p><p>Distracted again! Back to my present. Once I was done playing with my code, I started thinking about whether I should go for a run or sleep a little more because I still had 2.5 hours left before I left home for the office. And with all those thoughts, one part of me says:</p><p><strong>“C’mon, you are tired already; you can go for a run at night.”</strong></p><p>But the other half is like,</p><p><strong>“Shhh! What if it makes you feel more active and happy the entire day? Don’t you want to feel it?”</strong></p><p>The first half is like,</p><p><strong>“C’mon, how long does the effect of a workout last? You are going to be sleepy all day if you work out now.”</strong></p><p>And the other half is like,</p><p><strong>“Yes, might be, but it is your choice!”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lV2Dvkit_OjAdV5n" /><figcaption>Photo by <a href="https://unsplash.com/@miracleday?utm_source=medium&amp;utm_medium=referral">Elena Mozhvilo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There it is — the “C” word, the word that, knowingly or unknowingly, defines us! I have always been anxious about making choices, but what I am proud of is I was never scared of taking the tough ones. So I did the same. I will feel sleepy or not; the day will tell, but right now it is a choice I am supposed to make. And in no time, I was in my track pants, tying my shoelace, ready for a good run.</p><p>Ten minutes later, I am already losing my breath, my legs hurt, and my heart is pounding so fast that I could literally hear my heartbeat. “Let’s go back,” my mind said. “Oh wait, no!” the other part of my brain screamed. “Push yourself; people who push themselves are the ones who win.”</p><p><strong>“Win what?” </strong>the other half questioned.</p><p><strong>“Ummm, something I don’t know.”</strong></p><p><strong>“Ughhhh, shut up, you both!”</strong> Three deep breaths and I find myself running again. One complete round done; now I need to reward myself with coffee, I thought, and this is one point where both halves of my brain are in sync.</p><p>I start walking, and here I am amidst a field that I need to cross before I reach the hawker center. A gush of wind touches my face. I take a long breath, look around, and in that one moment, I feel: “Can it get better than this? This life, parents, a job that pays my bills, living abroad one year after graduation, an amazing set of friends, good coffee in the morning, and dreams to work for each day. How can it get better? Why does it have to get better? This, in this moment, is perfect. This life!”</p><p>I look at the sky, smile, and say it out loud: <strong>“Thank you, Universe, for being there even when I thought I had no one to listen to me. Thank you for giving me more than I could imagine, and I cherish it. Sorry if I wasn’t grateful enough,</strong>” and the sky seems to be smiling back at me.</p><p>I get my coffee, play my favorite music, and start walking back to my place, ready to face the not-so-dreadful Monday! I might be wrong, or a lot of you might not agree with my thoughts, but all I am doing is penning down my thoughts here because this is indeed a good morning! <br>Have a great Monday, you guys!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6KQW8uyOXMF8oGNq" /><figcaption>Photo by <a href="https://unsplash.com/@pablodelafuente?utm_source=medium&amp;utm_medium=referral">Pablo de la Fuente</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05807b5fd291" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deep Dive into Account Abstraction:)]]></title>
            <link>https://medium.com/@audaciousSneha/deep-dive-into-account-abstraction-3d682057e11d?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d682057e11d</guid>
            <category><![CDATA[account-abstraction]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Tue, 16 May 2023 18:19:58 GMT</pubDate>
            <atom:updated>2023-05-16T18:19:58.609Z</atom:updated>
            <content:encoded><![CDATA[<p>The word Abstract or Abstraction in itself sounds like a heavy concept. In the English Language, abstraction is defined as the feature or quality of formation of specific ideas by mental separation from instances or material objects. Leaving the very eloquent definition to those who are interested, let us talk about abstraction in simple terms. For the concern of software enthusiasts and developers, abstraction is the most fundamental concept of hiding the complexity behind building an application or an ecosystem. By the technical definition of abstraction, it is relatively easier to understand the convenience of any kind of technology. Owing to abstraction, the complex details that constitute the functioning of a technology is hidden away and a simplified interface is provided to the users. The avoidable complexities of the inner workings of the software makes it easy for a wider range of people to access and benefit from it. For instance, from a seven year old kid to an eighty five year old granny all can use the Internet with convenience.</p><p>Abstraction is not a new concept for the Internet. In Web1 as well as Web2, abstraction has been a prevalent feature. The vastness and widespreadness of the Internet are thanks to its accessibility and user-friendliness. A typical internet user, while sending an email, is unaware of the process of breaking down the message to be received as signals and then reassembled at the receiver’s system. The design of the internet makes use of abstraction to support its customer base. Thus, learning and getting inspired from already proven features of Web1 and Web2, developers in the blockchain ecosystem have come up with ways to implement abstraction for a smoother transition from web2 to web3.</p><p>In Ethereum, accounts are how a user is represented on the blockchain. An account can make transactions and interact with other accounts or users on the blockchain. There are two types of accounts in Ethereum:</p><p>· Externally owned accounts(EOAs) — These accounts are created with public private key pairs. The private key can be understood as a pin code of a debit card while the public key is like a bank account number. Thus, with a public key, ethers can be sent to an account but to initiate transactions, a private key is required.</p><p>· Contract Accounts — These accounts are controlled by a piece of code known as smart contracts. However, contract accounts need EOAs to be deployed on the network or to initiate transactions.</p><p>After understanding the account structure in Ethereum, we can conclude a few problems that arise:</p><p>· Contract accounts cannot initiate new transactions on their own.</p><p>· EOAs raise a concern of security as the wallet access cannot be recovered without a seed phrase (like a secret key).</p><p>· Public private key pairs in EOAs create a single point of failure. If a private key is lost, the access to the account is lost or it can be mishandled.</p><p>To overcome such shortcomings, abstraction or more specifically Account Abstraction, can be implemented to enhance the efficiency offered in the management and behavior of Ethereum accounts. Knowing the two types of accounts, implementation can be done by either updating EOAs to be controlled by smart contracts or upgrading smart contracts to initiate transactions. A combination of the features of the two is a single account type that can carry out the transactions while creating contracts all the same.</p><p>ERC-4337 is a mature proposal that brings smart contract features to wallets. Changes in Ethereum protocols come about by deploying new standards on the Ethereum mainnet. ERC or Ethereum Request for Comment is one such proposal that sets contract and token standards. ERC-4337 is the latest standard on Ethereum which achieves the goal of account abstraction. It was proposed by Ethereum co-founder Vitalik Buterin in 2021 and launched in 2023 to improve user-experience of crypto-wallet designs. A distinctive feature of ERC-4337 is that it provides decentralized wallet support without enforcing any changes to the Ethereum consensus layer.</p><p>The Ethereum protocol is an account-based model i.e., the protocol keeps track of all the account transactions, balances, and the like. In Ethereum, EOAs are controlled by users while contract accounts are controlled by smart contracts. Most crypto wallets active on Ethereum are EOAs. They function with no flexibility of their own and their setup is limited to the rules binding EOAs. The security measures of these wallets are troublesome for the users. If the seed phrase(like a secret phrase) is lost by the user, the wallet access is lost beyond recovery. ERC-4337 allows management of wallets by smart contract accounts instead of EOAs that achieve the same goal as before but with better efficiency.</p><p>ERC-4337 introduces a higher-layer concept known as UserOperation. UserOperation is a pseudo-transaction object that enables account abstraction. Many users can submit their UserOperation objects to a separate mempool. (Mempool : It is a list of transactions that are yet to be validated on the blockchain). Bundlers then come into play. A Bundler is a node that does a very similar job to the block “Builder” . They collect the UserOpertion objects and create the most profitable bundle that is signed, which is then included in the block. Bundlers are compensated for their service via the fees received from individual UserOperation executions. Moreover, we see a global wallet contract known as Entry Point being introduced. It handles the operations such as paying fees, preventing unauthorized access, execution of EVM code so that developers can focus on providing excellent user-experience.</p><p>Having account abstraction implemented on the blockchain, users can enjoy the benefits of Ethereum without knowing or caring about the underlying technology. We get the required support to make crypto wallets more flexible by using custom logic in smart contracts to handle the wallets. Normally, wallets are protected by a private key which is generated from a seed phrase assigned to every account. This seed phrase if lost cannot be recovered or can also be the cause of scams if it is lost for some unfortunate reason. To avoid that, smart contracts can be used to customize the security of the wallet. On the outside, the wallet is still handled by private key but with several layers of safety. Solutions like account recovery and whitelists can be instated using smart contracts. Account abstraction leads to better user-experience and improved security. More and more complex logic can be used behind the scenes to implement features that make transactions on the chain easier and secure thus allowing more users to join the ecosystem.</p><p>Overall, abstraction plays a crucial role in simplifying the use of technology. With the introduction of account abstraction in Ethereum through ERC-4337, wallets can now be managed by smart contracts, improving security and user experience. By abstracting away the complexities, more users can participate in the ecosystem, making it accessible to a wider audience. Developers building the ecosystem work with one focus in mind, security and more access to the users. ERC-4337 establishes a foundation of creative crypto wallets that can be formulated per users’ needs. With the flag of decentralization being upheld, it is safe to say that more developments in the path of convenient technology is upon us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d682057e11d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“The Push and Pull of Push Protocol: A Comprehensive Analysis”]]></title>
            <link>https://medium.com/@audaciousSneha/the-push-and-pull-of-push-protocol-a-comprehensive-analysis-5c791c095d75?source=rss-691daebab485------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c791c095d75</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[push]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Sneha Kumari]]></dc:creator>
            <pubDate>Tue, 25 Apr 2023 15:21:32 GMT</pubDate>
            <atom:updated>2023-04-25T15:21:32.272Z</atom:updated>
            <content:encoded><![CDATA[<p>“The Push and Pull of Push Protocol: A Comprehensive Analysis”</p><p>Web3 is idolized as the new up-and-coming technology, a digital revolution. The days of entrusting your data to faceless storage entities are a part of old news, equally and more crucial to the developments. Now, you can own your data. As even history is witness to the boom of democracy and self-governance, the technical space is progressing with a similar flow. The proof of the tireless hard work of developers all over the world are <strong>protocols</strong> that are offered on different <strong>blockchains</strong>. A blockchain, simply put, is a common database distributed between a group of nodes(computers/end points). The changes that occur in this database happen with the consensus of the nodes. The protocols of a blockchain make the operation of services and interactions between computers on the chain easier and more understandable. While the Web3 space is constantly evolving, a need was seen for a service that would send notifications to the users of a particular chain. These notifications will relate to different <strong>dApps </strong>hosted on the chain. dApps are decentralized applications i.e., owned and managed by a community, unlike the traditional way of being curated by a single entity.</p><p>Pushing notifications has already been a strategy for web2 applications to send information and retain their user base. But in Web2, users do not have control over the notifications they wish to receive. Imagine figuring out a way beyond this shortcoming using Web3. That is what a team in EthGlobal 2020 did with all its might.</p><p><strong>Bridge for Web3 Communication:</strong></p><p>The need for open communication in Web3 was first realized by a team of two Web3 Builders, Harsh Rajat and Richa Joshi, in 2020. As a part of EthGlobal Hack Money, 2020, EPNS was ideated. EPNS, Ethereum Push Notification Service, is a protocol that sends notifications to all potential users of different dApps on the Ethereum Blockchain. App Owners using EPNS can send <strong>mass unencrypted</strong> notifications or <strong>targeted messages</strong> to specific encrypted users for data protection. Notifications can be sent via the web, mobiles(push notifications as in Web2), and Web3 providers such as Metamask. Some terms used in EPNS can be broken down as such:</p><p>· Contract Owner- The address by which the contract is deployed on the chain.</p><p>· App Owner- The third-party projects, dApps, and smart contracts that want to send notifications to their users. Moreover, the address from which the users will receive the messages.</p><p>· Users-Everyone who does not own a contract or a third-party project falls under Users.</p><p>· App Owner Group- Like we see channels on a YouTube page, these groups also hold users subscribed to any particular channel.</p><p>· Subscribed Users- Users who have subscribed to a channel are called Subscribed Users.</p><p>Consistency has proven to be the key in this instance. What ideated as an abstract for a 30-day virtual hackathon became a ground-breaking service to bridge the gaps in web3 communication.</p><p><strong>Network, which brings about the communication:</strong></p><p>Before EPNS, although notifications by a Web3 provider were possible, there was no notion of a smart contract or dApp notifications. This was made possible by EPNS with the help of push nodes. <strong>Push nodes</strong> are a network of nodes, with each node having to play a different role in the network. They are responsible for validating and handling the communication between wallet addresses. These nodes have the essential role of listening to any events occurring in the smart contracts and triggering the broadcast of notifications.</p><p><strong>Incentivization of the EPNS project:</strong></p><p>The growth of a web3 ecosystem relies highly on governance and incentives. $PUSH is the native token of the EPNS Protocol. Push tokens are used to incentivize the activities in EPNS protocol, such as subscribing to a channel or even receiving a notification. Services such as dApps and smart contracts have channels to which the users subscribe to receive notifications. Everyone who participates in the protocol, as a user, token holder, channel owner, and others, benefits from the growth. At the time of writing, the value of a $PUSH token is worth $0.41.</p><p><strong>Use Cases of EPNS:</strong></p><ul><li>DeFi:</li></ul><p>Decentralized Finance or DeFi applications can use EPNS, where notifications can be useful to alert the users when their stakes will be liquidated so that they do not have to keep checking on it again and again. EPNS also offers its own cryptocurrency called $PUSH. Those who hold these tokens also have a say in the future of the protocol, and the roads to development that it can take. This is called Governance Rights.</p><ul><li>Use of notifications in NFT Marketplaces:</li></ul><p>NFT, Non-Fungible Tokens, give you ownership over collectibles such as music, art pieces, videos, etc. NFT Marketplace becomes one of the evident use cases of decentralization where users can trade i.e., sell or buy NFTs. For a trader, real-time updates on one’s NFTs are valuable. A trader might be interested in an NFT that gets sold out without him knowing or the launch of a new NFT might go unseen if not prompted. Here EPNS can work as a medium to inform the user in real time about the activities of the NFTs. For instance, when it is put up for auctions when the last of it is remaining for the final grab, the alterations in price which allows users to strategize how to trade and situations alike. Users can subscribe to the NFT creators and be alerted about new developments.</p><ul><li>Chatting:</li></ul><p>In Web2, we see push notification services as a way of alerting users about updates on specific applications. Many users chat with different other users on the same application via notifications. Thus, in the Web3 ecosystem, a gradual progression after push notifications is a platform that allows two wallet addresses to communicate messages with each other. Unlike traditional messengers that need personal data for user sign-up, a wallet address is all that is needed for safe and encrypted communication.</p><p><strong>Push Protocol — Rebranding of EPNS:</strong></p><p>Push Protocol, the next evolution in web3 communication, is built on the EPNS mainnet, which has been running for over a year. The EPNS mainnet is described as the primary blockchain that powers the protocol. This mainnet is where the channels and subscribers reside, and this space is where the decisions on a protocol’s future are taken. As Push is an open communication solution, the contributors have equal and more say on its progression.</p><p>The rebranding of EPNS as Push Protocol was a discernible milestone that signified the upscaling of the services that the company wanted to provide. It signified the service&#39;s move to chains other than Ethereum, which currently include Polygon and BNB. The rebranding assures the addition of expansive services of communication while also offering the existing facilities. This move was to make Push Protocol a communication protocol that evolves with the changing environments and can meet user&#39;s needs and expectations even more flexibly.</p><p><strong>Push Protocol on different chains:</strong></p><p>The step of opening Push to multi-chain was taken by launching Push on Polygon’s mainnet. Developers with dApps on Polygon can seamlessly integrate Push into their applications to improve user experience. Moving to Polygon can also be seen as a smart move for Push Protocol since Polygon is the go-to platform for web2 institutions such as Meta, Adobe, Starbucks, etc, to onboard with web3. dApps built by such corporations can use the services offered by Push to optimize the ability of users to have direct control over the messages they want to receive.</p><p>The launch of Push on BNB was also a welcomed upgrade for the developers. dApps on BNB can now integrate Push for an enhanced communication interface. Push on BNB was launched with its latest implementation of features in Push Protocol v1.5. The v1.5 includes:</p><ul><li>Increasing the use and importance of PUSH:</li></ul><p>Previously, channel creation needed some DAI to be staked by the creators. The new version revokes this need. All transactions like the creation of the channel, subscription, channel activation, etc will be done using $PUSH.</p><ul><li>Allowing upgrades on channels:</li></ul><p>Generally, repeated updates on channel details are not allowed since a malicious channel owner can give wrong updates on a channel which might confuse the subscribers. As the community demanded it, this feature was added with a preventive measure of depositing a fee before editing the channel details.</p><p>Fee Pool:</p><p>The Fee Pool is a concept where some fee is deducted by the primary smart contract for transactions such as channel creation, channel updates and such, and the fee is then used for incentivizing the PUSH token holders and users.</p><p><strong>Push Chat — An expansion of communication boundaries:</strong></p><p>Push Chat is a secure messaging protocol built by Push Protocol. Push Chat is a major step in realizing the vision of decentralized web3-native messaging. It enables secure wallet-to-wallet messaging between any addresses on the chain, including but not limited to file sharing and video calls. It works to provide permissionless wallet-to-wallet communication, spam prevention, and a user-friendly interface. The seamless addition of the UX/UI in existing dApps is made easier with the SDKs available on their developer ground. Push Chat uses IPFS, encryption, and pinning of the messages on Push Nodes to enable a seamless, no-message drop experience for the user. Each message (and notification) carries a verification proof which the front-end can use to determine that the message content and sender are actually the ones that sent these messages out. In addition, Push Group Chat allows web3 users to create group chats, and online communities, come together, and share experiences natively on web3. A wallet can create up to 10 groups which can be public or private. To enhance the chat experience, you can use your ERC20 tokens or certain NFTs to gate your group.</p><p>Conclusion: EPNS, now rebranded and thriving as Push Protocol, started as an idea to bring some familiarity to the web3 users by adding a feature very prevalent in web2 i.e. push notifications. Its addition to the ecosystem proved to be a new era of communication; a development that would form the base of the future internet. With an intricate network layer at its core, the service it has been providing and continues to do so is impeccable and endorsed by various entities across chains. With the amazing developers working behind Push, we are yet to see more and more features that will boost web3 native communication to the next level.</p><p>References:-</p><ol><li><a href="http://www.medium.com/">www.medium.com</a></li><li><a href="http://www.push.org/">www.push.org</a></li><li><a href="http://www.businessinsider.in/">www.businessinsider.in</a></li><li><a href="https://blog.logrocket.com/exploring-epns-dapp-notification-system/">https://blog.logrocket.com/exploring-epns-dapp-notification-system/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c791c095d75" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>