HackaTRON S3 community topics - $5K in prizes!

I know now that what you thought was almost a sure thing was really far from that.

I will rest my case here, and really hope the @admin.hackathon will take every point made here into account to deliver a better verdict.

If you are awarded, congratulations :tada:

1 Like

Hola, considero que tanto la comunidad como dev post, son dos partes importantes en este proyecto, en el momento que un concursante desea ignorar una de las partes, debería ser eliminado.
Todo es un conjunto en el cual nos apoyamos todos, la comunidad también es necesaria para saber que se está construyendo en la red, sin su apoyo la parte contraria tampoco se expande y sin ella no hay comunidad.

Creo que todos hacemos una labor, lo mejor posible y sobre nuestras capacidades, las cuales día a día van acrecentandose.

3 Likes

Hola, pero cuando se presenta un proyecto sea para desarrolladores o parar que lo conzca la comunidad y ella también tenga voto, no se puede pretender desacreditar la labor de nadie.

Si pretende crear para desarrolladores hay temas en dev post para ello.

Ser un poco mas humilde no cuesta nada y no es infravalorarte, detrás de cada miembro de la comunidad existe una experiencia en este tema¡, entonces no se puede tratar con menosprecio a nadie, todo el mundo es valido.

3 Likes

Greetings @TronLive @admin.hackathon :wave:!

Wrt the question of ‘significant updates’ I guess if we mention a checklist it would help qualification decision making more easier and objective for the Judges/Admins.

Some pointers for the checklist could be:

  • Link of working product created in previous season ( deployed on mainnet).
  • Quantification of users onboarded from previous season.
  • Regular Updates on forum about progress in previous season.
  • As stated by @fabsltsa @Sirluke too the new product should stand as a standalone product/module by itself.
  • The upgrade should have the capability to onboard new users on its own features.
  • The new upgrade should be deployed on mainnet.
  • Cosmetic, UI, Rebranding etc changes to be disqualified.
  • Copy/Paste of codes from other chains to be discouraged

Another check which can be useful in subsequent Hackathon would be to identify ‘Hackathon Hoppers’ … devs who use similar products and apply in various hackathons ( their Goal is to win rewards rather than contribute in evolving the ecosystem… hence this category of people needs to be discouraged from upcoming seasons)

6 Likes

Thank you to everyone that posted your opinions and findings in this thread so far. Rest assured that we are working really hard to look into all voters to ensure that we have taken out suspicious votes and added penalties to the final calculation. We are striving to get the community poll as fair as possible, and we thank you all for helping. We are Tronics, don’t give up, keep building, and we will keep growing!

9 Likes

Kudos to your dedication and tremendous hard work ! You and the team rock :love_you_gesture:t2:

1 Like

Wow that is wonderful, i just cant wait for the 16th of December. The results will bring joy to some people and also serve as a shocking news to others.

Can’t wait to read all the grievances of those who might feel cheated and those who will say bad things about this s3 because things didn’t go in their favour.

The drama will be intense this season and the thought of it alone makes me laugh :joy:

1 Like

Yeah.

There will be many expressing their dissatisfaction.

But i think they shall be informed privately about votes that are eliminated from their project and penalties.
Hopefully, this will create less dissatisfaction.

1 Like

Yh that is very true. :sunglasses::+1:

1 Like

How does “penalizing” work though? As @nickmura pointed out in the hackathon vote thread, it’s possible (and even probable) that the bot accounts voted on random projects aswell. Only removing votes seem more reasonable to me because of this.

2 Likes

Normally fraudulent votes are removed as they are found directly on the voting page. So everybody can see the exact amount of legit votes and the final result. Otherwise some might think there is something shady and extra votes have been removed for some contestants.
Transparency = no dispute.

3 Likes

Yeah.

Will the project owner who got 50 votes earlier and now is reduced to 40, know why it happened with them?

Because there will be cases where project owner had no relation with fraudulent voters but may feel that their votes were removed to support other projects.

2 Likes

No idea. I think last season only one project lost some ranks after the cleaning. Was 1st before the fraudulent votes got removed, ended at that #3 of DeFi if my memory is good. The rest of the rankings didn’t move.

1 Like

@admin.hackathon ,

As what @wodaken said, those of us who were affected from this botting problem, such as my project, distanced themselves immediately from this unfortunate event, trxmini.games is not responsible in any way for this malicious event occurring. Under no circumstances, did we wish to influence a unsafe and negative environment for any of the builders, and have encouraged and supported our fellow builders in our category.

trxmini.games and our fellow builders have been at our utmost diligence in participating and contributing positively to the community and ecosystem. Please acknowledge those who have been affected were not responsible for such botting or foul play. Thank you.

3 Likes

Hola, le agradezco la consideración que han tenido con los comentarios de la comunidad, se que es un trabajo duro para ustedes, pero es conveniente que se construya sobre unas bases de honestidad, transparencia y que el esfuerzo, los buenos proyectos sean ganadores por merecimiento propio.

No there was more than one category affected in the previous Hackathon. Our AfricaStars project ended one position higher after the judges cleared the fraudulent votes.

I agree on the worry about penalties if I remember correctly I saw two projects reaching out doubting the sudden boost in votes they received. Would be a shame if they got punished for votes added by someone else or by bots.

5 Likes

In everything i think there are exceptions. Those that distanced themselves from all these votes that they saw were coming from nowhere should be treated as exception.

But those who made no effort to distant themselves because it was going in their favour should as be penalized.

1 Like

It is a very delicate matter because the trace cannot be found on where the bots came from.

Penalizing any project shall be made based on some interaction with the project owner.

The organizing team should ask them a set of questions before concluding that they are responsible for bots and must be penalized.

It is good that some projects openly said that they are receiving bot votes, but then for a team of 1-2 members it is very easy to not see the pattern. So, these teams might not have realised that they have received bot votes penalizing them without giving an opportunity to answer is not right.

1 Like

Thanks for voicing your concerns. It’s actually quite clear to us the intention of the fraudulent voters and who they are truly “supporting” as there are patterns we can trace. Projects that got randomly targeted won’t be penalized. If a project receives too many suspicious votes and passes a certain threshold, then the project will be disqualified. We want to ensure that the projects are voted by people who truly care about the TRON ecosystem and are part of our real community members, and not someone that was asked to come and spam on the forum just to give out a few votes.

8 Likes

The message clears a lot of questions raised above.

We will be as fair as we could with all the project creators.

2 Likes