onNFT: Naming projects is tough

Progress Report:

Now that the humongous task of finalising a project idea was complete, the only small, easy bit left was to actually build it 😛

  • My week began by curating a proposal for my project idea, and elaborating upon topics like motivation, objectives, USP and execution plan.

  • I then submitted my proposal to the Devfolio team, and proceeded to setting up a basic flow for the project.

  • This phase involved reading up on existing libraries implementing onramps, account abstraction, web2 logins etc.

  • During this week, I was able to achieve web2 based logins paired with SCW creation uniquely mapped to each user.

  • Further, I decided to use gelato relay to setup a flow which allows the dApp to pay users’ gas-fee, or let the user pay gas-fee in non eth currencies as well, using gas abstraction, thus making the users’ experience gas-less.

Next Steps:

  • The next step is to complete a flow where a user can gaselessly mint NFTs to their SCWs.

  • Once the above is achieved, I will try to integrate an Onramp to this flow, and make my NFT contract paid, so as to pay credit card based payments for buying NFTs.

  • I also aim to understand access control over these SCWs better, so as to have clearly defined custodies and security measures at each step of the process.

  • Last but not the least, I wish to come up with a better project name than “onNFT”.