HackaTRON S3 community topics - $5K in prizes!

I am glad to be able to answer this and contribute to the community.

As I have found the Hackathon S3 has come a long way since the S1 was started and kudos to the team for that.

My suggestion is as follows.

Suggestion 1- Have a greater breakdown of the prizes. Allowing more members to win.

Reason I- Having only large prizes acts as an entry barrier for budding developers. These budding developers if exposed to TRON Community can stick around and build something that is native to TRON.

Reason II- Small prizes can attract more builders expecting that their chance to be rewarded at the end of two months is higher and it will mentally prepare them of being compensated for the time and effort.

Suggestion 2- Run quizzes around TRON & coding challenges during a specific period of the Hackathon.

For example, October 1st to 31st during S3. Prizes could be $200 for first 20, $100 for 21-100 & $50 for the next 500.(just an example, pick any number)

Reason I- Who doesn’t like to see them on the leaderboard and the one which keeps changing daily? This will make Forum the most happening place during the Hackathon and more members will be involved.

Reason II- More members will learn about the TRON, and refer to their documents & many among these will stay with the community longer because of the green cause by TRON blockchain.

Suggestion 3- Allow two verticals for the broader prize. One category for projects built before the Hackathon & submitted elsewhere & another category for projects built only during the Hackathon.

Reason I- This will attract true builders to the community. It is very scary to compete with teams that are dedicatedly building year around for TRON. This discourages new builders or those who will be assessed only based on work done during the specified period.

Suggestion 4- Provide differential weightage to the votes.

Reason I- It is very easy to rig the voting process and I have seen many messages being exchanged for vote exchanging.

Reason II- Members with badges of Level 2 & higher have spent more time in the forum and their vote shall be considered equivalent to 5 votes received from Level 1 badge.

For example,

Level 1 badge(basic) - 1 weight Just like mine

Level 2 badge(member) - 5 weight

Level 3 badge(regular) - 10 weight

Level 4 badge(leader) - 15 weight

Happy to discourse around the suggestions.

9 Likes

Just an opinion, dont you think vote weightage will give an undue advantage to projects that have been building all year round for tron. Some projects were here in the season 1, they came back in season two, and the team are back again in season three, because they have spent alot of time on the platform most of them have trust level two. And some of them too has as many as 20 team members.

So in effect, these 20 people in ur example will represent 100 votes. In as much as we want to do away with vote exchange and rigging, giving weight to trust level will do more harm than good to the forum.

Some projects will not present anything better, but because their team members have higher trust levels, they will win regardless.

What do you think?

4 Likes

So 5 is just an indicative number, it can be 2 as well.
It can be decided based on the total members available on the platform.

Right now, I see a storm of badge 1 members coming into the forum and most of them are here to vote for the pre-decided project.

Also, I suppose only 40 badges are issued for members and I hope these are genuine TRON contributors so they can be given some advantage.

If they have launched a product on TRON, they will have incentive to see the ecosystem grow.

3 Likes

Ur points are very much valid. I know most people are coming in from all angles with a premeditated agenda to vote for a particular project.

How do we curb this? A very tough question! Every approach has its pros and cons.

We will have to device another means that will be fair to all parties involved. I will sleep over it, and maybe the forces will bring solutions​:rofl::rofl::rofl:

3 Likes

It’s not great to see S2 Devpost winners of big grants still in testnet at this point, while other projects with community prizes were finished and ready for the users before the hackathon period ended.

Anyway, it’s good that you try to keep an eye on them and push them forward.

2 Likes

Same thought.
For example USTX with the T-Boost project for season 3 is already on the main network.
Well done, good job.

2 Likes

@TronLive One thing I feel may need to be looked into is repeat projects constantly entering the hackathon? especially if each time is to show a new project? if they have received rewards they should show work on previous project before entering a new one.

Also a limit on times you can enter the same project and say its been updated as the funds from the first reward are obviously to update the project so that does not grant another hackathon?

4 Likes

That’s a good point.

It will keep the competition fair.

2 Likes

even worse when they submit same project with very very small modification.

2 Likes

I’m not sure how voting works here; I’d appreciate it if someone could share a guide / forum post to help me understand the current voting procedure.

Because I received several messages from other forum users attempting to exchange votes, this is what I would like to suggest in terms of voting system.

I believe a simple solution would be to give every real forum user (who are not bots/fake accounts) 3-5 votes, allowing them to vote in up to 5 hackathons. This will prevent them from voting on only one project, and they will vote on many initiatives.
Bot/fake accounts should be removed/filtered at least a day/hour before voting starts.

  • Any account with fewer than 60 minutes of read time.
  • Any account that has not visited the forum for atleast 2-3 days ( Not allowing recently reacted account to vote )
  • Any account with less than 20-40 topics visited ( Which clearly states if the forum user is looking through multiple topics, and is really interested in hackathon )
  • A minimum number of likes given and received ( Likes received is important, and other members should only like their comment if the comment has some value, not just a random word )

This filtering should prevent bogus accounts, and enabling multiple votes (one post one vote) on up to five entries may assist in identifying the top projects this season.

3 Likes

I’m new here, will check out hackathon S2 projects & answer the questions.

1 Like

The hackathon team is currently reviewing new users who might be bots, fake accounts and you are welcome to flag if you find any weird account.

Every voters will have 5 votes per track if it didn’t change. And we will have enough time to vote (see judging/voting period schedule).

After the vote, the Hackathon team will take the time to verify if there is any irregularities and remove fraudulent votes.

7 Likes

The voters can vote up to 5 projects per track. That means they still can chose to vote for only 1 project if they want to.

To be able to vote, users need to reach the trust level 1 (basic badge).

4 Likes

Hahahah thats a real pain. When you win reward, u have to prove that you have really used to perform something substantial, u just dont go and do small polish and bring it back as upgrade.

2 Likes

This is an actual message sent by someone under a particular project. People will do anything to get basic user for the purpose of premeditated voting.

getting a university education recruiter related knowledge and everything make you financially stable this project and you’re going to do well trust me it is very good project and the one that make you very much money have to continue reading this article to get too many many many many of love uses diapers that process that is yet and know that I will help us with this project investors must have for you or we all appreciate every day we have in this community we appreciate you all we really love you all thank you

2 Likes

Yeah not the first suspicious message from the same user.

2 Likes

Support this initiative :100:

2 Likes

Maybe they should make it harder to get to “basic user” the closer we get to the vote? Now my impression is that you get “basic user” after 1-2h reading time together with some likes and comments, but maybe they should bump it up the closer we get? So that you need maybe 3-4 hours of reading

3 Likes

It appears like they were too busy sending out vote notifications to anybody to even read our messages.

4 Likes

Lol :joy: I am sure @admin.hackathon @TronLive are taking a note of it :smile:

1 Like