The past week as an EthIndia Fellow has been a whirlwind of exciting projects and learning opportunities. One of the main areas of focus for me was researching and exploring the ERC 998 standard, as well as working on a contract using this standard. Additionally, I delved into the Revise SDK, which offers a powerful backend for programming NFTs to interact with various applications, utilities, and data feeds. Finally, I spent some time looking into the Google Fit API and how this data can be leveraged to create on-chain dynamic NFTs.

First and foremost, ERC 998 is a relatively new standard that allows for the creation of NFTs that are composable and can be owned by other NFTs. This means that NFTs can now have other NFTs inside of them, which opens up a whole new world of possibilities for developers and artists. In order to better understand the standard, I spent some time researching various resources, including the official ERC 998 documentation, blog posts, and forums. By the end of the week, I felt comfortable enough with the standard to start writing my own contract using it.

Using the ERC 998 standard, I started to write a contract that allowed for the creation of NFTs that could own other NFTs. This was an exciting project for me, as I had never worked on an NFT contract before. I spent a lot of time reading through the documentation and experimenting with different code snippets until I was able to create a functional contract that complied with the ERC 998 standard.

In addition to working with ERC 998, I also spent some time exploring the Revise SDK. This software development kit allows developers to create NFTs that can interact with various applications, utilities, and data feeds. This is an exciting development for the NFT space, as it allows for more dynamic and useful NFTs. I spent some time playing around with the SDK, reading through the documentation, and experimenting with different code snippets. While I didn't have time to create a full-fledged project using the SDK, I gained a solid understanding of how it works and how it could be used in the future.

Finally, I spent some time looking into the Google Fit API and how this data could be leveraged to create dynamic NFTs. The Google Fit API allows developers to access fitness data from a user's Google account, including data from various fitness apps and wearables. I was particularly interested in the idea of creating NFTs that could change over time based on a user's fitness data. For example, an NFT could change its appearance or unlock new features based on a user's daily step count or calorie burn. While I didn't have time to fully explore this concept, I did gain a solid understanding of the Google Fit API and how it could be used to create more dynamic NFTs in the future.

Overall, the past week as an EthIndia Fellow was an exciting and educational experience. I learned a lot about the ERC 998 standard, worked on my own contract using this standard, explored the Revise SDK, and looked into the Google Fit API. While I still have a lot to learn, I feel that I made significant progress over the course of the week and I'm excited to continue exploring the world of NFTs and blockchain development.