<?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 Dev_lateefat on Medium]]></title>
        <description><![CDATA[Stories by Dev_lateefat on Medium]]></description>
        <link>https://medium.com/@dev_lateefah?source=rss-250c76ca3ddf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tu7IdObuWk-s2x62OLaTIQ.jpeg</url>
            <title>Stories by Dev_lateefat on Medium</title>
            <link>https://medium.com/@dev_lateefah?source=rss-250c76ca3ddf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:05:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dev_lateefah/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[What Brought About EIP-1155?]]></title>
            <link>https://medium.com/@dev_lateefah/what-brought-about-eip-1155-39a911730689?source=rss-250c76ca3ddf------2</link>
            <guid isPermaLink="false">https://medium.com/p/39a911730689</guid>
            <dc:creator><![CDATA[Dev_lateefat]]></dc:creator>
            <pubDate>Sat, 11 Oct 2025 02:05:41 GMT</pubDate>
            <atom:updated>2025-10-11T02:07:42.624Z</atom:updated>
            <content:encoded><![CDATA[<h4>Understanding how EIP-1155 solved the limitations of ERC-20 and ERC-721 by introducing a multi-token standard for Ethereum.</h4><p>An <strong>EIP (Ethereum Improvement Proposal)</strong> is a formal document that outlines new features and improvements for the Ethereum network. It provides a structured way for developers to propose and discuss updates that make Ethereum better over time.</p><p><strong>EIP-1155</strong>, also known as the <strong>Multi-Token Standard</strong>, was created to solve the limitations of two earlier token standards <strong>ERC-20</strong> and <strong>ERC-721</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/301/1*o-h0zvkMVnM1rc7yAn1vKg.png" /><figcaption>ERC-1155</figcaption></figure><h3>What Happened Before EIP-1155?</h3><h3>ERC-20 “The Fungible Token Standard” 🪙</h3><ul><li>Introduced to create a standard for <strong>fungible tokens</strong> (interchangeable tokens like <strong>UNI</strong>, <strong>USDT</strong>, etc.).</li><li>Ensured all fungible tokens behaved in the same way.</li><li><strong>Limitation:</strong> It could only represent <strong>fungible tokens</strong> i.e., coins or identical assets.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*nPnoe0rmZr4OHwNI8ws9jw.jpeg" /><figcaption>ERC-20 token coin</figcaption></figure><h3>ERC-721 “The Non-Fungible Token (NFT) Standard” 🖼️</h3><ul><li>Introduced to represent ownership of <strong>unique digital assets</strong> like <strong>collectibles</strong> or <strong>real-world assets (RWA)</strong>.</li><li>Each ERC-721 token is <strong>unique</strong> and <strong>non-interchangeable</strong>.</li><li><strong>Limitation:</strong> It could only handle <strong>one unique token type per contract</strong>, so multiple contracts were needed for different NFTs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*BfmlbTn6jRQd9oI4PfH-dQ.jpeg" /><figcaption>RERC-721 token, NFT</figcaption></figure><h3><strong>Example:</strong></h3><p>In an online game like <em>Free Fire</em> or <em>Call of Duty</em>, if a user wants to buy 20 different weapons, accessories, and coins, the system would need <strong>20 separate smart contracts, </strong>one for each asset type.</p><h3>🚀 The Birth of EIP-1155</h3><p><strong>EIP-1155</strong> was proposed by the blockchain gaming company <strong>Enjin</strong> to make it easier for gaming and digital asset platforms to manage multiple types of tokens (<strong>both fungible and non-fungible</strong>) within a single smart contract.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*boM5SuDJgHaP_G_e.png" /></figure><h3>What EIP-1155 Solved</h3><ul><li><strong>Multi-token support:</strong> One smart contract can manage both fungible and non-fungible tokens.</li><li><strong>Simplified management:</strong> Developers no longer need multiple contracts for different token types.</li><li><strong>Reduced gas fees:</strong> Multiple tokens can be sent in one transaction.</li><li><strong>Improved performance:</strong> Great for gaming, metaverse, and asset-heavy apps.</li></ul><h3><strong>🪙Why It Matters</strong></h3><p>EIP-1155 made Ethereum development more efficient by merging the best parts of ERC-20 and ERC-721. With one smart contract managing multiple token types, it opened the door for scalable, flexible asset systems.</p><p>#NFTs #developers #Web3 #Ethereum #EIPs</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39a911730689" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>