Renaiss @renaissxyz's Hackathon S1 has entered community voting, with 45+ teams submitting. The deadline is July 17 at 23:59 UTC+8.

Winning obviously matters, but the more critical question is what happens after the awards: how many winning works can enter the Tool Directory, be found and used by users, and continue to be maintained.
This community vote accounts for 40%, while the team evaluation accounts for 60%.
Award-winning projects can receive a Tool Directory Listing, and may also appear in the Renaiss Lab, Protocol, or community channels—but they still must pass quality, security, and relevance reviews. Winning does not automatically mean becoming an official product, and this boundary must be clearly stated.
The 45+ submissions show developers are willing to come. What truly determines the quality of the ecosystem is what Renaiss ultimately leaves behind. Submission volume can only show the event has momentum; it’s the usable tools in the Directory that will fill in product capabilities.
The Renaiss Protocol is still in open beta. Gacha and Marketplace are already available. There are real use cases for valuation, tracking, and analytics tools as well. Regular users shouldn’t only watch the award list next; check whether the works enter the Directory, whether they’re actually used after they do, and whether they still receive continued updates months later.
The hackathon is responsible for discovering works, while the Tool Directory is responsible for filtering tools. What Renaiss needs to prove this time is whether it can turn a one-time development event into a long-term, usable product add-on layer.