Salary Dapp

Demo

About

The problem it solves We see a lot of __startups__ coming up these days and a lot of companies are already there hustling on solving __real-life__ issues. One such problem that exists in the space is the mode of __payment__ in the companies and this continues to grow with a lot of people jumping into the space. Using __Blockchain technology__ we want to improve this problem for the __payment__ structure of these startups and companies by allowing an organization's __admin__ to send payments to their __employees__ and manage it all in one place. So we built a __decentralized infrastructure tooling application__ that does this work for startups/companies by adding employees and paying them a __salary in one click__. This decentralized application also solves the problem of multiple hands involved in the simple task of paying employees. In startups/companies we see that a specific team is involved to manage salaries of employees that can simply be done by a single person. So using this application we allow a single person/admin to pay all of their employees at once on basis of the position they are working on. This would save a lot of resources for a startup/company as the task done by a team can now be done by a single person. With the growing space of blockchain technology, we want to improve this classic system of salary management of a startup/company in a single click. We hope to improve this project more in the future and add some interesting features to it like allowing multiple startups/companies to register on our application and manage their employee's other important details. We aim to make it a fully-fledged application for companies to improve their workflow and act as an important tool. Thank you for giving us this chance to participate in this Hackathon.

How it's made

Challenges we ran into While building this project, we encountered a few issues and learned so many new things. This was the first time we worked on __Next.js__ and we are extremely happy that we can put a working project. We used __Tailwind CSS__ to design stuff and make it look better. The very first challenge was to decide whether to allow anyone to call __functions__ in our __solidity__ code or not. We ended up deciding not to allow anyone else to call functions other than the person who deployed the __contract__. But to allow Judges to test our application and use its all features for judgment purposes, we removed the __onlyOwner__ modifier from our contract so that our application functionalities can be accessible. We wanted to make our app gasless and implement __Biconomy__ for the same purpose, but due to time restrictions and our ongoing college exams we had to drop the idea of using __Biconomy__. We hope to use it in the future for learning purposes. We faced some issues in implementing the __Connect Wallet__ button in our app's all components when using __Next.js__. We wanted to make a single component for that but due to our limited knowledge in using __Next.js__ we couldn't do it, so the solution we came across this problem was to copy-paste the Connect Wallet button's logic in each component that needed it. We also had issues with our __Solidity__ code, we wanted to keep it simple and cost less gas, we spent a lot of time learning about this stuff, and at last, we were able to __optimize__ our contract a little.