<?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 Humble Lee on Medium]]></title>
        <description><![CDATA[Stories by Humble Lee on Medium]]></description>
        <link>https://medium.com/@Humblelee71?source=rss-479ef29b935f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IB5NRw1lRAjCi8OobqyFUg@2x.jpeg</url>
            <title>Stories by Humble Lee on Medium</title>
            <link>https://medium.com/@Humblelee71?source=rss-479ef29b935f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:10:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Humblelee71/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[Why Most Pitches Get Ignored (And It’s Probably Not for the Reason You Think)]]></title>
            <link>https://medium.com/@Humblelee71/why-most-pitches-get-ignored-and-its-probably-not-for-the-reason-you-think-1e0967fdafdc?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e0967fdafdc</guid>
            <category><![CDATA[messaging]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Sun, 05 Jul 2026 14:58:39 GMT</pubDate>
            <atom:updated>2026-07-05T14:58:39.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*BxdQtdpIyDZp4Sv5svdnxg@2x.jpeg" /></figure><h4>A while ago, I started asking myself a simple question.</h4><p>Why do some people build really good products, offer great services, or have impressive skills, yet hardly get any replies when they reach out?</p><p>At first, I thought maybe the market was too competitive.</p><p>Maybe people were too busy.</p><p>Maybe everyone was receiving hundreds of messages every day.</p><p>Those things are true, but after spending time reaching out to projects myself and reading messages that other people were sending, I realised something.</p><p>Most pitches fail long before anyone decides whether the product is good or not.</p><p>The problem isn’t always the product.</p><p>Most times, it’s the message.</p><p>I have seen people write five long paragraphs explaining everything they do, every skill they have, every feature their product offers, and every award they have won.</p><p>By the time I finished reading the message, I still had one question in my head.</p><p>“So… why are you telling me all this?”</p><p>That is where many people get it wrong.</p><p>When someone opens your message, they are not thinking about you first.</p><p>They are thinking about themselves.</p><p>They are wondering whether your message is worth spending the next minute reading.</p><p>If they can’t see that quickly, they move on.</p><p>That doesn’t mean they’re rude.</p><p>It just means they have other things to do.</p><p>Think about it.</p><p>A founder might be in the middle of fixing a problem with their team.</p><p>A developer could be writing code.</p><p>A recruiter may have hundreds of applications waiting.</p><p>Even a community manager is probably replying to dozens of messages at the same time.</p><p>Nobody wakes up hoping to read another long sales message.</p><p>That changed the way I started writing my outreach.</p><p>Instead of trying to tell people everything about me, I started paying more attention to them.</p><p>I looked at what they were building.</p><p>I tried to understand where they might need help.</p><p>Then I wrote my message around that instead.</p><p>The funny thing is that I actually wrote less.</p><p>My messages became shorter, clearer, and easier to read.</p><p>Ironically, that was when I started getting more replies.</p><p>Persuasive pitching isn’t about sounding intelligent.</p><p>It isn’t about using big words.</p><p>And it definitely isn’t about copying a template you found online.</p><p>It’s about helping the other person understand, as quickly as possible, why your message matters to them.</p><p>That sounds simple, but it takes practice.</p><p>It also takes research.</p><p>One mistake I see quite often is people copying the same pitch and sending it to fifty different projects.</p><p>They change the company name, press send, and hope someone replies.</p><p>Sometimes they even forget to change the company name.</p><p>If you’re lucky, people ignore the message.</p><p>If you’re unlucky, you’ve just damaged your reputation.</p><p>People can usually tell when a message was written just for them and when it was copied from somewhere else.</p><p>The difference is obvious.</p><p>Over time, I started collecting little lessons from my own outreach.</p><p>Some worked.</p><p>Some failed.</p><p>Some got ignored.</p><p>Some turned into conversations, calls, partnerships, and paid opportunities.</p><p>Those experiences eventually became the reason I wrote The Art of Persuasive Pitching.</p><p>I didn’t write it because the internet needed another book about sales.</p><p>I wrote it because I wanted one place where I could explain the things I wish someone had taught me before I started reaching out to people.</p><p>If you’ve been sending messages and wondering why nobody replies, don’t immediately assume you have nothing valuable to offer.</p><p>Sometimes the opportunity isn’t the problem.</p><p>Sometimes the message is.</p><p>If you’d like to learn the complete system, including real outreach examples, practical templates, and the approach I use when reaching out to clients and projects, you can find The Art of Persuasive Pitching here:</p><p><a href="https://selar.com/7oz2124345">The Art Of Persuasive Writing</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e0967fdafdc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Prediction Markets Are Becoming Core to Web3]]></title>
            <link>https://medium.com/@Humblelee71/why-prediction-markets-are-becoming-core-to-web3-2f095ffe1a3f?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f095ffe1a3f</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto-betting]]></category>
            <category><![CDATA[prediction-markets]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Sun, 08 Feb 2026 00:29:01 GMT</pubDate>
            <atom:updated>2026-02-08T00:29:01.581Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*W0b3viSJCMDR9wq4QjAKJw@2x.jpeg" /></figure><p>The prediction market started trending around <strong>2024</strong>, and recently, more people have been asking: “What is it all about?”</p><p>Simply put, a <strong>prediction market</strong> is a platform where you can <strong>predict future events and make money while doing it.</strong> It’s a mix of <strong>trading, betting, and forecasting,</strong> and it’s becoming a new way to engage with markets you care about.</p><p>On Web3, prediction markets are even more interesting. You can make predictions on a wide range of events:</p><ul><li><strong>Crypto and tokens </strong>— like the next big protocol or token launch</li><li><strong>Politics</strong> — elections, senatorial candidates, policy decisions</li><li><strong>Sports and entertainment</strong> -championships, awards, cultural events</li></ul><p>Basically, <strong>anything with a measurable outcome </strong>can become a prediction market event.</p><p>Here’s a simple example:</p><p>Imagine there’s a market asking: <em>“Will Paragon be the next big DEX protocol in 2026?”</em></p><p><strong>Yes</strong>: 70% chance</p><p><strong>No</strong>: 30% chance</p><p>Total trading volume: around <strong>$15 million</strong></p><p>The market shows <strong>how people collectively feel about the outcome</strong>, and you can buy shares according to your prediction.</p><h4>How the Numbers Actually Work (Simple Example)</h4><p>Let’s break this down with real numbers.</p><p>Imagine this prediction market:</p><p><em>“Will Paragon become the most talked-about DEX protocol in 2026?”</em></p><ul><li><strong>Yes price:</strong> $0.70</li><li><strong>No price:</strong> $0.30</li><li><strong>Total market volume: </strong>$15,000,000</li></ul><p><strong>Step 1: You place a prediction</strong></p><p>You believe Yes will happen.</p><p>You invest <strong>$100</strong> on <strong>Yes</strong></p><p>At a price of <strong>$0.70 per share</strong></p><p>You receive <strong>about 142 Yes shares</strong></p><p>(100 ÷ 0.70 ≈ 142)</p><p><strong>Step 2: The market moves</strong></p><p>As more people buy <strong>Yes</strong>, the price may rise:</p><p>Yes moves from <strong>$0.70 → $0.85</strong></p><p>No drops from <strong>$0.30 → $0.15</strong></p><p>At this point, you can:</p><p><strong>Sell early</strong> for profit</p><p>Or <strong>hold</strong> until the event is resolved</p><p><strong>Step 3: Outcome is resolved</strong></p><p><strong>If Yes wins</strong></p><p>Each Yes share is worth <strong>$1</strong></p><p>Your 142 shares = <strong>$142</strong></p><p><strong>Profit</strong>: $42</p><p><strong>If No wins</strong></p><p>Your Yes shares become <strong>worth $0</strong></p><p>Your $100 is redistributed to No holders</p><p>That’s it.</p><p>No hidden math. No middleman.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Huo0PQovuO3kZITxEAJ_aQ@2x.jpeg" /></figure><h4>Why This Example Matters</h4><p>This is the part most people miss.</p><ul><li>The <strong>price</strong> shows probability (70% confidence)</li><li>Your <strong>profit</strong> comes from being early or being right</li><li>You’re not guessing randomly, you’re trading <strong>belief plus information</strong></li></ul><p>That’s why prediction markets sit between <strong>trading, betting, and forecasting.</strong></p><h4>Popular Web3 Prediction Platforms</h4><p>Some of the platforms where you can place predictions include:</p><p><strong>Polymarket</strong> — One of the largest platforms, allowing predictions on a wide range of events, from politics to culture. It’s unregulated in the US but remains very popular globally.</p><p><strong>PredictIt</strong> — More academic-focused, mainly political events.</p><p><strong>Crypto.com</strong> — Lets users trade and predict crypto markets, sports, and global events.</p><p><strong>Other emerging platforms </strong>— @sapiencemarket and @predictionpath are newer platforms that allow daily market predictions.</p><p>Choose the platform that works best for you.</p><h4>How to Place a Bet in a Web3 Prediction Market</h4><p>Connect your wallet —<strong> Use a Web3-compatible wallet </strong>like MetaMask, Coinbase Wallet, or any WalletConnect-supported wallet.</p><p><strong>Deposit funds </strong>— Usually stablecoins like USDC or USDT, though some platforms accept other cryptocurrencies.</p><p><strong>Explore markets </strong>— Browse events you’re interested in. Each market shows Yes/No prices, trading volumes, and other details.</p><p><strong>Buy your shares </strong>— Pick Yes or No for the outcome you believe in, enter your investment amount, and execute the trade.</p><p><strong>Monitor the market</strong> — Keep an eye on your predictions until the event resolves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*XahQmEGUO4F7bAG5266Oqg@2x.jpeg" /></figure><h4>How Results Are Determined</h4><p>Prediction markets rely on <strong>trusted data sources called oracles.</strong> Oracles feed real-world information into the blockchain so that <strong>the outcome of each prediction can be verified automatically.</strong></p><p><strong>Winning shares </strong>are paid out to those who predicted correctly.</p><p><strong>Losing shares</strong> are redistributed to the winners.</p><p>On Polymarket, these platforms are globally accessible, though US users may face some restrictions. Sometimes, a VPN can bypass these limitations.</p><h4><strong>Why Prediction Markets Matter in Web3</strong></h4><p>Prediction markets aren’t just about winning or losing money. They are <strong>crowd intelligence engines:</strong></p><p>They aggregate insights from people who are actually putting their money where their predictions are.</p><p>They can provide early signals on trends, elections, or token launches.</p><p>DAOs and communities can use them to <strong>forecast outcomes of proposals or governance decisions.</strong></p><p>Whether you’re into crypto, politics, or sports, <strong>prediction markets give you a chance to see how your intuition stacks up against the crowd.</strong></p><h4>Final Thoughts</h4><p>Prediction markets in Web3 are more than just bets, they’re a way to <strong>engage with the future </strong>while learning how <strong>markets, probabilities, and crowd sentiment</strong> really work. So pick a platform, place your first prediction, and see how accurate you really are.</p><p><strong>Web3 just made guessing profitable. Are you ready to predict the future?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f095ffe1a3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Basics of Video Creation for Web3 Creators]]></title>
            <link>https://medium.com/@Humblelee71/the-basics-of-video-creation-for-web3-creators-1d01779fc8a6?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d01779fc8a6</guid>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[cinematography]]></category>
            <category><![CDATA[ai-video-creator]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Mon, 02 Feb 2026 17:55:56 GMT</pubDate>
            <atom:updated>2026-02-02T17:55:56.174Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*gC7fvsHgmY6nbAaHJslbog@2x.jpeg" /></figure><p>2026 has seen a lot of people coming into Web3 and suddenly picking up video creation as a skill. Many people are now adding video creation to their list of skills, especially creators who want to stand out.</p><p>And we’ve seen everything so far. We’ve seen good videos. We’ve seen bad videos. And we’ve seen ugly videos.</p><p>Now, don’t get me wrong. Starting something you’ve always been scared of trying is not wrong at all. But before venturing into it, there are steps you should have taken to at least show that you are not coming in as a complete amateur.</p><p>This could be watching other Web3 creators who already make videos, understanding what video creation and editing really involve, reading about it, or watching basic classes. These things help you understand that video creation is not just setting up a camera on a tripod and recording anything that comes to mind.</p><p>That is why I want to talk about the basics. The basics every video creator needs, whether you are just starting out or you’ve been creating videos for a while but doing it wrongly.</p><h4>The Importance of Shots</h4><p>Shots are important because they add meaning. They give extra meaning to certain words, set actions, and help interpret emotions to your viewers. The shots you use can quietly change how people feel about your video, even if they don’t notice it directly.</p><h4>Wide / Master Shots</h4><p>Wide or master shots are mostly used as opening shots. They are often used to show the environment you are currently in. Sometimes a wide or master shot can start as a hook, but most times, we use close-up shots for hooks because they make the audience focus on you and not your environment.</p><p>A wide or master shot is used when you want to give your viewers more details. This could be your environment, the items or props you have around you, and also to make the video more visually appealing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*YqzlYBiynRNLa_80FWFcvw@2x.jpeg" /></figure><p>The wide or master shot can include you, your background, your chair, your table, or wherever you are standing if you are outside. It can run from your head to your full body, or from your head to your knees, depending on the context.</p><p>In cinematic laws, or the rules of filmmaking, a master shot traditionally shows the full subject and the surrounding environment. A wide shot emphasizes how much space surrounds the subject.</p><p>However, context matters. A master shot does not always have to be wide. A shot can be considered a master shot if it is the first shot of a video, establishing the scene before any other shots follow. That means even a close-up or medium shot can act as a master shot in the right context.</p><h4>Medium Shots</h4><p>Medium shots usually run from the head to the waist. They are commonly used in video creation because they are balanced and allow the viewer to see both the subject and some context without showing the full environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*DQBgRm0z_mECSxgH3xtYAA@2x.jpeg" /></figure><p>Medium shots can also be broken down further:</p><p>•	Cowboy shot — head to hips, named after Western films where the gun was visible at hip level.</p><p>•	Standard medium shot — head to waist or mid-section.</p><p>•	Medium close-up (mid-CU) — head to just below the chest. Sometimes people confuse this with a close-up because it’s closer than the standard medium shot, but it’s still classified under medium shots.</p><p>The wide/master shot can include aspects that a medium shot does as well, depending on how it’s framed. For example, a master shot could show a full-body subject but then focus on a portion of the subject, like a medium or CU, if it is the first shot in the video. This shows why understanding context is critical.</p><h4>Close-Up Shots (CU)</h4><p>Close-up shots, often abbreviated CU, typically run from the head to the shoulders or upper chest. This shot makes viewers focus fully on you and your message, minimizing distraction from the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*kgJfFSJ61gh2Us2Ic1gbPw@2x.jpeg" /></figure><p>This is where your emotions become visible. Your excitement, seriousness, confidence, or concern all show clearly. Close-ups allow your audience to connect with you on a more personal level.</p><p>Close-up shots are mostly used to emphasize important words or messages. Examples include a call to action, highlighting a pain point, addressing a problem, or showing a reaction that you want the audience to notice.</p><h4>Extreme Close-Up Shots (ECU)</h4><p>Extreme close-up shots, also called tight close-ups, are extremely tight. They usually run from the head to the neck or chin. This shot emphasizes small details like your eyes, lips, facial expressions, or subtle movements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*STc0LgeIZY3QsEadMYiZHg@2x.jpeg" /></figure><p>ECUs are used to make viewers notice very specific traits or emotions. For example, the squint of your eyes, the movement of your lips, or even a tear. It can highlight intensity, detail, or emotion that a standard close-up cannot.</p><h4>Insert Shots</h4><p>Insert shots focus on objects or actions rather than your face. Examples include:</p><p>•	Typing on a keyboard</p><p>•	Showing a laptop screen or a trading signal</p><p>•	Displaying notes in a journal</p><p>•	Mouse movements</p><p>•	Objects on a desk or in your hands</p><p>•	Actions like snapping fingers, clapping, or fidgeting</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*--LNwnI6CWs5SK4ZKDRFag@2x.jpeg" /></figure><p>Insert shots help viewers notice details or actions without needing to show the full person. They make videos more dynamic and informative, and they prevent monotony by breaking up long talking segments.</p><h4>Takeaway</h4><p>Every shot has meaning. Using the wrong shot or using the same shot throughout the video can make viewers tired and bored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*teyiEQZBJdLOBPD8FoaC3g@2x.jpeg" /></figure><p>Understanding these shots and their context allows you to create videos that feel intentional, entertaining, and emotionally engaging.</p><p>I will cover other shots more as we continue, so you can master how to use them properly rather than randomly switching angles.</p><p>This is just part one. I’ll be sharing more basics on video creation, including editing and how to use these shots better, in the next content.</p><p>I also have a video creation class coming up on my channel soon. If you’re interested, <a href="https://t.me/ThinkingWithLee">Join Here</a></p><p>If you learned something from this, retweet it or tag a video creator or a friend who is getting into video creation or needs to improve their videos.</p><p>I wish you the very best in your video creation journey. Good luck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d01779fc8a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Automation in Web3 (What It Is and What It Is Not)]]></title>
            <link>https://medium.com/@Humblelee71/ai-automation-in-web3-what-it-is-and-what-it-is-not-15b6f911d6c0?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/15b6f911d6c0</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 22:41:12 GMT</pubDate>
            <atom:updated>2026-01-06T22:41:12.723Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*gi2peGcghe1p0NN3lvEpXA@2x.jpeg" /></figure><p>AI automation is often misunderstood.</p><p>Some things people say about it are true.</p><p>Some are partially correct.</p><p>And some are just wrong.</p><p>AI automation is about AI systems carrying out tasks without continuous human help. It saves time, reduces errors, and increases efficiency.</p><p>In Web3, AI automation is already playing a key role in community management, analytics, content operations, and workflow optimization.</p><p>Before going deeper, there are a few misconceptions that need to be cleared up.</p><h4>Misconception 1: ChatGPT Equals AI Automation</h4><p>Some people think ChatGPT equals AI automation.</p><p>That is not true.</p><p>ChatGPT is an AI model, one of many AI models. It generates text reactively. It responds to prompts given by humans and cannot execute tasks on its own.</p><p>Automation only happens when AI models are integrated into workflows that trigger actions without human input every single time.</p><h4>Misconception 2: Scheduling Tools Are AI Automation</h4><p>Another common misconception is around scheduling tools.</p><p>Tools that post content or send emails on a schedule are not AI automation. They execute predefined tasks but do not analyze, decide, or generate content intelligently by themselves.</p><p>They can be paired with AI, but alone, they are not AI automation.</p><h4>Misconception 3: AI Automation Only Exists on Discord</h4><p>AI automation is not limited to Discord.</p><p>Discord is simply a visible example of how automation helps Web3 communities. The same logic applies across other Web3 workflows.</p><h4>Where AI Automation Exists in Web3</h4><p>AI automation exists wherever AI systems are triggered to perform tasks on their own.</p><p>This includes community workflows, trading systems, analytics, content pipelines, and notifications.</p><h4>How AI Automation Works (High-Level)</h4><p>At a high level, AI automation follows a simple flow:</p><p>•	Data is collected</p><p>•	AI models process and interpret that data</p><p>•	Automated actions are triggered</p><p>•	Feedback improves future outcomes</p><p>This is the foundation of AI automation across Web3 use cases.</p><h4>Why AI Automation Matters</h4><p>AI automation helps scale operations.</p><p>One person can manage large communities, workflows, or datasets that would normally require multiple team members.</p><p>It saves time, handles repetitive tasks, improves consistency, and helps operators stay updated without constantly monitoring platforms manually.</p><h4>Who This Is For</h4><p>You do not need to be a developer to apply AI automation.</p><p>These skills are useful for Web3 operators, community managers, growth strategists, analysts, and content marketers.</p><p>This is a brief public insight into AI automation.</p><p>The full breakdown, workflows, and implementation details are part of a course I’m building.</p><p>Follow for more skills that will matter going into 2026.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15b6f911d6c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Misconceptions About Technical Writing in Web3]]></title>
            <link>https://medium.com/@Humblelee71/misconceptions-about-technical-writing-in-web3-527327fc0fce?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/527327fc0fce</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Sat, 03 Jan 2026 23:00:41 GMT</pubDate>
            <atom:updated>2026-01-03T23:00:41.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-jg_MuzGP-cGJ7EyIhnMZg@2x.jpeg" /></figure><h4>THERE ARE MISCONCEPTIONS ABOUT TECHNICAL WRITING IN WEB3.</h4><p>Knowing crypto does not make you a technical writer, and being a developer does not automatically make you one.</p><p><strong>Technical writing is not just dumping complex jargon into a white paper.</strong></p><p><strong>Technical writing is about understanding, clarity, and accuracy.</strong></p><p>You must consider your audience and your goal.</p><h4>Audience and intent</h4><p>Are you writing for advanced users, intermediates, beginners, or a mix?</p><p>Are you trying to get users, investors, or community members?</p><p>You can also check the quoted thread for the key elements of technical writing I discussed earlier.</p><p><a href="https://x.com/humblelee71/status/1953110474217697422">https://x.com/humblelee71/status/1953110474217697422</a></p><h4>Credibility and tools</h4><p><strong>A credible technical writer must know the tools.</strong></p><p>Notion. GitHub. Google Documents. Medium.</p><p>Learning and mastering these tools shows professionalism and builds trust in your writing.</p><h4>Words and implications</h4><p>Be careful with words that can implicate you or reduce credibility.</p><p>For example, instead of saying<strong> “this project is the best,”</strong> say<strong> “this is one of the best projects.”</strong></p><p><em>Accuracy, verified facts, and cautious wording protect your credibility.</em></p><h4>Beyond white papers</h4><p><strong>Technical writing is not only about white papers.</strong></p><p>Projects need proposals, user guides, documentation, and more.</p><p>Many miss opportunities because they only pitch for white papers.</p><h4>What I am building</h4><p>I am preparing a proper course breakdown on technical writing, analysis, AI automation, systems thinking and workflow design, and more.</p><p>This course will break down complexities in each skill with real use cases and relatable vocabulary, so you can understand and apply them without stress.</p><p>I will also be sharing brief insights along the way.</p><p>Follow me and turn on notifications to keep up.</p><h4>Presentation and clarity</h4><p>Colors, fonts, and formats should reflect the project and stay consistent.</p><p><strong>Technical writing in Web3 is about communicating the vision clearly to different audiences, with accuracy, clarity, and credibility.</strong></p><p>Master these and you become valuable and ready.</p><p>© Humble Lee</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=527327fc0fce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Framework for Interpreting DEX On-Chain Data]]></title>
            <link>https://medium.com/@Humblelee71/a-framework-for-interpreting-dex-on-chain-data-aa6ef2843057?source=rss-479ef29b935f------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa6ef2843057</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[dex]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[onchain-analysis]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Humble Lee]]></dc:creator>
            <pubDate>Sun, 21 Dec 2025 15:21:35 GMT</pubDate>
            <atom:updated>2025-12-21T15:21:35.781Z</atom:updated>
            <content:encoded><![CDATA[<h4>Liquidity, Volume, Users, and Their Analytical Limitations</h4><h4><strong>Objective</strong></h4><p>The objective of this article is to present a structured framework for interpreting DEX on-chain data, with a focus on liquidity, volume, and user activity. The framework clarifies how commonly used metrics should be read, the assumptions they rely on, and the conditions under which misinterpretation is likely to occur.</p><p>This article is intended as a technical reference rather than a trading guide or protocol review.</p><h3>Scope and Assumptions</h3><h4>Scope</h4><p>This analysis is limited to:</p><p>•	EVM-based decentralized exchanges</p><p>•	On-chain liquidity metrics</p><p>•	Swap volume and transaction activity</p><p>•	Wallet-level participation observable on-chain</p><p>The following are explicitly excluded:</p><p>•	Centralized exchange data</p><p>•	Off-chain order flow</p><p>•	Token valuation models</p><p>•	Price prediction or trading strategies</p><p>•	Non-EVM chains</p><h4>Assumptions</h4><p>•	On-chain data is accurate at the protocol level but incomplete at the behavioral level</p><p>•	Wallet addresses are treated as analytical units, not unique human identities</p><p>•	DEX activity is evaluated independently of broader macroeconomic or market sentiment factors</p><h4><strong>Note:</strong></h4><blockquote>On-chain metrics describe what occurred, not why it occurred. This distinction underpins the entire framework.</blockquote><h3>Framework Overview</h3><p>The framework organizes DEX on-chain data into three primary metric classes:</p><p>•	Liquidity metrics</p><p>•	Volume metrics</p><p>•	User metrics</p><p>Each metric class is evaluated through:</p><p>1.	What the metric measures</p><p>2.	How it is commonly interpreted</p><p>3.	Why that interpretation can fail</p><p>4.	How the metric should be read instead</p><h3>I. Liquidity Metrics</h3><h4>What Liquidity Metrics Measure</h4><p>Liquidity metrics quantify the amount of capital available to facilitate swaps with minimal price impact. Common examples include:</p><p>•	Total Value Locked (TVL)</p><p>•	Pool-level liquidity</p><p>•	Liquidity distribution across price ranges</p><h4>Common Interpretation</h4><p>Liquidity is often interpreted as a proxy for:</p><p>•	User confidence</p><p>•	Protocol health</p><p>•	Reduced trading friction</p><h4>Why This Interpretation Fails</h4><p>Liquidity metrics do not encode:</p><p>•	Duration of capital commitment</p><p>•	Source of liquidity (organic vs incentivized)</p><p>•	Sensitivity of liquidity to price movements</p><p>Incentive-driven liquidity can inflate TVL without indicating sustainable demand.</p><h4>Correct Interpretation</h4><p>Liquidity should be evaluated alongside:</p><p>•	Incentive structures and emission schedules</p><p>•	Liquidity churn over time</p><p>•	Depth at relevant price ranges rather than aggregate TVL</p><p><strong>Liquidity is a capacity metric, not a demand signal.</strong></p><h3>II. Volume Metrics</h3><h4>What Volume Metrics Measure</h4><p>Volume metrics represent the notional value of swaps executed over a given period, including:</p><p>•	Daily trading volume</p><p>•	Pool-specific volume</p><p>•	Volume-to-liquidity ratios</p><h4>Common Interpretation</h4><p>High volume is often interpreted as:</p><p>•	Strong product-market fit</p><p>•	High user engagement</p><p>•	Sustainable fee generation</p><h4>Why This Interpretation Fails</h4><p>Volume may be inflated by:</p><p>•	Wash trading</p><p>•	MEV-driven arbitrage loops</p><p>•	Incentive-based volume farming</p><p>Volume alone does not distinguish between <strong>economic demand</strong> and <strong>mechanical activity.</strong></p><h4>Correct Interpretation</h4><p>Volume should be contextualized using:</p><p>•	Unique active traders</p><p>•	Trade size distribution</p><p>•	Persistence of volume across time periods</p><p><strong>Volume is an activity metric, not a usage-quality metric.</strong></p><h3>III. User Metrics</h3><h4>What User Metrics Measure</h4><p>User metrics attempt to quantify participation through:</p><p>•	Unique wallet interactions</p><p>•	New vs returning addresses</p><p>•	Transaction frequency per address</p><h4>Common Interpretation</h4><p>Growing user counts are frequently taken as evidence of:</p><p>•	Adoption</p><p>•	Network effects</p><p>•	Expanding user base</p><h4>Why This Interpretation Fails</h4><p>Wallet-based metrics obscure:</p><p>•	Multi-wallet usage</p><p>•	Bot and automated activity</p><p>•	Contract-mediated interactions</p><p>Address counts do not equate to individual users.</p><h4>Correct Interpretation</h4><p>User metrics should be evaluated through:</p><p>•	Behavioral patterns over time</p><p>•	Retention rather than raw growth</p><p>•	Activity consistency across observation windows</p><p><strong>User metrics are participation proxies, not identity metrics.</strong></p><h3>IV. Cross-Metric Validation</h3><p>No single metric class should be interpreted in isolation.</p><p><strong>Validation Principles:</strong></p><p>•	Liquidity without volume suggests idle or incentive-driven capital</p><p>•	Volume without user diversity suggests mechanical or automated activity</p><p>•	User growth without volume suggests low economic engagement</p><p>Reliable signals emerge only when <strong>multiple metrics converge.</strong></p><h3>Limitations</h3><h4>Data Visibility</h4><p>On-chain data captures executed transactions only. It does not reflect:</p><p>•	User intent</p><p>•	Failed transactions</p><p>•	Off-chain decision-making</p><h4>Identity Abstraction</h4><p>Wallet addresses are analytical units, not verified individuals. This limits precision in user-level analysis.</p><h4>Incentive Distortion</h4><p>Liquidity mining and trading incentives can materially distort observed metrics. This framework does not normalize for incentive effects beyond qualitative interpretation.</p><h4>Protocol Design Differences</h4><p>Differences in AMM architecture, fee structures, and liquidity mechanisms affect metric comparability across protocols.</p><h4>Temporal Sensitivity</h4><p>Short observation windows can produce misleading conclusions. Longitudinal analysis is required for robustness.</p><h4>Technical Conclusion</h4><p>DEX on-chain data provides valuable insight into protocol activity, but raw metrics are insufficient without structured interpretation. Liquidity, volume, and user metrics each describe different dimensions of protocol behavior and rely on assumptions that must be made explicit.</p><p>This framework emphasizes:</p><p>•	Metric categorization by function</p><p>•	Explicit identification of failure modes</p><p>•	Cross-metric validation</p><p>•	Transparent analytical limitations</p><p>Applied consistently, the framework improves analytical reliability and reduces false signals. It does not eliminate uncertainty, but it makes assumptions visible and analytical errors easier to detect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa6ef2843057" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>