<?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 Yash Jadhav on Medium]]></title>
        <description><![CDATA[Stories by Yash Jadhav on Medium]]></description>
        <link>https://medium.com/@yashjadhav1595?source=rss-bf2f67d11a8c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ncLMx2VkihUM7HsYVvUAYg.png</url>
            <title>Stories by Yash Jadhav on Medium</title>
            <link>https://medium.com/@yashjadhav1595?source=rss-bf2f67d11a8c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:49:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yashjadhav1595/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[Web3 System Design: A Deep Dive into Blockchain Architecture, EVM & Smart Contracts]]></title>
            <link>https://medium.com/@yashjadhav1595/web3-system-architecture-under-the-hood-blockchain-smart-contracts-the-evm-272ffcd43b28?source=rss-bf2f67d11a8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/272ffcd43b28</guid>
            <category><![CDATA[account-abstraction]]></category>
            <category><![CDATA[blockchain-architecture]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[evm]]></category>
            <category><![CDATA[web3-system-architecture]]></category>
            <dc:creator><![CDATA[Yash Jadhav]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 18:18:50 GMT</pubDate>
            <atom:updated>2026-10-06T18:29:36.722Z</atom:updated>
            <content:encoded><![CDATA[<h4>How decentralized applications manage state, execution, storage, transactions, and account abstraction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bUU0jeVS6phJsq4BFv9Ukw.png" /></figure><p>In our <strong>previous article</strong>, we shattered one of the most stubborn myths in the crypto space: the idea that your digital assets sit inside your wallet. We established that your tokens live exclusively as balances on a globally distributed bank ledger, and your wallet is simply a cryptographic keychain used to prove ownership. We also looked at the monumental shift from rigid, single-key accounts (EOAs) to programmable <strong>Smart Contract Accounts</strong>, which behave less like static keys and more like dynamic security systems.</p><p><a href="https://medium.com/@yashjadhav1595/ledgers-vs-wallets-what-you-actually-own-in-crypto-014059a23b25">Ledgers vs. Wallets: Where Your Crypto Actually Lives</a></p><p>But if you are a software engineer, systems architect, or core builder, knowing that the wallet is just a keychain isn’t enough. You need to know how the rest of the engine works. When you transition from building traditional Web2 platforms to architecting Web3 applications, your fundamental assumptions about state management, execution environments, and computational costs are completely turned upside down.</p><p>Let’s strip away the marketing buzzwords and look at the actual system design of a production-ready Web3 application, tracking exactly how data moves, executes, and settles across the decentralized stack.</p><h3>The Surface Level: A Brief Nod to the Web2 Outershell</h3><p>Before we dive deep into the blockchain core, we must acknowledge how a user actually interacts with a Web3 application. If you look at the outermost layer of a Decentralized Application (dApp), it looks deceptively similar to a traditional Web2 app.</p><pre>┌────────────────────────────────────────────────────────┐<br>│                   THE WEB2 OUTERSHELL                  │<br>│                                                        │<br>│  ┌────────────────┐    ┌───────────────────────────┐   │<br>│  │  FRONTEND UI   │    │      CACHING BACKEND      │   │<br>│  │ (Next.js/React)│ ──&gt;│ (FastAPI/NodeJS/GraphQL)  │   │<br>│  └───────┬────────┘    └─────────────┬─────────────┘   │<br>└──────────┼───────────────────────────┼─────────────────┘<br>           │                           │<br>           ▼                           ▼<br>┌────────────────────────────────────────────────────────┐<br>│                   THE WEB3 CORE ENGINE                 │<br>│                                                        │<br>│             [ DECENTRALIZED STATE MACHINE ]            │<br>│            Blockchain Ledger &amp; Smart Contracts         │<br>└────────────────────────────────────────────────────────┘</pre><p><strong>The Frontend UI:</strong> Built using standard web tools like Next.js or React, the frontend handles nothing more than presentation logic. It collects user input, reads state from the network, and structures user intentions into clean cryptographic requests.</p><p><strong>The Backend &amp; Database (The Contextual Off-Chain Layer):</strong> In high-performance Web3 systems, you still use traditional databases (like PostgreSQL) and backend servers (like FastAPI or Node.js). However, their role is strictly relegated to <em>off-chain indexing and speed</em>. They track webhooks, cache event logs, index historical metadata, and serve user profiles.</p><p><strong>Here is the golden rule of Web3 system design:</strong> The off-chain backend and database are purely optional optimization layers. If your server crashes or your private database disappears entirely, your application’s core logic, absolute security, and true state remain completely unaffected.</p><p>Why? Because the entire source of truth, user balance sheet, and execution logic live downstairs — inside the <strong>decentralized state machine</strong>.</p><h3>1. The Blockchain Engine: A Shared, Deterministic State Machine</h3><p>To design systems for Web3, you must stop thinking of the blockchain as a slow database.</p><blockquote>Instead, you must think of it as a <strong>globally distributed, single-threaded, deterministic state machine</strong>.</blockquote><p>When a regular database processes data, it relies on a central authority to say, “This write operation happened at exactly 10:01 AM.” In a decentralized network, thousands of independent computers (nodes) must reach an agreement (consensus) on the sequence of events without a central coordinator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5Bg9VM6hf-jOznbXPYpmQ.png" /></figure><p>Mathematically, a blockchain functions as a state transition system. Let <strong><em>s</em></strong> represent the current state of the entire universe (all account balances, smart contract code, and variable storage). When a user submits a signed transaction <strong><em>tx</em></strong>, the network applies a strict State Transition Function, commonly represented as: <strong><em>S(s,tx) → s’</em></strong></p><p>If the transaction is valid according to the predefined rules of the network, the system outputs a brand new state <strong><em>s’</em></strong>. If the transaction is invalid (e.g., a user tries to spend tokens they don’t own, or a cryptographic signature is forged), the state transition function fails completely, reverts any changes, and returns the original state <strong><em>s</em></strong>.</p><p>Every single node on the network processes the exact same transactions in the exact same sequence. Because the state transition function is completely deterministic, every node arrives at the identical output state <strong><em>s’</em></strong>. This absolute consensus is what makes the ledger unalterable and completely trustless.</p><h3>2. The Execution Environment: Inside the Virtual Machine (EVM)</h3><p>Where does this state transition function actually run? It executes inside a sandboxed environment built into the nodes, the most prominent example being the <strong>Ethereum Virtual Machine (EVM)</strong></p><p>The EVM is a stack-based virtual machine that executes bytecode. When you write a smart contract, you write it in a human-readable language like Solidity. Before deployment, that code is compiled down into raw, low-level operational codes (Opcodes) — such as ADD, BALANCE, SSTORE (save to storage), and SLOAD (load from storage).</p><pre>┌────────────────────────────────────────────────────────┐<br>│               THE EVM EXECUTION PIPELINE               │<br>│                                                        │<br>│    Solidity Code ──&gt; Compiled Bytecode ──&gt; EVM Opcodes │<br>│                                           (ADD, SSTORE)│<br>└───────────────────────────────────┬────────────────────┘<br>                                    │<br>                                    ▼<br>                       ┌─────────────────────────┐<br>                       │   THE GAS CONSTRAINT    │<br>                       │                         │<br>                       │ Every Opcode costs Gas  │<br>                       │ Out of Gas = Reversion  │<br>                       └─────────────────────────┘</pre><p>When an RPC node passes a transaction to the EVM, the virtual machine handles the execution sequentially. Unlike a standard Web2 server, which can dynamically scale its hardware, allocate more RAM, or launch multiple parallel threads to handle high traffic, the EVM runs on hard, shared physical constraints:</p><ul><li><strong>Single-Threaded Execution:</strong> To prevent race conditions and ensure perfect determinism across thousands of global nodes, transactions are processed sequentially within a block.</li><li><strong>The Halting Problem and Gas:</strong> In standard software engineering, an infinite loop (while(true)) will freeze a server, causing a denial-of-service failure. To solve this, Web3 systems use <strong>Gas</strong>. Every single opcode executed by the EVM costs a specific number of gas units, directly proportional to the computational effort required by the physical host nodes.</li></ul><p>If a user submits a transaction, they must pre-fund it with enough gas. If the transaction hits an infinite loop or runs out of gas mid-execution, the EVM halts immediately, throws an Out of Gas error, and rolls back every single state change made during that runtime window. However, the gas spent up to that microsecond is still collected by the network to compensate the nodes for their spent computing power.</p><h3>3. Smart Contracts: The Immutable Rules of Engagement</h3><blockquote>If the blockchain is the engine and the EVM is the combustion chamber, <strong>Smart Contracts</strong> are the programmatic tracks guiding the system.</blockquote><p>As we touched upon in our previous post, a smart contract is not “smart,” nor is it a legal contract. It is simply a persistent piece of code that has its own unique deployment address on the ledger, its own dedicated storage slots, and the ability to hold and transfer assets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*409O-GNIFlXIOpXYK3gZHw.png" /></figure><p>To truly understand smart contract system design, you must understand how it manages data internally. A smart contract has access to three primary data locations during execution:</p><ul><li><strong>Memory:</strong> A temporary, clean byte-array that is completely wiped clean the millisecond the transaction finishes executing. It is incredibly cheap to use.</li><li><strong>Calldata:</strong> An immutable, temporary receive-buffer that contains the exact arguments passed by the external transaction caller.</li><li><strong>Storage:</strong> A persistent, key-value store mapping 2²⁵⁶ slots of 32-byte words directly onto the permanent blockchain ledger.</li></ul><p>Modifying data inside <strong>Storage</strong> (SSTORE) is one of the most expensive engineering operations in all of software design. Writing a new variable to storage can cost up to 20,000 units of gas, whereas reading or writing to temporary <strong>Memory</strong> costs next to nothing. Therefore, Web3 system design requires developers to optimize their algorithms aggressively, minimizing storage writes to keep transaction fees practical for end users.</p><p>Once a smart contract is compiled and deployed to the network, its code becomes entirely <strong>immutable</strong>. Unlike a Web2 server where you can push hotfixes or patch bugs quietly at midnight, a deployed smart contract cannot be modified. If there is a logical vulnerability in your code, it exists permanently on the open ledger for anyone to exploit.</p><h3>4. Advanced Architecture: The Shift to Intent-Driven Pipelines</h3><blockquote>Now let’s tie this core infrastructure back to the major breakthrough we closed with last time: <strong>Account Abstraction (ERC-4337)</strong>.</blockquote><p>In a traditional Web3 design, a user had to sign a transaction, pay for gas in the network’s native token (like ETH), and submit it directly to an RPC node. If they didn’t have the correct token for gas, the transaction was dead on arrival.</p><p>The modern Web3 system architecture decouples this process entirely by shifting from <em>transaction submission</em> to <em>intent generation</em>.</p><pre>┌───────────────────────────────────────────────────────────────────────────────┐<br>│                          MODERN INTENT-DRIVEN PIPELINE                        │<br>│                                                                               │<br>│  ┌───────────┐         ┌────────────────┐         ┌───────────┐   ┌─────────┐ │<br>│  │USER INTENT│ ──────&gt; │   MEMPOOL OF   │ ──────&gt; │  BUNDLER  │ ─&gt;│ENTRYPT. │ │<br>│  │ (UserOp)  │         │ USEROPERATIONS │         │ (Pay Gas) │   │CONTRACT │ │<br>│  └───────────┘         └────────────────┘         └───────────┘   └────┬────┘ │<br>└────────────────────────────────────────────────────────────────────────┼──────┘<br>                                                                         ▼<br>                                                               ┌────────────────┐<br>                                                               │ SMART CONTRACT │<br>                                                               │    ACCOUNT     │<br>                                                               └────────────────┘</pre><p><strong>The UserOperation:</strong> Instead of creating a heavy, low-level blockchain transaction, the user’s wallet constructs a high-level intent object called a UserOperation. This object states exactly what the user wants to accomplish (e.g., <em>&quot;Transfer 50 stablecoins to Bob&quot;</em>), alongside custom signature rules.</p><ol><li><strong>The Alt-Mempool:</strong> These operations do not go straight to the main network queue. Instead, they travel to a dedicated, decentralized waiting room called an alternative memory pool (Alt-Mempool).</li><li><strong>The Bundler:</strong> A specialized network actor called a <strong>Bundler</strong> monitors this pool. The Bundler takes multiple independent UserOperations, packages them together into one single, massive standard blockchain transaction, and submits it to the network. The Bundler pays the upfront gas fee out of its own pocket.</li><li><strong>The EntryPoint Contract &amp; Paymasters:</strong> The transaction hits a universal, highly secure smart contract on the blockchain called the EntryPoint. The EntryPoint validates each user&#39;s request against their specific <strong>Smart Contract Account</strong> rules. If a developer integrates a secondary contract called a <strong>Paymaster</strong>, the app can sponsor the user’s gas entirely or accept payment in standard stablecoins, completely shielding the end-user from the complex infrastructure spinning beneath them.</li></ol><h3>The Paradigm Shift of the Web3 Architect</h3><p>Designing systems for Web3 requires an entirely different mental model than building for the traditional web. In Web2, your engineering challenges revolve around managing physical scale, horizontal scaling, and optimizing microservices.</p><blockquote>In Web3, your engineering challenges revolve around <strong>maximizing security constraints, optimizing storage access, and designing predictable, deterministic workflows.</strong></blockquote><p>By shifting your application’s core state out of private silos and onto an open, shared ledger, you aren’t just building a system that resists tampering — you are creating software that can seamlessly connect with other protocols worldwide, building a fully open and composable digital ecosystem.</p><h3>References and Research Work</h3><ul><li><a href="https://ethereum.org/roadmap/account-abstraction/">Account abstraction | ethereum.org</a></li><li><a href="https://www.alchemy.com/overviews/what-is-account-abstraction">What is ERC-4337?</a></li><li><a href="https://www.alchemy.com/overviews/how-do-smart-contract-wallets-work">How do ERC-4337 smart contract wallets work?</a></li><li><a href="https://eips.ethereum.org/EIPS/eip-4337">ERC-4337: Account Abstraction Using Alt Mempool</a></li><li><a href="https://docs.erc4337.io/bundlers/index.html">📦 Bundlers - ERC-4337 Documentation</a></li><li><a href="https://docs.safe.global/advanced/erc-4337/overview">What is ERC-4337? - Safe Docs</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=272ffcd43b28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ledgers vs. Wallets: Where Your Crypto Actually Lives]]></title>
            <link>https://medium.com/@yashjadhav1595/ledgers-vs-wallets-what-you-actually-own-in-crypto-014059a23b25?source=rss-bf2f67d11a8c------2</link>
            <guid isPermaLink="false">https://medium.com/p/014059a23b25</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[Yash Jadhav]]></dc:creator>
            <pubDate>Fri, 02 Oct 2026 21:10:13 GMT</pubDate>
            <atom:updated>2026-10-02T21:38:08.440Z</atom:updated>
            <content:encoded><![CDATA[<h4>Think your crypto lives in your wallet? Think again. Learn how blockchain ledgers work and how smart contract accounts are changing asset security.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C5i6BA2l9cAzCRuFX-JXNA.png" /></figure><h3>Think of the Blockchain Like a Giant Public Bank Ledger</h3><p>Imagine a bank with a giant database.</p><p>The database says:</p><pre>Alice → ₹10,000<br>Bob   → ₹5,000<br>Yash  → ₹20,000</pre><p>The money isn’t physically sitting inside each person’s mobile banking app.</p><p>Your banking app simply gives you a way to <strong>prove who you are and request changes to the bank’s records</strong>.</p><p>Crypto works with a similar mental model.</p><p>The blockchain maintains the state of the network.</p><p>For example:</p><pre>Wallet A → 5 ETH<br>Wallet B → 12 ETH<br>Wallet C → 0.5 ETH</pre><p>Those balances are part of the blockchain’s state.</p><p>Your wallet doesn’t download 5 ETH into your phone.</p><p>Instead, it gives you the cryptographic ability to say:</p><blockquote><em>“I am authorized to move the 5 ETH associated with this account.”</em></blockquote><p>That request is then checked by the blockchain.</p><h3>So What Does a Wallet Actually Do?</h3><p>At the simplest level, a wallet manages <strong>cryptographic keys</strong>.</p><p>Think of those keys as extremely powerful digital credentials.</p><p>A simplified picture looks like this:</p><pre>YOU<br>                  │<br>                  ▼<br>             ┌─────────┐<br>             │ Wallet  │<br>             └────┬────┘<br>                  │<br>             Uses a key<br>                  │<br>                  ▼<br>             ┌─────────┐<br>             │ Sign    │<br>             │ Request │<br>             └────┬────┘<br>                  │<br>                  ▼<br>             ┌──────────┐<br>             │Blockchain│<br>             └────┬─────┘<br>                  │<br>          Checks the request<br>                  │<br>                  ▼<br>             Updates state</pre><p>So a wallet is less like a <strong>pocket</strong> and more like a <strong>key ring</strong>.</p><p>It doesn’t carry your assets around.</p><p>It carries what you need to prove that you are allowed to control them.</p><h3>The Key Is the Important Part</h3><p>This is where traditional crypto wallets become both powerful and inconvenient.</p><p>For a traditional Ethereum wallet, often called an <strong>Externally Owned Account (EOA)</strong>, the private key is extremely important.</p><p>You can think of it like the master key to a safe.</p><pre>             🔑 PRIVATE KEY<br>                    │<br>                    ▼<br>              ┌──────────┐<br>              │   EOA    │<br>              └────┬─────┘<br>                   │<br>                   ▼<br>               Blockchain</pre><p>Whoever controls the private key can generally authorize transactions from that account.</p><p>That’s useful.</p><p>But it also creates a major problem.</p><h3>What happens if you lose the key?</h3><p>There may be no customer support department to call.</p><p>No:</p><blockquote><em>“Forgot password? Click here.”</em></blockquote><p>No central administrator can simply reset the account for you.</p><p>And if someone else gets your private key, they may be able to control the account.</p><p>This is one of the biggest differences between traditional apps and blockchain systems.</p><h3>Your Netflix Password Isn’t Your Netflix Account</h3><p>Here’s a simple comparison.</p><p>With a normal online service:</p><pre>You<br> │<br> ▼<br>Email + Password<br> │<br> ▼<br>Company Database<br> │<br> ▼<br>Account</pre><p>Lose your password?</p><p>You can usually reset it.</p><p>With a traditional crypto account:</p><pre>You<br> │<br> ▼<br>Private Key<br> │<br> ▼<br>Blockchain Account<br> │<br> ▼<br>Assets controlled by account</pre><p>Lose the key?</p><p>The system doesn’t automatically know that you’re the legitimate owner.</p><p>That’s because blockchain networks are designed to verify <strong>cryptographic authority</strong>, not your real-world identity.</p><p>This is one reason onboarding new users into Web3 has historically been difficult.</p><h3>What If the Wallet Could Be Smarter?</h3><p>Now imagine your wallet wasn’t simply controlled by one key.</p><p>Imagine you could tell it:</p><p><em>“Allow this phone to make small transactions.”</em></p><p><em>“Block transactions above $500.”</em></p><p><em>“Require two approvals for large transfers.”</em></p><p><em>“Let these three trusted people help me recover the account.”</em></p><p><em>“Allow this temporary key to work only for the next 24 hours.”</em></p><p>Suddenly, the wallet starts behaving less like a key.</p><p>It starts behaving like a <strong>programmable security system</strong>.</p><p>That is the basic idea behind <strong>smart contract accounts</strong> and <strong>account abstraction</strong>.</p><h3>From a Key to a Programmable Account</h3><p>A traditional wallet can be thought of like this:</p><pre>          ONE KEY<br>             │<br>             ▼<br>       ┌───────────┐<br>       │   ACCOUNT │<br>       └─────┬─────┘<br>             │<br>             ▼<br>        BLOCKCHAIN</pre><p>A smart account can look more like this:</p><pre>         USER REQUEST<br>              │<br>              ▼<br>      ┌────────────────┐<br>      │ Smart Account  │<br>      │                │<br>      │ • Check rules  │<br>      │ • Verify user  │<br>      │ • Set limits   │<br>      │ • Recover      │<br>      │ • Execute      │<br>      └───────┬────────┘<br>              │<br>              ▼<br>         BLOCKCHAIN</pre><p>The account itself contains logic.</p><p>That is the big architectural change.</p><p>Instead of saying:</p><p><em>“The correct private key signed this.”</em></p><p>the system can support richer rules such as:</p><p><em>“This request came from an approved device.”</em></p><p>or:</p><p><em>“This transaction is below the user’s spending limit.”</em></p><p>or:</p><p><em>“Two trusted guardians approved the recovery.”</em></p><p>The wallet becomes more programmable.</p><h3>A Simple Example: Your Debit Card</h3><p>Imagine your bank automatically blocks:</p><ul><li>a ₹10,000 transaction from a suspicious location,</li><li>a ₹1,00,000 purchase unless you approve it,</li><li>transactions made by an unknown device.</li></ul><p>Those are <strong>rules</strong>.</p><p>Now imagine having similar rules for a blockchain account.</p><p>For example:</p><pre>Normal transactions<br>       │<br>       ▼<br>✅ Automatically allowed<br></pre><pre>Transaction &gt; ₹50,000<br>       │<br>       ▼<br>🔐 Extra approval required<br></pre><pre>Unknown device<br>       │<br>       ▼<br> ❌ Blocked</pre><p>This is the type of flexibility programmable accounts can introduce.</p><h3>Enter Account Abstraction</h3><p><strong>Account Abstraction</strong> is a broad concept that makes blockchain accounts more programmable.</p><p>One important Ethereum implementation is <strong>ERC-4337</strong>.</p><p>You don’t need to memorize the standard to understand the idea.</p><p>The simplest way to think about it is:</p><blockquote><strong><em>Account Abstraction separates what the user wants to do from the exact mechanics of how the blockchain transaction gets executed.</em></strong></blockquote><p>Instead of the user having to deal directly with all the blockchain plumbing, the infrastructure can handle more of it.</p><h3>But There Is Another Problem: Gas</h3><p>Even if your account is programmable, there is still another annoying question:</p><blockquote><em>Who pays for the blockchain transaction?</em></blockquote><p>Blockchains require computation.</p><p>Computation costs money.</p><p>That payment is generally called <strong>gas</strong>.</p><p>So imagine downloading an app and getting this message:</p><blockquote><em>“Welcome! Before using the app, first buy some cryptocurrency so you can pay the network.”</em></blockquote><p>That’s not a great onboarding experience.</p><p>And this is where another important piece of infrastructure appears.</p><h3>Bundlers: The Middlemen of User Intent</h3><p>With ERC-4337-style account abstraction, users can create something called a <strong>UserOperation</strong>.</p><p>Don’t let the name scare you.</p><p>Think of it simply as:</p><blockquote><strong><em>“Here is what I want my smart account to do.”</em></strong></blockquote><p>A simplified flow looks like this:</p><pre>               YOU<br>                │<br>                ▼<br>        &quot;Send ₹500 worth<br>          of tokens&quot;<br>                │<br>                ▼<br>        ┌──────────────┐<br>        │ UserOperation│<br>        └──────┬───────┘<br>               │<br>               ▼<br>        ┌──────────────┐<br>        │   Bundler    │<br>        └──────┬───────┘<br>               │<br>               ▼<br>          EntryPoint<br>               │<br>               ▼<br>        Smart Account<br>               │<br>               ▼<br>          Blockchain</pre><p>A <strong>bundler</strong> collects these operations and submits them to the blockchain through the account-abstraction infrastructure.</p><p>The user doesn’t need to understand every step.</p><p>And that is exactly the point.</p><h3>What About Paying the Gas for the User?</h3><p>Now we can introduce another useful component:</p><p><strong>Paymasters.</strong></p><p>A paymaster can sponsor eligible transactions.</p><p>Imagine a new user opening your Web3 application.</p><p>Instead of telling them:</p><blockquote><em>“Buy ETH first.”</em></blockquote><p>the application could potentially say:</p><blockquote><em>“Don’t worry. We’ll cover the network fee for your first few transactions.”</em></blockquote><p>Conceptually:</p><pre>             USER<br>               │<br>               ▼<br>        UserOperation<br>               │<br>               ▼<br>           Bundler<br>               │<br>               ▼<br>          EntryPoint<br>          ┌────┴────┐<br>          │         │<br>          ▼         ▼<br>     Smart Account  Paymaster<br>                       │<br>                       │<br>                 Pays eligible<br>                    gas fees</pre><p>From the user’s perspective, the experience can become much simpler.</p><p>They interact with the application.</p><p>The infrastructure handles much of the blockchain complexity underneath.</p><h3>From “Using Crypto” to “Using an App”</h3><p>This is perhaps the most important idea.</p><p>Early blockchain applications often exposed the infrastructure directly to the user.</p><p>The user had to think about:</p><ul><li>private keys</li><li>seed phrases</li><li>gas</li><li>network selection</li><li>token approvals</li><li>transaction confirmations</li><li>wallet popups</li></ul><p>For a blockchain engineer, these are normal concepts.</p><p>For a normal user, they can feel like unnecessary friction.</p><p>The long-term goal of abstraction is to move more of this complexity into the infrastructure.</p><pre>OLD EXPERIENCE<br><br>User<br> │<br> ├── Manage keys<br> ├── Find gas<br> ├── Confirm transactions<br> ├── Understand networks<br> └── Handle recovery<br><br><br>versus:<br><br><br>MORE ABSTRACTED EXPERIENCE<br><br>User<br> │<br> ▼<br>&quot;I want to buy this.&quot;<br> │<br> ▼<br>Application<br> │<br> ▼<br>Infrastructure<br> │<br> ▼<br>Blockchain</pre><p>The blockchain doesn’t disappear.</p><p>The complexity does.</p><h3>Traditional Wallet vs. Smart Account</h3><p>Here is the simplest comparison:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*Vlwwoz22bn5Je_p3A0tuuw.png" /></figure><p>The key difference isn’t simply:</p><blockquote><em>“Old wallet vs. new wallet.”</em></blockquote><p>It is:</p><blockquote><strong><em>Fixed authorization vs. programmable authorization.</em></strong></blockquote><h3>The Whole Architecture in One Picture</h3><p>If you remember only one diagram from this article, make it this one:</p><pre>YOU<br>                          │<br>                    &quot;I want to...&quot;<br>                          │<br>                          ▼<br>                 ┌─────────────────┐<br>                 │  AUTHENTICATION │<br>                 │                 │<br>                 │ Key / Passkey   │<br>                 │ Session Key     │<br>                 └────────┬────────┘<br>                          │<br>                          ▼<br>                 ┌─────────────────┐<br>                 │ SMART ACCOUNT   │<br>                 │                 │<br>                 │ • Verify        │<br>                 │ • Check rules   │<br>                 │ • Authorize     │<br>                 │ • Execute       │<br>                 └────────┬────────┘<br>                          │<br>                          ▼<br>                 ┌─────────────────┐<br>                 │ INFRASTRUCTURE  │<br>                 │                 │<br>                 │ UserOperation   │<br>                 │ Bundler         │<br>                 │ EntryPoint      │<br>                 │ Paymaster       │<br>                 └────────┬────────┘<br>                          │<br>                          ▼<br>                 ┌─────────────────┐<br>                 │   BLOCKCHAIN    │<br>                 │                 │<br>                 │ Ownership       │<br>                 │ Balances        │<br>                 │ Contract State  │<br>                 └─────────────────┘</pre><p>This is the bigger picture:</p><p><strong>You express an intention.</strong></p><p><strong>The account decides whether you’re allowed to perform it.</strong></p><p><strong>The infrastructure gets it processed.</strong></p><p><strong>The blockchain updates the state.</strong></p><h3>So Where Does Your Crypto Actually “Live”?</h3><p>Let’s finally answer the original question.</p><p>Your crypto is not sitting inside your wallet app.</p><p>Your wallet isn’t a container full of coins.</p><p>The blockchain maintains the <strong>official record of ownership and balances</strong>.</p><p>Your wallet provides the credentials — and increasingly, the logic — needed to control that account.</p><p>A useful mental model is:</p><pre>Wallet  =  Keys + Authentication<br>Account =  Rules + Authorization<br>Ledger  =  State + Ownership Record</pre><p>Or, even simpler:</p><blockquote><strong><em>The wallet holds the key.</em></strong></blockquote><blockquote><strong><em>The account defines the rules.</em></strong></blockquote><blockquote><strong><em>The blockchain holds the record.</em></strong></blockquote><h3>Why This Matters</h3><p>This may look like a technical detail.</p><p>It isn’t.</p><p>The distinction affects almost everything built on top of blockchain infrastructure.</p><p>If you’re building:</p><ul><li>a fintech application,</li><li>a Web3 game,</li><li>a payments platform,</li><li>a DeFi application,</li><li>a digital identity system,</li><li>a tokenized-asset platform,</li></ul><p>you eventually have to answer the same question:</p><blockquote><strong><em>How should users prove that they are allowed to perform an action?</em></strong></blockquote><p>Traditional wallets give you one answer.</p><p>Programmable accounts give you many more.</p><p>And that opens the door to experiences that can feel much closer to the applications people already understand.</p><h3>The Bigger Shift</h3><p>Blockchain started with a powerful idea:</p><blockquote><strong><em>We don’t need a central authority to maintain the ledger.</em></strong></blockquote><p>The next challenge is different:</p><blockquote><strong><em>How do we make decentralized systems easy enough for ordinary people to use?</em></strong></blockquote><p>Account abstraction is one piece of that puzzle.</p><p>It doesn’t change the fundamental idea that the blockchain is the source of truth.</p><p>Instead, it changes the <strong>front door</strong> through which users interact with that truth.</p><p>And perhaps that is the real evolution:</p><p>The future of blockchain UX may not be about teaching everyone how wallets, gas, signatures, and transaction pipelines work.</p><p>It may be about building infrastructure so good that <strong>most users never need to know.</strong></p><p>And that is where the difference between a wallet, an account, and a ledger becomes much more than terminology.</p><p>It becomes an architectural principle.</p><h3>A final mental model</h3><p>When you’re thinking about blockchain systems, remember these three lines:</p><blockquote><strong><em>The ledger remembers.</em></strong><em><br></em><strong><em>The account decides.</em></strong><em><br></em><strong><em>The wallet proves.</em></strong></blockquote><p>Everything else is infrastructure built around those three ideas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rcHAQaho8eRhgAlG2isVmA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=014059a23b25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>