Kue3 | Devpost

Homepage
Answering Questions
QuestionPage

Inspiration

There are numerous web applications, such as Brainly.in, Stack Overflow, and Course Hero, where users can ask or debate their questions. Despite having a very strong community, none of them offer rewards to the community members who volunteer their time to help others with their difficulties. Additionally, responses are frequently delayed, and sometimes users aren't even satisfied with the answers.

In order to address these problems, we created Kue3 as a platform which enables anybody to post questions at any time simply by connecting his wallet without having to sign in up or register , the one who is posting the question can also add some matics to the question pool so that the answer-er who provided the most satisfying response could be rewarded.

What it does

All the most recent queries and associated prize pools can be seen on the home page by just connecting your wallet. Its user interface is quite simple and open to the general public.

You can also post your own questions and deposit matics to the question pool. To save users' gas money after uploading, your question will be hosted on InterPlanetary File System (IPFS) . After posting your question, along with the prize fund and question title, will be displayed on the home page, which will be open and accessible to every user .

As all the questions will be displayed on the home page, allowing community members and subject matter experts with wallets connected to Kue3 to provide answers which will also be stored on IPFS . The questioner himself does not have the right to answer the question , The questioner then has the option to authorise the transfer of the MATICs from the question pool to the respondent who gave the best response as a token of appreciation for his time and knowledge. In this way, we can also get answers to our questions and thank answerers for their time and knowledge , following the wallet's connection Users in general can simply view all the questions and their replies without paying any gas fees if they don't wish to ask or answer any inquiries.

How we built it

For Front-End we used Next.js to enable server-side rendering thus better performance security along with Chakra UI to make components for our application . We utilised RainbowKit to link wallets since it is user-friendly and supports a variety of wallets. It also automatically manages wallet connection and disconnection, swaps connection chains is we are on wrong connection chain thus providing better experience to users . Our contract is written in Solidity, where we defined a struct for question and answer, mappings to get questions by the questioner's address as well as to to get questions by the question's id, mapping to get answers by the answer id, and all submitted answers to a question using the question id. Later, we defined functions to post questions, answers, for approving payment, to get the most recent questions, etc. Wagmi, which offers a collection of React Hooks, makes it simple to "Connect Wallet," display ENS and balance information, sign messages, communicate with contracts from the front end, and much more, is what we use to deal with and interact with our contract. For storing our data for questions and answers we are using IPFS through Infura IPFS api , for compiling and deploying our contract we have used hardhat and for testing our contract we have used Remix IDE . Our Contract is deployed on Polygon Testnet and our Front End application is deployed on Spheron.

Challenges we ran into

Even though I've been working on web development for a while, this was my first web 3.0 Hackathon, thus it was an interesting and difficult experience all around. The biggest obstacle I encountered during this amazing journey was structuring my project so that it operated with contracts rather than databases and APIs. Using wagmi to interface with the contract from Front-End presented a second problem for me. The third challenge was amusing because I had never heard of hardhat, making it difficult to even deploy or compile my contract. The fourth hurdle was storing our data for questions and answers using IPFS to overcome this, we used the Infura API but we have to migrate our app to

Accomplishments that we're proud of

It was the very first hackathon for one of the teammate, so it was a huge challenge and accomplishment for him. Another accomplishment would be using great set of tools that are best fit for the application.

What we learned

We learnt a lot from this hackathon, specially about server side rendering applications, IPFS and Filecoin but other than that we also learnt about the value of community and building in public.