Hello there! @QuestArcade 
Good day to you too.
Thank you for your kind words and encouragement!
Rest assured, we’re working day night to ensure that CodeHive is ready to be tested and enjoyed by all. 
Your support means a lot to us, all the best to you too mate. will check out your project shortly 
Welcome codeHive to Tron hackathon season 6. I like your project because it aims to spur creativity among developers.
After it challenge on codeHive would the code be made open source for other developers to learn from ?
Thanks for the reply, it’s only right cause courtesy goes side by side with gratitude.
Moving forward, using a visual tag system to communicate the status of reported issues is an effective way to keep people informed and engaged with the platform.
What criteria will be utilized to determine whether to use each tag, and how do you intend to maintain consistency and accuracy in identifying reported issues?
Thanks for the interest mate, means alot 
Yes the cods will be made available once the bounty is claimed…
@ to everyone
The big note i would like to add up is,
Wow so amazing project i would love to try this one out…
Glad you like our project Thanks for the support !
For your first question, we’ll address reports based on their frequency and severity. Our reporting system will cover common issues like invalid problem statements, incorrect input/output, and flawed problem diagrams, along with custom report descriptions.
To maintain consistency in identifying reported issues, our team will conduct regular reviews and ensure that tags are applied accurately.
It’s encouraging to hear about your approach to prioritizing and correcting reported concerns based on frequency and severity, as well as your dedication to preserving uniformity in the tagging process.
After reading your reply, I have a question;
How do you plan to assess the severity of reported issues, and what criteria will be used to determine which issues require immediate attention versus those that can be addressed at a later time?
Since the person putting up bounties has to pay(fees) to post questions and could lose money if something goes wrong, they’ll likely be careful to avoid making mistakes. As for what to focus on first, we deal with any problems that come up during deployment of question/solution for that question on the users end. After that, we can look into any bounties that are claimed incorrectly. However, those kinds of mistakes are expected to be rare based on how the contract work
Thanks for your reply, given the potential financial consequences, it’s reasonable that those posting bounties would be cautious to avoid mistakes.
How do you intend to educate users about the potential risks and challenges of posting bounties, and what tools will be available to help them successfully navigate the process?
Thanks for the Question,
answer to question 1 : Before a questioner submits a question, the user will be prompted with a dialog box to alert them about potential risks. They’ll be prompted to ensure all details in the question form are correct, as any errors will result in forfeiting their fees without refund.
answer to question 2 : I assume you’re referring to the tools we use throughout the process, from question submission to solution. We using Judge0 API for code compilation, TronQL for retrieving blockchain questions, and Pinata IPFS for data storage.
feel free to ask more question. more than happy to answer them.
Thank you 
It’s helpful to know the tools you’re using to facilitate the question submission and solution process on Code Hive.
How are you getting user feedback on their experiences with these products, and what steps will you take to resolve any usability or performance issues that users raise?
To gather user feedback for Code Hive, we’ll utilize Tron Forum/Twitter, alongside we have also planned to implement the feedback form within the platform itself.
As for resolving usability or performance issues, we are implementing the reporting system in app, I believe I’ve addressed this in detail in a reply here :
Thank you
Thank you for this detailed response, was easy to comprehend first-hand. Using numerous channels, such as Tron Forum, Twitter, and an in-app feedback form, indicates your commitment to collecting customer input from a variety of sources.
I’ve one question; will users be able to see the status of their provided feedback, such as whether it was received, reviewed, or acted on, to promote openness and accountability in the feedback process?
Unfortunately, no. Since we are fully decentralized and do not store any user information such as email or phone numbers, we are unable to send responses to users. However, we will keep our Telegram and Discord groups updated with all the latest updates and features.
Thank you 
The project milestones have been updated and will continue to evolve as we move forward. For a detailed overview of our progress, check out our GitHub repository. 
I want to be sure on one part. If you are not so good at programming, this website is not for you. And you just put high-level developers together, so there will be a lot of competitive situation for small rewards. I wonder how you want to attract people to your platform by that logic
Hey there! @Dermov1
Thanks for the Question!
Yep, Code Hive is mainly for folks who already know a bit about coding. But don’t worry, we’re open to everyone, no matter your skill level. Even if you’re just starting out, there’s still stuff here for you to learn and get better at. Our goal is to make a friendly place where everyone can join in and help out. So, whether you’re a pro or just getting started, you’ll find something cool to do here and maybe even earn some rewards along the way!