<?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 Prakhar Sharma on Medium]]></title>
        <description><![CDATA[Stories by Prakhar Sharma on Medium]]></description>
        <link>https://medium.com/@prakharentp2002?source=rss-ac53500fcb43------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*7c4RnsBN1gjAJ7h5</url>
            <title>Stories by Prakhar Sharma on Medium</title>
            <link>https://medium.com/@prakharentp2002?source=rss-ac53500fcb43------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 02:45:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@prakharentp2002/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[The Private Key Management Problem on Blockchain Part-1]]></title>
            <link>https://medium.com/@prakharentp2002/the-private-key-management-problem-on-blockchain-part-1-0f2ca1f4b49e?source=rss-ac53500fcb43------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f2ca1f4b49e</guid>
            <category><![CDATA[private-key]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Prakhar Sharma]]></dc:creator>
            <pubDate>Fri, 30 Aug 2024 13:11:59 GMT</pubDate>
            <atom:updated>2024-08-30T13:11:59.288Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*XK9sDY808LG5NiSG.png" /></figure><p>Suppose you have a blockchain-powered web app where every user registers on the app you create a web3 wallet for him/her.</p><p>After a certain amount of time, the count of users goes up to freaking 10000, now you have to manage private and public keys for all of those 10,000 users!!.</p><p>What if I tell you there are some ways not to manage those keys instead manage one, yup just one!</p><h3>There are 2 main concepts I like for this huge key pair management:</h3><ol><li>Hierarchical Deterministic Wallets (HD Wallets)</li><li>Account Abstraction</li></ol><p><strong>Hierarchical Deterministic Wallets (HD Wallets):</strong></p><p>This concept of HD wallets was proposed originally for Bitcoin where the same problem was being experienced by the users, if they were to to create 5 accounts, they were needed to manage 10 keys(5-Private, 5-Public).</p><p>So BIP-39 was proposed in 2013, in which a mnemonic seed phase(common random english language words) was introduced for deterministic wallets. Before this private keys were used to create accounts.</p><p>Now using mnemonic seed phases one can generate tons of private-public key pairs. BIP-44 was added to it, where BIP-44 introduced the addition of a hierarchical structure for account creation using mnemonic phases.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*1VPwGwYaaf9o5sH7.jpeg" /></figure><p>Credit: BIP32</p><p>As per the above flow in the picture, we can see from a master seed(mnemonic) that a master node(master key-pair) is created and from which n number of wallet accounts are created at path m/0-n(This is the path of the tree structure we are following), n is the purpose of the path, m/44 for example will be followed here for BIP-44.</p><p>Further upon describing the path code for the specified chain, you will be using, here it is m/0/0-n for example(m/0/60 for Ethereum chain).</p><p>Finally, the wallet’s keypair is generated at path m/0/0/0/0-n, which will be used to do the transactions on-chain.</p><p>By following this pretty structure we just need to remember the private key and public key of the master pair created at path m. If someone wants to fetch those deterministic keypairs when needed, they can just give the same path again(ex: m/44/60/0/0) to the root node(master keypair) and hence will receive the same keypair signer again and again to use.</p><p>Note: <a href="https://docs.ethers.org/v5/">ethers</a> supports the creation of HD wallets, so we can simply integrate from there. :)</p><p>Follow for Part-2</p><p>Thankyou</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f2ca1f4b49e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>