Thanks you for the translated summary 
2 Likes
Thank you for sharing the report and the results of the Buildathon.
Looking at the numbers, the overall event seems to have exceeded expectations with 6,000 participants compared to the 3,000 originally expected, which is clearly a positive outcome.
Personally, I think it would be great if the WhatsApp group of 50 participants could be nurtured and kept alive, rather than letting it fade away after the event. That could be a simple but effective way to cultivate ongoing relationships and keep those developers engaged with Astar. Beyond these figures, there aren’t many other metrics to analyze in the report.
I also took a look at the Instagram video mentioned from the winner team. Since I don’t speak Spanish, I might have missed it, but it didn’t seem to me that Astar was explicitly referenced.
Reading through the report, one thought that came to mind is that it could be very valuable if events like these were structured with a continuation phase after the hackathon. In this way, the teams that start building during the event could have the chance to further develop their ideas, with the ultimate goal of turning them into complete projects that might even be eligible for dApp Staking in the future.
This suggestion comes from the idea of avoiding that all the good work, contacts, and developer relationships built during the event simply end once it’s over, and instead ensuring that they are nurtured and supported afterwards.
These are just ideas that came to me while reading, but perhaps they could serve as useful reflections for how similar events might be designed going forward.
1 Like
Hey Simon! I really appreciate your comments and observations. I completely agree with your vision and the need for more tangible long-term effectiveness. Your analysis coincides with the perceptions we gained from the experience.
The importance of post-event follow-up
As you rightly point out, the enthusiasm and desire to learn did not dissipate at the end of the event. I personally observed that many developers and participants had a genuine interest in learning about the next steps, discovering the available mechanisms, and continuing with the development of their projects. In fact, the main reason the WhatsApp group remained active was the commitment to share more information about building opportunities within the Astar ecosystem.
However, I agree with you that follow-up becomes a challenge without clear guidance or a framework for action. It is precisely at this point that I believe there is a significant opportunity to build a formal roadmap that allows us to nurture those relationships and turn short-term interest into a lasting commitment.
To capitalize on the momentum of future events, I think we could do a strategic approach that goes beyond the hackathon or buildathon itself. Rather than viewing the event as the end point, we would consider it the starting point of a structured incubation process. This could be achieved with a three-phase plan.
The first phase would be the event itself, where the spark of creativity is ignited and initial contacts are established. The second, most crucial phase would be one of intensive follow-up. Here, the WhatsApp group, as in this case, or a similar communication channel, would become a support and resource center, publishing guides, tutorials, and Q&A sessions with Astar experts. The goal would be to proactively address technical questions and motivate teams to continue working on their ideas.
Finally, the third phase would be the incubation and development of promising projects. This would involve offering dedicated mentoring to the most outstanding teams, guiding them in the transition from prototype to functional product. By providing them with the support they need to complete their projects, we could even help them meet the criteria to be eligible for Astar’s dApp Staking, thus ensuring a real and sustainable impact on the ecosystem.
This approach would allow us to avoid losing momentum and build a strong, long-term relationship with developers, transforming a short-term event into a strategic investment in regional talent.
However, I believe that this development requires more comprehensive support from people who are already directly involved in Astar, as they are the ones who know all the details needed to bring the equipment to fruition.
1 Like
Really great outcome. The Buildathon showed a lot of talent in the region and how Astar tech can be put to use. Excited to see the projects that came out of it and the plans to keep building on this momentum.
1 Like
Thank you @EzioRed for your thoughtful reply. I’m really glad to see that we share the same perspective on the importance of post-event follow-up.
I fully agree that the approach you describe could be a constructive way forward. Seeing the event not as the final goal but as the first step in a larger process is, in my view, the right path to ensure that all the efforts and results generated don’t fade away. An approach like this, where the hackathon is only the starting point, is what can create true long-term value for Astar.
Without a doubt.
We will evaluate what else we can do to continue monitoring the situation. I would like to know if it is possible to organize virtual meetings to continue training and disseminating the tools that developers have at their disposal to build on Astar.