<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Aniket Singh</title>
        <link>https://paragraph.com/@aniket-singh</link>
        <description>undefined</description>
        <lastBuildDate>Sun, 06 Sep 2026 21:14:59 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 6]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-6</link>
            <guid>Q3IdGhHcapWWE1rdpQwJ</guid>
            <pubDate>Tue, 21 Mar 2023 11:44:39 GMT</pubDate>
            <description><![CDATA[👋 Hey! web3 builders, As I reach the halfway point of my fellowship with ETHIndia 3.0, I am thrilled to announce that the alpha release of the extension is forthcoming. I am excited to share the significant progress that I have made during week 6 of the fellowship and pleased with the work accomplished thus far. In week 5, I successfully implemented the feature of custom network implementation, enabling developers to add any EVM-compatible network in the extension and interact with their Sol...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! web3 builders,</p><p>As I reach the halfway point of my fellowship with ETHIndia 3.0, I am thrilled to announce that the alpha release of the extension is forthcoming. I am excited to share the significant progress that I have made during week 6 of the fellowship and pleased with the work accomplished thus far.</p><p>In week 5, I successfully implemented the feature of custom network implementation, enabling developers to add any EVM-compatible network in the extension and interact with their Solidity smart contracts.</p><p>During week 6, I made substantial advancements in the development of the extension. I have fixed several bugs and implemented several new features to improve the user experience.</p><p>One of the critical features I added was the auto-fetching of newly deployed contracts. Previously, newly deployed contracts were not visible in the web view immediately after deployment. However, with this feature, they will be visible right away, significantly improving the development process.</p><p>Another feature I implemented was the ability to toggle immutable transactions in the console. This feature allows for the visualization of immutable transactions with essential parameters, making it easier to understand and monitor transactions. This feature was already present for mutable transactions.</p><p>Furthermore, I added the auto-fetch balance feature, which automatically retrieves the current balance of the account after any transaction in the extension. Additionally, a refresh feature was provided to fetch the balance manually.</p><p>The most significant feature I developed in week 6 was providing sidebar extension support to activate the Layer extension. This extension enables the activation of the extension directly from the sidebar, eliminating the need to activate the extension using the VSCode command. This sidebar extension will also support the activation of other extensions in the Layer series that will be introduced in the future.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/21cdb31dfa674004e493fc50dc0850a28e9014135e34b07ab3b6c487cdbc0a29.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Overall, week 6 was highly productive and successful for my fellowship. I am eager to launch the alpha version of the extension as soon as possible, and I am confident that the features and improvements implemented will provide users with an enhanced and efficient development experience.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/cbdd2de555dd336d2d271a09605670c2d6971a26403ceaecd7596c45cdcfca67.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 5]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-5</link>
            <guid>xv5EuRXg5VMWtASnOiPR</guid>
            <pubDate>Tue, 14 Mar 2023 12:15:01 GMT</pubDate>
            <description><![CDATA[👋 Hey! web3 builders, As I approach the halfway point of my fellowship, I am excited to share the progress I have made during week 5 of the ETHIndia fellowship 3.0. I am pleased with the work accomplished thus far and eager to continue building on this momentum. In week 4 I implemented the most important feature which is the execution of smart contract functions. This extension provides an interface for developers to interact with smart contracts by passing the required parameters. All funct...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! web3 builders,</p><p>As I approach the halfway point of my fellowship, I am excited to share the progress I have made during week 5 of the ETHIndia fellowship 3.0. I am pleased with the work accomplished thus far and eager to continue building on this momentum.</p><p>In week 4 I implemented the most important feature which is the execution of smart contract functions. This extension provides an interface for developers to interact with smart contracts by passing the required parameters. All functions present in the smart contract were categorized into four types: view, pure, payable, and non-payable.</p><p>In week 5, I continued to contribute to the development of Layer and implemented two significant features, editing extension configuration, and one-time password requirement.</p><p>The editing extension configuration feature allows smart contract developers to customize the network configuration for the extension. Developers can use their custom RPC endpoints provided by Alchemy, Infura, Quicknode, and other providers. They can also add new EVM networks of their choice to perform smart contract operations. The extension also provides the facility to remove the network configuration.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/0d3bb6b01df357fc0572f7239ee0de42fc9d5550a94e70b8bc5fd16f86591c95.png" alt="Adding new network" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Adding new network</figcaption></figure><p>In addition, I implemented the one-time password requirement feature. It allows developers to enter the password only once for the selected wallet and interact with the smart contract any number of times without worrying about entering the password repeatedly.</p><p>Furthermore, I made some fixes and implemented the feature of fetching gas prices before any transaction on a selected EVM network. The extension now internally fetches the current gas price on the selected network before executing any transaction.</p><p>Overall, week 5 was a productive and successful week for my fellowship, and I am eager to implement more critical features in the upcoming weeks.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/cbdd2de555dd336d2d271a09605670c2d6971a26403ceaecd7596c45cdcfca67.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 4]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-4</link>
            <guid>nVWcFd8O46VB9uqZMrUm</guid>
            <pubDate>Thu, 09 Mar 2023 07:10:33 GMT</pubDate>
            <description><![CDATA[👋 Hey! web3 builders, Another productive week has passed during my fellowship, and I am excited to share my progress. I am pleased with the work I have accomplished thus far, and I am eager to continue building on this momentum. In week 3 of my fellowship, I successfully accomplished the task of deploying the selected smart contract on a chosen network. I also implemented several crucial features that are essential for efficient smart contract execution and deployment. In the fourth week of ...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! web3 builders,</p><p>Another productive week has passed during my fellowship, and I am excited to share my progress. I am pleased with the work I have accomplished thus far, and I am eager to continue building on this momentum.</p><p>In week 3 of my fellowship, I successfully accomplished the task of deploying the selected smart contract on a chosen network. I also implemented several crucial features that are essential for efficient smart contract execution and deployment.</p><p>In the fourth week of the EIF3.0 project, I continued to contribute to the development of Layer. One of the main features that I implemented was adding the details of the deployed smart contract in the compiled JSON file. This feature ensures that the deployment history of the smart contract remains consistent, even when multiple sessions are being used. developers can reference the same smart contract in different sessions with ease.</p><p>Furthermore, I identified and fixed several bugs that prevented the extension from interacting with local networks such as Hardhat and Ganache. Previously, the extension environment did not display local network accounts because Layer does not use extension accounts on local networks.</p><p>The most important feature that I implemented in week 4 was smart contract function execution. The extension now provides developers with an interface to execute smart contract functions. These functions are categorized into four types: view, pure, payable, and non-payable. View and pure functions do not require transaction signing to read blockchain data. In contrast, payable and non-payable functions require transaction signing to write or modify blockchain data.</p><p>Overall, week 4 was a productive and successful week for my fellowship, and I look forward to implementing more critical features in the upcoming weeks.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/cbdd2de555dd336d2d271a09605670c2d6971a26403ceaecd7596c45cdcfca67.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 3]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-3</link>
            <guid>lTSgAyzmrpDTjIhNoCOz</guid>
            <pubDate>Wed, 01 Mar 2023 12:28:11 GMT</pubDate>
            <description><![CDATA[👋 Hey! web3 builders, This has been another amazing week of the fellowship and I can&apos;t wait to share what I&apos;ve been doing. In the third week of the Ethereum India Fellowship 3.0 program, I made significant contributions towards building a complete solution for developers to deploy, debug and execute Solidity smart contracts using the "Layer" vscode extension. In the second week of the EIF3.0, I contributed to the implementation of several features in Layer. One of the major accompl...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! web3 builders,</p><p>This has been another amazing week of the fellowship and I can&apos;t wait to share what I&apos;ve been doing. In the third week of the Ethereum India Fellowship 3.0 program, I made significant contributions towards building a complete solution for developers to deploy, debug and execute Solidity smart contracts using the &quot;Layer&quot; vscode extension.</p><p>In the second week of the EIF3.0, I contributed to the implementation of several features in Layer. One of the major accomplishments was the successful implementation of success events for all mutable transactions. This feature enables developers to send transactions and view the results in the Transaction object format, making it easier to debug and track the status of transactions.</p><p>Additionally, I implemented success events for all immutable and readable function calls. Another key contribution was implementing error events for all errors that occur while sending mutable transactions. With this feature, developers can easily see the reason for the failure and take appropriate action to fix it.</p><p>In the third week of the EIF3.0 project, I continued to contribute to the development of Layer. One of the main features that I implemented was the ability to select a contract that needs to be deployed from the dropdown on the home page. This feature allows developers to choose the contract that they want to work on easily. I also added a feature that shows all the parameters that need to be passed for the contract constructor if present. The feature lists all the parameters present in the constructor and takes the input.</p><p>Moreover, I implemented the ability to post the selected contract data to the extension backend and get all the constructor parameters. Another feature that I added was the ability to check if all the required constructor parameters are passed or not and if the provided gas limit is sufficient or not.</p><p>Another feature that I added was the ability to deploy the select solidity smart contract on the selected chain by passing all the required parameters. Finally, after deployment, Layer shows the deployed contract address of the selected smart contract on the selected blockchain network.</p><p>In conclusion, Layer is an extension that makes Solidity smart contract development on VSCode easier and more efficient. The features implemented in the third week of the EIF3.0 will enhance the debugging, interaction, and deployment of smart contracts, making Layer an essential tool for Solidity smart contract development.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/6d67e0675609b537852636b6118ce5b1c2eb7d8bc4fda58f8aed2812b2a4839e.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 2]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-2</link>
            <guid>Hlv4q6Zhpv56emBDKsid</guid>
            <pubDate>Sun, 19 Feb 2023 06:49:09 GMT</pubDate>
            <description><![CDATA[👋 Hey! web3 builders, This has been another amazing week of the fellowship and I can&apos;t wait to share what I&apos;ve been doing. In the second week of the Ethereum India Fellowship 3.0 program, I made significant contributions towards building a complete solution for developers to deploy, debug and execute Solidity smart contracts using the "Layer" vscode extension. One of my major accomplishments was the successful implementation of success events for all mutable transactions, allowing ...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! web3 builders,</p><p>This has been another amazing week of the fellowship and I can&apos;t wait to share what I&apos;ve been doing. In the second week of the Ethereum India Fellowship 3.0 program, I made significant contributions towards building a complete solution for developers to deploy, debug and execute Solidity smart contracts using the &quot;Layer&quot; vscode extension.</p><p>One of my major accomplishments was the successful implementation of success events for all mutable transactions, allowing developers to send transactions and view the results in the Transaction object format. This feature makes it easier to debug and track the status of transactions.</p><p>I was also responsible for implementing success events for all immutable and readable function calls, making it easy for developers to interact with their smart contracts and retrieve data without having to write custom code.</p><p>Another key contribution was implementing error events for all errors that occur while sending mutable transactions. This means that if a transaction fails, developers can easily see the reason for the failure and take appropriate action to fix it.</p><p>Finally, I implemented events for calling immutable and readable function calls. This means that if a call to a function in a smart contract fails, developers can easily see the reason for the failure and take appropriate action.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/97b054243d628c31543f22108e2ca89b0b20c6af9c35f123befbcac3cc8709cf.jpg" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>All of these contributions represent significant progress toward building a comprehensive solution for developers to deploy, debug, and execute Solidity smart contracts. With the continued progress in the coming weeks, the &quot;Layer&quot; extension is poised to become an essential tool for any developer working on Ethereum-based projects.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/6d67e0675609b537852636b6118ce5b1c2eb7d8bc4fda58f8aed2812b2a4839e.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA["Layer" Development Journey at EIF 3.0: week 1]]></title>
            <link>https://paragraph.com/@aniket-singh/layer-development-journey-at-eif-3-0-week-1</link>
            <guid>5mc25umMSsc4tX05S1Bb</guid>
            <pubDate>Sat, 11 Feb 2023 17:58:45 GMT</pubDate>
            <description><![CDATA[👋 Hey! Web3 builders, get ready with your smart contracts because I&apos;ll be sharing the development journey of "Layer - smart contract interaction tool" at EIF 3.0 fellowship. The ETHIndia Fellowship program is an 8-week mentor-led program for web3 developers to learn, build, and collaborate to boost their careers in web3 and blockchain technology. During the program selection process, I was lucky enough to be selected for the Gwei track. In the first week, we had an onboarding session an...]]></description>
            <content:encoded><![CDATA[<p>👋 Hey! Web3 builders, get ready with your smart contracts because I&apos;ll be sharing the development journey of <strong>&quot;Layer - smart contract interaction tool&quot;</strong> at EIF 3.0 fellowship. The ETHIndia Fellowship program is an 8-week mentor-led program for web3 developers to learn, build, and collaborate to boost their careers in web3 and blockchain technology.</p><p>During the program selection process, I was lucky enough to be selected for the Gwei track. In the first week, we had an onboarding session and some exciting workshops. At the end of the onboarding session, I received the SBT for being in the cohort of the EIF 3.0 Gewi track.</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://opensea.io/assets/0xfe8321df99317c365797c4f95c2dbd9beec8c694/27">https://opensea.io/assets/0xfe8321df99317c365797c4f95c2dbd9beec8c694/27</a></p><p>In addition to the building project, one thing that excites me the most is the learning materials that are provided to us to improve our knowledge and understanding of the latest blockchain research. Here are some of them 👇</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dev.to/spalladino/a-beginners-intro-to-coding-zero-knowledge-proofs-c56">https://dev.to/spalladino/a-beginners-intro-to-coding-zero-knowledge-proofs-c56</a></p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mirror.xyz/0xeee68aECeB4A9e9f328a46c39F50d83fA0239cDF/K63khDZank5wrfzCulDq5R6dfN2m4zGanO5lsAxfg-w">https://mirror.xyz/0xeee68aECeB4A9e9f328a46c39F50d83fA0239cDF/K63khDZank5wrfzCulDq5R6dfN2m4zGanO5lsAxfg-w</a></p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://worldcoin.org/blog/developers/privacy-deep-dive">https://worldcoin.org/blog/developers/privacy-deep-dive</a></p><h3 id="h-layer-milestones-that-were-accomplished-in-week-1" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">“Layer” milestones that were accomplished in week 1</h3><p>Layer is a VSCode extension for testing, debugging, deploying, and executing solidity smart contracts. The project supports the feature of an inbuilt key pair and password-protected wallet, which can be used to interact with smart contracts present in the Hardhat project&apos;s current working directory.</p><p>Developers can deploy and execute smart contracts on any EVM-compatible blockchain network by adding a network configuration in the extension environment.</p><p>Both of the features I mentioned have already been implemented. A developer can create a new account, import accounts using a private key, import accounts using a Keystore file, export the account private key, and export the account Keystore file. By exporting the private key, accounts that work in extension can also be used in other wallets like metamask.</p><p>Additionally, there is a feature of token transfer that was implemented in the extension. The extension wallet allows developers to transfer tokens directly to other wallets on the selected network, and the balance of the selected account can also be seen.</p><p>Apart from adding the above features, the most significant thing I implemented in week 1 was loading all compiled contracts from the hardhat projects&apos; artifacts folder to the webview.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/95674c96f33c236a5c6ab8667766cff4ec700c1addf4bbfdcdc33af18dd38471.png" alt="Current status of the main page" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Current status of the main page</figcaption></figure><p>However, the extension is still in the development phase, so there will be major changes in the UI/UX after the alpha release.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/0200bb675a90a2dabac70fac4b8ed96bf1791d7cc96a9f53832ba66ee0498ea2.png" alt="Current status of the Wallet page" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Current status of the Wallet page</figcaption></figure><h3 id="h-the-long-term-goal-of-the-project" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">The long-term goal of the project</h3><p>As part of this project, I intend to offer remix-IDE-like features to smart contract developers in Vscode so that they can test and debug their smart contracts offline too, since most developers prefer Vscode to develop full-stack projects.</p><p>In addition, it will make onboarding new developers in the web3 space easier with a simple smart contract tool in VSCode.</p>]]></content:encoded>
            <author>aniket-singh@newsletter.paragraph.com (Aniket Singh)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/6d67e0675609b537852636b6118ce5b1c2eb7d8bc4fda58f8aed2812b2a4839e.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>