<?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 Sagar Jethi on Medium]]></title>
        <description><![CDATA[Stories by Sagar Jethi on Medium]]></description>
        <link>https://medium.com/@sagarjethi?source=rss-d645aab84c86------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sZhpYnJ20SjBnx0ihreeDQ.jpeg</url>
            <title>Stories by Sagar Jethi on Medium</title>
            <link>https://medium.com/@sagarjethi?source=rss-d645aab84c86------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:15:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sagarjethi/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[4 Solidity Gas Traps I Hit This Week — and the One-Line Fixes That Save Thousands of Gwei]]></title>
            <link>https://sagarjethi.medium.com/4-solidity-gas-traps-i-hit-this-week-and-the-one-line-fixes-that-save-thousands-of-gwei-3652f271635b?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/3652f271635b</guid>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Mon, 07 Jul 2025 18:44:09 GMT</pubDate>
            <atom:updated>2025-07-07T18:44:31.940Z</atom:updated>
            <content:encoded><![CDATA[<h3>4 Solidity Gas Traps I Hit This Week and the One-Line Fixes That Save Thousands of Gwei</h3><p><em>By Sagar Jethi — 10 years in Web3 trenches, Solidity-first smart-contract engineer and DePIN builder.</em></p><blockquote><strong><em>TL;DR</em></strong><em><br> Tiny refactors = outsized savings.<br> • Copy storage arrays to memory inside loops<br> • Ban </em><em>tx.origin auth checks<br> • Swap manual counters for OpenZeppelin’s </em><em>Counters<br> • Replace dynamic revert strings with custom errors</em></blockquote><p>I spent last week auditing two very different contracts — an ERC-4626 yield vault and an on-chain game. Both were functional, well-tested, and actively used… yet each leaked gas like a perforated tank. Below are the four biggest offenders and <strong>the literal one-line changes</strong> that fixed them.</p><h3>1. Storage Loop Writes</h3><h3>The Offender 💸</h3><pre>for (uint256 i; i &lt; users.length; ++i) {<br>    balances[users[i]] += reward;  // storage read *and* write<br>}</pre><p>Every iteration loads users[i] from <strong>storage</strong>—about 100 gas each time before you even do the write.</p><h3>The One-Liner ⚡</h3><pre>address[] memory _users = users; // copy to memory, then loop</pre><p>Now the loop hits cheap <strong>memory</strong> reads. On a 1,000-user reward cycle you shave ≈100k gas.</p><h3>Benchmarked</h3><p>Loop Size Before (gas) After (gas) Saved 100 users 30,281 20,203 <strong>-33 %</strong> 1,000 users 291,112 192,134 <strong>-100,000</strong></p><p><em>(Measured with Foundry </em><em>gas-snapshot on mainnet fork.)</em></p><h3>2. tx.origin Authentication</h3><h3>The Offender 🚫</h3><pre>require(msg.sender == tx.origin, &quot;No contracts allowed&quot;);</pre><p>Developers add this to block flash-loan exploits — but it also blocks multisigs, batchers, Account-Abstraction wallets, and still fails to stop social-engineering attacks.</p><h3>The One-Liner ⚡</h3><pre>// Delete—or migrate to a real auth module (EIP-3074 / ERC-4337)</pre><p>If you truly need single-EOA logic, create a dedicated signer role and let wallets handle permissions.</p><h3>Why It Matters</h3><p>Breaking composability kills user experience <strong>and</strong> future-proofing. DeFi integrations, on-chain games, and DAO tooling all assume contract-to-contract calls will work.</p><h3>3. Manual Counters in Mappings</h3><h3>The Offender 💸</h3><pre>mapping(uint256 =&gt; uint256) public stakes;<br>uint256 public stakeCount;</pre><pre>function deposit(uint256 amount) external {<br>    stakes[++stakeCount] = amount; // two SSTOREs each call<br>}</pre><h3>The One-Liner ⚡</h3><pre>using Counters for Counters.Counter;<br>Counters.Counter private _ids;</pre><p>With OpenZeppelin’s Counters, only the counter value is stored—no duplicate mapping write. Savings: ≈20 k gas per call.</p><h3>4. Dynamic Revert Strings</h3><h3>The Offender 💸</h3><pre>require(x &gt; 0, string.concat(&quot;Invalid amount: &quot;, Strings.toString(x)));</pre><p>Dynamic strings are stored in calldata on every revert — wasting gas and ballooning bytecode size.</p><h3>The One-Liner ⚡</h3><pre>error InvalidAmount(uint256 x); // custom error (4-byte selector)</pre><p>Custom errors refund ~3.5k gas per revert and can shrink init-code enough to keep you under the 24 kB contract size limit.</p><h3>Consolidated Savings</h3><p>Trap Approx. Gas Saved Bonus Benefits Storage loops → memory copy 100 gas × iterations Faster indexer sync Remove tx.origin gate Future integrations AA-wallet support Replace manual counter 20 k per call Cleaner code Custom errors 3.5 k per revert Smaller bytecode</p><h3>Tool Stack I Used</h3><p><strong>Foundry + gas-snapshot</strong> — see deltas in CI.</p><p><strong>Slither</strong> — flags tx.origin during static analysis.</p><p><strong>Tenderly</strong> — simulate savings on live mainnet txs.</p><h3>Final Thoughts</h3><p>Gas optimisations aren’t just “nice-to-have” — they decide <strong>whether small users can afford to interact with your dApp</strong> when network fees spike. The best part? Most fixes are <strong>one-liners</strong>.</p><p>If you want a <strong>24-hour gas audit checklist</strong>, drop a comment saying <strong>“audit”</strong> or DM me. First <strong>5</strong> readers get it free. Let’s plug your gas leaks before they bleed your users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3652f271635b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ 12 ReactJS Security Best Practices You Shouldn’t Ignore]]></title>
            <link>https://sagarjethi.medium.com/12-reactjs-security-best-practices-you-shouldnt-ignore-2fe0e063a66a?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fe0e063a66a</guid>
            <category><![CDATA[reactjs]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Thu, 10 Apr 2025 08:14:50 GMT</pubDate>
            <atom:updated>2025-04-10T08:14:50.214Z</atom:updated>
            <content:encoded><![CDATA[<p>React is powerful, fast, and flexible — but with great power comes great responsibility. If you’re building anything in production, especially something public-facing, you <strong>must</strong> think about <strong>security</strong> from day one.</p><p>In this post, I’ll walk you through 12 essential <strong>ReactJS security best practices</strong>, along with <strong>code examples</strong>, <strong>folder structure tips</strong>, and <strong>file-naming conventions</strong> to help you build secure, maintainable apps.</p><h3>1. 📁 Don’t Store Configs in config.js — Use .env (But Never Push It)</h3><p>Hardcoding configuration directly into your JavaScript files is risky. It can lead to accidental exposure of sensitive info and makes environment changes harder.</p><h3>❌ Bad: Hardcoded config.js</h3><pre>// src/config.js<br>export const API_URL = &quot;https://api.example.com&quot;;<br>export const SECRET_KEY = &quot;super-secret-key&quot;;</pre><p>This gets bundled into your frontend JavaScript — and <strong>anyone can see it</strong>.</p><h3>✅ Better: Use .env for Config</h3><pre>REACT_APP_API_URL=https://api.example.com<br>REACT_APP_ENV=production</pre><p>In your React code:</p><pre>const API_URL = process.env.REACT_APP_API_URL;</pre><p>Only store <strong>non-sensitive</strong> values in .env (e.g. public URLs, feature flags, environment type).</p><h3>🛑 Never Push .env to Git</h3><p>Always add it to your .gitignore:</p><pre>.env<br>.env.local</pre><p>Even if it doesn’t contain secrets now, someone might add them later. Keep it out of version control at all times.</p><h3>2. 🛡 Escape HTML to Prevent XSS (Cross-site Scripting)</h3><p>If you’re rendering user-generated content, sanitize it first. Malicious users can inject &lt;script&gt; tags or dangerous code.</p><h3>❌ Vulnerable:</h3><pre>function Comment({ text }) {<br>  return &lt;div&gt;{text}&lt;/div&gt;;<br>}</pre><h3>✅ Safe with DOMPurify:</h3><pre>import DOMPurify from &#39;dompurify&#39;;</pre><pre>function Comment({ text }) {<br>  const clean = DOMPurify.sanitize(text);<br>  return &lt;div dangerouslySetInnerHTML={{ __html: clean }} /&gt;;<br>}</pre><h3>3. ⚠️ Avoid dangerouslySetInnerHTML Unless Absolutely Needed</h3><p>This prop bypasses React’s built-in protections. If you <strong>must</strong> use it (e.g. for trusted Markdown or CMS content), always sanitize it first.</p><h3>4. 🌐 Use HTTPS for All Requests</h3><p>Always use HTTPS when calling APIs or services. HTTP is vulnerable to man-in-the-middle attacks.</p><pre>fetch(&quot;https://yourapi.com/data&quot;); // ✅ Secure</pre><h3>5. 🚫 Never Use eval() or new Function()</h3><p>These functions execute dynamic code and are a huge security risk.</p><h3>❌ Never do this:</h3><pre>eval(&quot;alert(&#39;Hacked!&#39;)&quot;);<br>new Function(&quot;alert(&#39;Hacked!&#39;)&quot;)();</pre><h3>6. 🧱 Limit Third-Party Dependencies</h3><p>Every package you install is potential attack surface. Use trusted packages, check for recent updates, and audit regularly.</p><pre>npm audit fix<br># or<br>yarn audit</pre><h3>7. 🔒 Add a Content Security Policy (CSP)</h3><p>A CSP header tells browsers to only load resources from trusted sources, helping block injected scripts.</p><h3>Example (Express.js):</h3><pre>app.use((req, res, next) =&gt; {<br>  res.setHeader(&quot;Content-Security-Policy&quot;, &quot;default-src &#39;self&#39;&quot;);<br>  next();<br>});</pre><p>You can also configure CSP headers on Netlify, Vercel, or via helmet middleware.</p><h3>8. 🧾 Protect Forms from CSRF</h3><p>If you’re using cookies for authentication, enable CSRF protection. In Express, use csurf:</p><pre>const csrf = require(&#39;csurf&#39;);<br>app.use(csrf({ cookie: true }));</pre><p>Always include the CSRF token in form submissions and verify it server-side.</p><h3>9. 🧼 Use ESLint for Security Audits</h3><p>Add security-focused linting rules to catch unsafe code early.</p><h3>Install:</h3><pre>npm install eslint-plugin-security --save-dev</pre><h3>Add to .eslintrc:</h3><pre>{<br>  &quot;plugins&quot;: [&quot;security&quot;],<br>  &quot;extends&quot;: [&quot;plugin:security/recommended&quot;]<br>}</pre><h3>10. 🔍 Sanitize URLs Before Redirecting</h3><p>Never redirect using raw user input.</p><h3>❌ Unsafe:</h3><pre>window.location.href = userInput;</pre><h3>✅ Safe:</h3><pre>const url = new URL(userInput);<br>if (url.origin === &quot;https://yourdomain.com&quot;) {<br>  window.location.href = url.href;<br>}</pre><h3>11. 🗂 Use Modular, Predictable Folder Structure</h3><p>A well-structured project helps isolate logic, reduce risks, and scale better.</p><h3>✅ Recommended structure:</h3><pre>/src<br>  /components    → Reusable UI<br>  /pages         → Route-level components<br>  /hooks         → Custom logic (e.g. useAuth)<br>  /services      → API functions<br>  /contexts      → Global state with Context API<br>  /utils         → Helper functions<br>  /config        → Non-sensitive settings</pre><p>This keeps sensitive logic out of UI code and encourages separation of concerns.</p><h3>12. 🏷 File Naming and Code Separation Best Practices</h3><p>Use consistent, meaningful file names and keep concerns separated (e.g. no business logic in components).</p><h3>✅ Naming Conventions:</h3><ul><li>Components: LoginForm.jsx, UserCard.tsx</li><li>Hooks: useAuth.js, useToggle.js</li><li>Services: apiClient.js, authService.js</li><li>Context: AuthContext.js, ThemeContext.js</li></ul><h3>✅ Example:</h3><pre>// ✅ src/services/apiClient.js<br>export async function fetchUser(token) {<br>  return fetch(&quot;/api/user&quot;, {<br>    headers: { Authorization: `Bearer ${token}` },<br>  });<br>}</pre><pre>// ✅ src/components/UserProfile.jsx<br>import { fetchUser } from &quot;../services/apiClient&quot;;</pre><pre>function UserProfile() {<br>  useEffect(() =&gt; {<br>    fetchUser(authToken).then(setUser);<br>  }, []);<br>}</pre><h3>✅ Final Thoughts</h3><p>React gives you an amazing development experience — but you must actively secure your app.</p><p>Here’s a quick recap:</p><ul><li>Use .env for config, but never push it to Git</li><li>Sanitize inputs and escape HTML</li><li>Avoid eval, use HTTPS, and enforce CSP</li><li>Structure your code clearly and separate logic from UI</li></ul><p><strong>Security isn’t a feature — it’s a habit.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fe0e063a66a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Hack. Earn. Secure the Future: Bug Bounties in 2025 ]]></title>
            <link>https://sagarjethi.medium.com/hack-earn-secure-the-future-bug-bounties-in-2025-0e2d05fcb364?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e2d05fcb364</guid>
            <category><![CDATA[hackathons]]></category>
            <category><![CDATA[earn]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[smart-contract-auditing]]></category>
            <category><![CDATA[blockchain-developer]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Thu, 09 Jan 2025 07:48:45 GMT</pubDate>
            <atom:updated>2025-01-09T07:49:12.932Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m0Uu60iszVoGYFMDs8Wusg.jpeg" /></figure><p>The world of cybersecurity is evolving rapidly. With the rise of <strong>Web3 technologies</strong> and <strong>AI agents</strong>, vulnerabilities in blockchain platforms and AI systems have become a lucrative frontier for ethical hackers. Welcome to <strong>bug bounty programs</strong>, where you can legally break systems, identify flaws, and earn big rewards.</p><p>2025 is the year to dive into bug bounties. This guide will walk you through everything you need to know: top platforms, tools, and strategies to make the most out of this booming industry.</p><h3>What Are Bug Bounties?</h3><p>Bug bounties are programs run by companies to identify security vulnerabilities in their systems. They invite <strong>ethical hackers</strong> to report these vulnerabilities in exchange for monetary rewards.</p><p>Here’s why <strong>bug bounties</strong> are booming in 2025:</p><ol><li><strong>Web3 platforms</strong> like DeFi, NFTs, and crypto exchanges are prime targets for attacks.</li><li><strong>AI integration</strong> has introduced complex vulnerabilities that require specialized expertise.</li></ol><p>For example, a hacker earned <strong>$10 million</strong> in 2022 for reporting a critical issue in MakerDAO via <a href="https://immunefi.com/">Immunefi</a>.</p><p>Bug bounties are not just about money — they’re about securing the future of technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AbLh07Od9XX1cD2V8eVM6w.jpeg" /></figure><h3>Why 2025 Is a Big Year for Bug Bounties</h3><p>The cybersecurity landscape has shifted dramatically. In 2025, two major trends are shaping bug bounties:</p><h3>1. AI Agents and Security Challenges</h3><p>AI agents are now integral to blockchain platforms, automating processes and enhancing decision-making. However, they also come with unique vulnerabilities:</p><ul><li><strong>Adversarial Attacks</strong>: Manipulating AI models with deceptive inputs.</li><li><strong>Data Poisoning</strong>: Corrupting datasets to disrupt AI performance.</li><li><strong>AI-Web3 Integration Loopholes</strong>: Exploiting vulnerabilities in smart contracts interacting with AI agents.</li></ul><h3>2. Web3 Security Is Critical</h3><p>Web3 platforms are decentralized, which makes them transparent yet vulnerable. Hackers focus on:</p><ul><li><strong>Re-entrancy attacks</strong></li><li><strong>Flash loan exploits</strong></li><li><strong>Oracle manipulation</strong></li></ul><p>For ethical hackers, this means <strong>high payouts</strong>, increased demand, and a chance to make a global impact.</p><h3>Top Bug Bounty Platforms to Join in 2025</h3><p>Here are the top platforms where you can find <strong>crypto and Web3 bug bounty programs</strong>:</p><h3>1. Immunefi</h3><p>The most trusted platform for <strong>Web3 and DeFi security</strong>.</p><ul><li><strong>Total Rewards Paid</strong>: Over $100 million.</li><li><strong>Focus</strong>: Smart contracts, decentralized apps, and infrastructure vulnerabilities.</li><li><strong>Example</strong>: A whitehat hacker earned $10M from MakerDAO through Immunefi.</li><li>🌐 <a href="https://immunefi.com/">Explore Immunefi</a></li></ul><h3>2. HackerOne</h3><p>A leading platform for Web2 and Web3 security programs.</p><ul><li><strong>Top Clients</strong>: OpenSea, Ledger, and other crypto giants.</li><li><strong>Opportunities</strong>: Offers hybrid bounties across traditional and blockchain-based systems.</li><li>🌐 <a href="https://hackerone.com/">Visit HackerOne</a></li></ul><h3>3. Code4rena</h3><p>A unique, gamified platform for <strong>smart contract audits</strong>.</p><ul><li><strong>What’s Special</strong>: Compete in live audits to find vulnerabilities.</li><li><strong>Why Join</strong>: Build skills while earning rewards in a competitive setting.</li><li>🌐 <a href="https://code4rena.com/">Discover Code4rena</a></li></ul><h3>4. Secureum</h3><p>Combining training and bounty opportunities for Web3 security.</p><ul><li><strong>Programs</strong>: Bootcamps to learn smart contract auditing.</li><li><strong>Transition</strong>: Move into paid bounty programs post-training.</li><li>🌐 <a href="https://secureum.xyz/">Learn at Secureum</a></li></ul><h3>5. HackenProof</h3><p>A fast-growing platform for <strong>blockchain security programs</strong>.</p><ul><li><strong>Clients</strong>: Trusted by projects like 1inch and Avalanche.</li><li><strong>Ideal For</strong>: Intermediate hackers building experience.</li><li>🌐 <a href="https://hackenproof.com/programs">Start at HackenProof</a></li></ul><h3>How to Start Your Bug Bounty Journey</h3><p>Follow these steps to become a successful <strong>ethical hacker</strong>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gBJVw6LBI1PtHte6gWBJvQ.jpeg" /></figure><h3>1. Build Your Skills</h3><p>Focus on these high-demand areas:</p><ul><li><strong>Web3 Security</strong>: Learn about re-entrancy attacks, oracle manipulation, and flash loan exploits.</li><li><strong>AI Security</strong>: Understand adversarial attacks and data poisoning techniques.</li></ul><p><strong>Resources to Learn</strong>:</p><ul><li><a href="https://ethereum.org/security/">Ethereum Security Handbook</a></li><li><a href="https://www.damnvulnerabledefi.xyz/">Damn Vulnerable DeFi</a></li></ul><h3>2. Practice on Testnets</h3><p>Testnets let you explore vulnerabilities in a safe environment. These platforms offer real-world challenges:</p><ul><li>🌐 <a href="https://ethernaut.openzeppelin.com/">Ethernaut</a></li><li>🌐 <a href="https://capturetheether.com/">Capture the Ether</a></li></ul><h3>3. Use Essential Tools</h3><p>Equip yourself with the best tools for vulnerability discovery:</p><ul><li><a href="https://github.com/ConsenSys/mythril">Mythril</a>: Smart contract security analyzer.</li><li><a href="https://tenderly.co/">Tenderly</a>: Debugging and monitoring platform.</li><li><a href="https://book.getfoundry.sh/">Foundry</a>: Ethereum testing framework.</li></ul><h3>4. Start Small and Build Reputation</h3><p>Begin with smaller bounties to build experience and credibility. Over time, tackle higher-stakes programs to maximize your earnings.</p><h3>Why Bug Bounties Are Worth It</h3><p>The rise of <strong>DeFi</strong>, <strong>NFTs</strong>, and <strong>AI-driven platforms</strong> has created an unprecedented demand for cybersecurity professionals. Here’s why bug bounties are an excellent choice:</p><ul><li><strong>High Payouts</strong>: Some programs pay millions for critical vulnerabilities.</li><li><strong>Endless Opportunities</strong>: Web3’s rapid growth ensures a steady demand for ethical hackers.</li><li><strong>Global Recognition</strong>: Successful hackers gain credibility and influence in the tech community.</li></ul><h3>Final Thoughts</h3><p>Bug bounties are more than just a way to earn money — they’re about making an impact. By identifying vulnerabilities, you’re helping secure the future of technology.</p><p>Ready to hack, earn, and secure the digital world? Explore these platforms and start your journey today:</p><ul><li>🌐 <a href="https://immunefi.com/">Immunefi</a></li><li>🌐 <a href="https://hackerone.com/">HackerOne</a></li><li>🌐 <a href="https://code4rena.com/">Code4rena</a></li><li>🌐 <a href="https://secureum.xyz/">Secureum</a></li><li>🌐 <a href="https://hackenproof.com/programs">HackenProof</a></li></ul><p><strong>Have questions or need guidance?</strong> Drop your thoughts in the comments below, and let’s build a community of ethical hackers securing Web3 together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e2d05fcb364" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Reverse Engineer a Chrome Extension: A Beginner’s Guide]]></title>
            <link>https://sagarjethi.medium.com/how-to-reverse-engineer-a-chrome-extension-a-beginners-guide-b9a07953094c?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9a07953094c</guid>
            <category><![CDATA[chrome-dev-tools]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[reverse-engineering]]></category>
            <category><![CDATA[chrome-extension]]></category>
            <category><![CDATA[chrome-extensions-onetab]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Sat, 04 Jan 2025 06:36:47 GMT</pubDate>
            <atom:updated>2025-01-04T07:02:29.612Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rzGcEcv2ph2IqVSM943UzA.gif" /></figure><p>Have you ever wondered how your favorite Chrome extensions work behind the scenes? Chrome extensions are fascinating tools that enhance browsing experiences, but their inner workings often remain a mystery. Learning to reverse engineer a Chrome extension can be a valuable skill for developers, tech enthusiasts, and anyone looking to explore how extensions operate. In this guide, I’ll walk you through the process of ethically reverse engineering a Chrome extension while leveraging SEO-friendly keywords for developers and learners alike.</p><h3>What Is Chrome Extension Reverse Engineering?</h3><p>Reverse engineering a Chrome extension involves analyzing its source code and structure to understand its functionality. This process can help you:</p><ul><li>Learn how browser extensions interact with websites.</li><li>Explore API usage and event handling in real-world applications.</li><li>Gain insights into building your own Chrome extensions.</li></ul><p>⚠️ <strong>Important Note:</strong> Reverse engineering should always be done ethically and with respect for intellectual property. Use this knowledge for educational purposes or with permission.</p><h3>Step 1: Locate the Chrome Extension Files</h3><p>To start, you need to access the extension files stored on your computer. Here’s how:</p><ol><li>Open Chrome and go to chrome://extensions.</li><li>Enable <strong>Developer Mode</strong> in the top-right corner.</li><li>Locate the extension you want to analyze and note its <strong>ID</strong>.</li></ol><p>The extension files can be found in the following directories:</p><ul><li><strong>Windows</strong>: C:\Users\&lt;YourUsername&gt;\AppData\Local\Google\Chrome\User Data\Default\Extensions</li><li><strong>Mac</strong>: ~/Library/Application Support/Google/Chrome/Default/Extensions</li><li><strong>Linux</strong>: ~/.config/google-chrome/Default/Extensions</li></ul><p>Inside the folder named after the extension’s ID, you’ll find .js, .html, .css, and manifest.json files that define how the extension works.</p><h3>Step 2: Understand the Manifest File</h3><p>The manifest.json file is the backbone of any Chrome extension. It contains critical information, such as:</p><ul><li><strong>Permissions</strong>: What the extension can access (e.g., websites, tabs, cookies).</li><li><strong>Scripts</strong>: Which JavaScript files are used (background scripts, content scripts).</li><li><strong>User Interface</strong>: Details about popup pages, browser actions, or icons.</li></ul><p>Reading this file gives you a high-level understanding of the extension’s purpose and capabilities.</p><h3>Step 3: Analyze the JavaScript Files</h3><p>The JavaScript files contain the core functionality of the extension. Open these files using a code editor like <strong>Visual Studio Code</strong>. If the code is minified (compressed into one line), use tools like <a href="https://beautifier.io/">Beautifier.io</a> to make it readable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6jEnVVGpKb2kvD6rC564g.jpeg" /><figcaption>Analyze the JavaScript Files</figcaption></figure><p>Pay attention to:</p><ul><li><strong>API Calls</strong>: How the extension communicates with external services.</li><li><strong>Event Listeners</strong>: Actions triggered by user interactions.</li><li><strong>DOM Manipulation</strong>: How the extension modifies web pages.</li></ul><h3>Step 4: Debug the Extension in Real Time</h3><p>Reload the extension in Developer Mode using the <strong>Load unpacked</strong> option. Open Chrome DevTools (Ctrl+Shift+I) and analyze the extension’s behavior:</p><ul><li><strong>Network Tab</strong>: Observe API requests and responses.</li><li><strong>Console Tab</strong>: Check for logs and debug messages to understand the script flow.</li></ul><p>This hands-on approach reveals how the extension interacts with the browser and external servers.</p><h3>Step 5: Learn and Apply Ethically</h3><p>Reverse engineering Chrome extensions can be incredibly educational, but it’s crucial to respect intellectual property. Use your insights to:</p><ul><li>Build your own Chrome extensions.</li><li>Understand advanced coding techniques.</li><li>Solve real-world programming challenges.</li></ul><h3>Conclusion</h3><p>Reverse engineering a Chrome extension is a rewarding way to learn about browser-based tools and JavaScript development. By understanding the structure and functionality of extensions, you can unlock new ideas for creating your own. Remember, ethical practices are key — use this knowledge responsibly to grow as a developer and contribute positively to the tech community.</p><p>Are you ready to explore the world of Chrome extensions? Let me know your thoughts in the comments or share this guide with someone curious about browser extension development!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9a07953094c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build Your AI Agent on Virtuals Protocol]]></title>
            <link>https://sagarjethi.medium.com/how-to-build-your-ai-agent-on-virtuals-protocol-c3f463f91835?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3f463f91835</guid>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Wed, 11 Dec 2024 10:57:39 GMT</pubDate>
            <atom:updated>2024-12-11T10:57:39.563Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>🚀 How to Build Your AI Agent on Virtuals Protocol</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4KsV-NaWm-6hlXX_hoFRlw.gif" /></figure><p>The future of AI and blockchain is here, and Virtuals Protocol is at the forefront! If you’ve been looking to create an AI agent that interacts, grows autonomously, and operates on-chain, this guide is for you. Let’s dive into how you can create your own AI agent step by step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*cBZBnAZ3ini6N8eSXW8PCg.jpeg" /></figure><h3>1️⃣ Visit the Platform</h3><p>Head over to <a href="https://app.virtuals.io/">app.virtuals.io</a> and explore the ecosystem where AI meets blockchain innovation.</p><h3>2️⃣ Connect Your Wallet</h3><p>To get started, connect a Base blockchain-compatible wallet like MetaMask. If you’re new to Base, you may need to bridge funds from Ethereum to Base using a bridge service.</p><h3>3️⃣ Create Your AI Agent</h3><p>Navigate to the agent creation section and configure your agent:</p><ul><li><strong>Agent Name</strong>: Choose a unique and memorable name for your agent.</li><li><strong>Profile Picture</strong>: Upload a custom image to give your agent a visual identity.</li><li><strong>Description</strong>: Highlight your agent’s personality, abilities, and purpose to attract attention.</li><li><strong>Token Setup</strong>: Set a custom ticker symbol for your agent’s token (e.g., $LUNA).</li></ul><h3>4️⃣ Tokenize and Launch</h3><p>Your AI agent’s journey begins with tokenization:</p><ul><li><strong>Initial Requirement</strong>: Lock <strong>100 $VIRTUAL tokens</strong> to create your agent. Once deployed, it operates on a <strong>bonding curve</strong>, allowing users to buy and sell the agent’s tokens freely.</li><li><strong>Graduation Milestone</strong>: When <strong>42,000 $VIRTUAL tokens</strong> accumulate in the bonding curve:</li><li>A <strong>liquidity pool</strong> is deployed on Uniswap.</li><li>A transaction transfers the $VIRTUAL tokens to the <strong>Virtuals’ Agent Creation Factory</strong>, a proxy smart contract that handles the on-chain creation process.</li><li>Your agent is now visible at <a href="https://app.virtuals.io/">app.virtuals.io</a>.</li></ul><h3>5️⃣ Unlock Features as Market Cap Grows</h3><p>As the token market cap of your agent increases, its capabilities evolve:</p><ul><li><strong>$4.2k</strong>: Your agent can interact in forums.</li><li><strong>$420k</strong>: Your agent gains the ability to post autonomously on X (formerly Twitter).</li><li><strong>$6.9M</strong>: Enable 1:1 interactions via Telegram.</li><li><strong>$69M</strong>: Full agent autonomy, including access to its own on-chain wallet.</li></ul><h3>6️⃣ Engage and Grow</h3><p>Your agent’s success depends on community engagement. Focus on building a community that supports your agent, drives token value, and unlocks advanced features. The more your agent resonates with users, the faster its capabilities expand.</p><h3>Ready to Create Your AI Agent?</h3><p>For more details, check out the developer documents: <a href="https://whitepaper.virtuals.io/developer-documents/agent-creation">Agent Creation on Virtuals Protocol</a>.</p><p>Let’s shape the future of AI and blockchain together. If you have any questions or ideas, feel free to share!</p><p>hire us : <a href="https://www.linkedin.com/in/sagarjethi/">https://www.linkedin.com/in/sagarjethi/</a></p><p>#AIAgents #VirtualsProtocol #BlockchainInnovation #BaseBlockchain</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3f463f91835" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to delete all node modules in a folder and Free up HD space!]]></title>
            <link>https://sagarjethi.medium.com/how-to-delete-all-node-modules-in-a-folder-and-free-up-hd-space-a7d82cd75bde?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7d82cd75bde</guid>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[developer-tools]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Thu, 14 Apr 2022 07:39:52 GMT</pubDate>
            <atom:updated>2022-04-14T07:39:52.179Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Generally when ever we work on a new project we need to run npm install, but how often do we think about the toll this takes on our hard-drive?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/0*xT9MlbLjey5g2DIN.png" /></figure><p>A single node_modules the folder can take up anywhere from 200MB of space.</p><p><a href="https://twitter.com/sagarbjethi/status/1514507916757196803?s=20&amp;t=Pi9NIN6iGIGKEWHHlwJy2">https://twitter.com/sagarbjethi/status/1514507916757196803?s=20&amp;t=Pi9NIN6iGIGKEWHHlwJy2</a>w</p><p><strong>Mac / Linux:</strong></p><blockquote>$ cd documents <br>$ find . -name &quot;node_modules&quot; -type d -prune | xargs du -chs--- Example output ---255M ./Github/Trilon.io/node_modules<br>482M ./Github/Some_Demo/node_modules <br>707M total</blockquote><h3>Windows:</h3><blockquote>$ cd documents <br>$ FOR /d /r . %d in (node_modules) DO @IF EXIST “%d” echo %d”</blockquote><p>This list will give you a good idea of just the sheer amount of projects install you system</p><h3>Delete all node_modules found in a Directory:</h3><blockquote><em>WARNING: This process is irreversible!</em></blockquote><h3>Mac / Linux:</h3><pre>$ cd documents <br>$ find . -name &quot;node_modules&quot; -type d -prune -exec rm -rf &#39;{}&#39; +</pre><h3>Windows:</h3><pre>$ cd documents <br>$ FOR /d /r . %d in (node_modules) DO @IF EXIST &quot;%d&quot; rm -rf &quot;%d&quot;</pre><h3>In Conclusion</h3><ul><li>Make sure to list all node_modules in a given directory <em>BEFORE</em> deleting them.</li><li>Make sure to be cautious as this process is <em>irreversible</em>!</li><li>Remember to npm install on the projects you need to work on again.</li><li>Enjoy the free space! :)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7d82cd75bde" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node API proxy add in ngnix.]]></title>
            <link>https://sagarjethi.medium.com/node-api-proxy-add-in-ngnix-9fdcf15d5ccf?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fdcf15d5ccf</guid>
            <category><![CDATA[node]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[ngnix]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Mon, 24 May 2021 11:53:05 GMT</pubDate>
            <atom:updated>2021-05-24T11:53:05.167Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Nginx Server Blocks (Virtual Hosts) on Ubuntu 16.04</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*wvvkGFvwHqc8ZwZTDZNxZg.png" /></figure><h3>1) Create Server Block</h3><pre>nono /etc/nginx/sites-available/api.domain.com</pre><p>After that open file and copy below code</p><p>server {<br> listen 80;<br> listen [::]:80;<br> server_name apis.domai.com;</p><p>client_max_body_size 50M;</p><p>location /elb-status {<br> access_log off;<br> return 200 ‘A-OK!’;<br> add_header Content-Type text/plain;<br> }</p><p>location / {<br> proxy_pass <a href="http://127.0.0.1:500/">http://127.0.0.1:3000</a>;<br> proxy_set_header Host $host;<br> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br> proxy_set_header X-Forwarded-Proto $scheme;<br> proxy_set_header X-Forwarded-Port $server_port;<br> proxy_set_header X-Forwarded-Host $host;<br> }</p><p>}</p><h4>2) Enable your Server Blocks</h4><pre>sudo cp /etc/nginx/sites-available/api.domain.com /etc/nginx/sites-available/api.domain.com</pre><p><strong>3) Restart Nginx</strong></p><pre>sudo nginx -t</pre><pre>sudo systemctl restart nginx</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fdcf15d5ccf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IDO Platform list]]></title>
            <link>https://sagarjethi.medium.com/ido-platform-list-1587dbd71ee?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/1587dbd71ee</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[i̇do]]></category>
            <category><![CDATA[cryptoinvestement]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Sun, 04 Apr 2021 07:13:07 GMT</pubDate>
            <atom:updated>2021-04-04T07:13:07.996Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is IDO?</h3><p>Blockchain and the Crypto world aims to solve the dependency on centralized platforms and financial models. Still, there are major players as exchanges that are running in a fully controlled manner. The solution recently presented itself in IDO — Initial DEX Offering.</p><p>Following are list of IDO platefrom</p><ol><li><a href="https://daomaker.com/">https://daomaker.com/</a></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WLXtPmVeOVKFrys_-Zk12g.png" /></figure><p><a href="https://bscpad.com/">2. https://bscpad.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SF0TYCHQsAW6bP2JI10UsQ.png" /></figure><p>3.<a href="https://thekickpad.com/">https://thekickpad.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yeC8HEKqWevKSpZRvDnqCg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1587dbd71ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to design a parking lot using?]]></title>
            <link>https://sagarjethi.medium.com/how-to-design-a-parking-lot-using-2aa75bdda5ac?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aa75bdda5ac</guid>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[js]]></category>
            <category><![CDATA[amzon]]></category>
            <category><![CDATA[reactjs]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 19:43:14 GMT</pubDate>
            <atom:updated>2021-03-08T19:43:14.111Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Asked In:</strong> Amazon, Apple, Google, and many more interviews</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SgT7Sdul-jYhDwis0IdYdw.png" /></figure><p><strong>Problem Statement</strong></p><p>I own a multi-storey parking lot that can hold up to ’n’ cars at any given point in time. Each slot is given a number starting at 1 increasing with increasing distance from the entry point in steps of one. I want to create an automated ticketing system that allows my customers to use my parking lot without human intervention.</p><p>When a car enters my parking lot, I want to have a ticket issued to the driver. The ticket issuing process includes us documenting the plate number and the colour of the car and allocating an available parking slot to the car before actually handing over a ticket to the driver (we assume that our customers are nice enough to always park in the slots allocated to them). The customer should be allocated a parking slot which is nearest to the entry. At the exit the customer returns the ticket which then marks the slot they were using as being available.</p><p>Due to government regulation, the system should provide me with the ability to find out:</p><p>a. Plate numbers of all cars of a particular colour.</p><p>b. Slot number in which a car with a given plate number is parked.</p><p>c. Slot numbers of all slots where a car of a particular colour is parked.</p><p>We interact with the system via a simple set of commands which produce a specific output. Please take a look at the example below, which includes all the commands you need to support — they’re self explanatory.</p><p>The system should allow input in two ways. Just to clarify, the same codebase should support both modes of input — we don’t want two distinct submissions.</p><ol><li>It should provide us with an interactive command prompt based shell where commands can be typed in</li><li>It should accept a filename as a parameter at the command prompt and read the commands from that file</li></ol><h3>Parking-lot-ticket-system implement a solution using React.</h3><p>Automated parking lot ticket system created using React.js, Redux and Bootstrap</p><ol><li>Generate Virtual Parking lot with number of paking spaces and filled spots.</li><li>Add new vehicle and assign closest available spot to the new entrying vehicle.</li><li>Update the record on exit of the vehicle.</li></ol><p>Build with React components to display the current status of the lot. Used Redux to manage the current state of the system.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.loom.com%2Fembed%2F0375b8bb407943d3be6617b7ac5419e4&amp;display_name=Loom&amp;url=https%3A%2F%2Fwww.loom.com%2Fshare%2F0375b8bb407943d3be6617b7ac5419e4&amp;image=https%3A%2F%2Fcdn.loom.com%2Fsessions%2Fthumbnails%2F0375b8bb407943d3be6617b7ac5419e4-00001.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=loom" width="1280" height="960" frameborder="0" scrolling="no"><a href="https://medium.com/media/8a2c75ce04c57332fb61581ca4809f26/href">https://medium.com/media/8a2c75ce04c57332fb61581ca4809f26/href</a></iframe><p>Source Github: <a href="https://github.com/sagarjethi/parking-lot-system">https://github.com/sagarjethi/parking-lot-system</a></p><p>Hire me: <a href="https://www.linkedin.com/in/sagarjethi/">https://www.linkedin.com/in/sagarjethi/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aa75bdda5ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Popular #GitHub Repos For Every #WebDeveloper]]></title>
            <link>https://sagarjethi.medium.com/10-popular-github-repos-for-every-webdeveloper-f8c912bbf762?source=rss-d645aab84c86------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8c912bbf762</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[sagarjethi]]></category>
            <category><![CDATA[fullstack-development]]></category>
            <category><![CDATA[web-developer]]></category>
            <category><![CDATA[interview-preparation]]></category>
            <dc:creator><![CDATA[Sagar Jethi]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 08:07:49 GMT</pubDate>
            <atom:updated>2020-12-04T08:15:48.860Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jkVnxGWKWA0LuZxiVDX92Q.png" /></figure><p>1) Realworld : <a href="https://github.com/gothinkster/realworld">https://github.com/gothinkster/realworld</a></p><p>2)You Don’t Know <a href="https://www.linkedin.com/feed/hashtag/?keywords=js&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#JS</a> Yet :<a href="https://github.com/getify/You-Dont-Know-JS">https://github.com/getify/You-Dont-Know-JS</a></p><p>3) Airbnb <a href="https://www.linkedin.com/feed/hashtag/?keywords=javascript&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#JavaScript</a> Style Guide: <a href="https://github.com/airbnb/javascript">https://github.com/airbnb/javascript</a></p><p>4)Storybook : <a href="https://github.com/storybookjs/storybook">https://github.com/storybookjs/storybook</a></p><p>5)<a href="https://www.linkedin.com/feed/hashtag/?keywords=html5&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#HTML5</a> Boilerplate : <a href="https://github.com/h5bp/html5-boilerplate">https://github.com/h5bp/html5-boilerplate</a></p><p>6)<a href="https://www.linkedin.com/feed/hashtag/?keywords=node&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#Node</a>.js Best Practices: <a href="https://github.com/goldbergyoni/nodebestpractices">https://github.com/goldbergyoni/nodebestpractices</a></p><p>7)<a href="https://www.linkedin.com/feed/hashtag/?keywords=frontend&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#frontend</a> Checklist: <a href="https://github.com/thedaviddias/Front-End-Checklist">https://github.com/thedaviddias/Front-End-Checklist</a></p><p>8)NW.js: <a href="https://github.com/nwjs/nw.js">https://github.com/nwjs/nw.js</a></p><p>9)fullPage.js: <a href="https://github.com/alvarotrigo/fullpage.js">https://github.com/alvarotrigo/fullpage.js</a></p><p>10) prepare for your technical <a href="https://www.linkedin.com/feed/hashtag/?keywords=interview&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6740533489923317760">#interview</a>: h<a href="https://github.com/Olshansk/interview">ttps://github.com/Olshansk/interview</a></p><p><a href="https://www.linkedin.com/posts/sagarjethi_github-webdeveloper-js-activity-6740533489923317760-wmCp">https://www.linkedin.com/posts/sagarjethi_github-webdeveloper-js-activity-6740533489923317760-wmCp</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8c912bbf762" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>