Cover photo

"Layer" Development Journey at EIF 3.0: week 4

๐Ÿ‘‹ 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 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.

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.

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.

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.