• Transfer of data from smart contract to simple database in order to reduce gas expense
• Proxy attendance can be removed
• Attendance data can be secured
• Immutable data assurance
• Reduction in employee conflicts in his presence
• Clear counting of employee inside institute
• Secured Payment transactions through blockchain
• Cashless end to end payments
Many many challenges. To start off, I was not very familiar with Web3 technologies, meaning I had to learn everything from scratch. After I miraculously coded the smart-contract I had to deploy it to the Goerli Testnet, one problem though I needed GoerliETH to pay for the gas fees. After scouring the web for a working ETH faucet I finally got the smart-contract deployed to the blockchain. Finally, the ThirdWeb framework was fairley new, so there was still very limited documentation. And that was just the Web3 Backend. I also had quite a bit of trouble using the implementing the Verbwire API call in react, since this is a very new API there was not much documentation, however after a lot of trial and error I was able to get it to work! The frontend went a little bit more smoothly, but was still an incredible learning experience.
To reduce the gas expense we used simple database and transferred smart contracts to simple database.
Discussion