When Should the fundamentals of Hackathon Projects Be Done?

Hey everyone I just wanted to share a quick concern, and I’m not sure if it’s just me who feels this way.

I’ve participated in several hackathons in the past, and I might have misunderstood something in Hackathon 6.

After reviewing many of the submitted projects, I’ve noticed that about 60-70% have a completion date set for three weeks from now. Which by checkingDevpost rules, this is after the winners and rewards have already been announced.

And my concern is that maybe I misread the rules. I hope that for the next TronDAO Hackathon 7 or future, it will be explicitly stated that if a product isn’t usable, meaning the fundamentals aren’t ready, it shouldn’t be submitted :heavy_multiplication_x:.

Let me give an example, a DEX > (Decentralized Exchange) should allow token trading (buying, selling, or adding liquidity) as its fundamental functionality. If someone submits a DEX to the hackathon, these features should be ready to be used and tested. And additional features, like farming, can come later.

If I misunderstood the hackathon and it’s acceptable to submit only ideas rather than fully functional products{ if not full but at least a useable product} , then I feel that defeats the purpose of a hackathon.

Anyways this is my concern and if am wrong or getting this twisted, :disappointed: but just thoughts

7 Likes

A project must be fully functional on main net by June 28th for hackaTRONs6. If the product is not usable it will not be rewarded. If only a idea is submitted during the submission period and they fail to update the project in pre-selection round they will not qualify for the judging and community voting round.

5 Likes

4 Likes

What do you mean “If only a idea is submitted during the submission period and they fail to update the project in pre-selection round they will not qualify for the judging and community voting round.” - you mean project code or update what?

How I have understood it is that after Submission period (7th of May) its code freeze. And the only thing left to do is deploy on mainnet if you are one of the winners.

From the rules: “Milestone 2 completion means that a Milestone 1 winner’s Project is successfully on Mainnet.”

Nowhere does it say that the project should be updated during pre-selection period.

1 Like

Yes I mean by pre-selection period the project which is being submitted for the hackathon must be updated in the correct manner mentioned in the hackaTRON rules. Participants can and should update the projects with further enhancements during and beyond hackaTRON period.

BTW @Rink3y this topic should be in TRON Discussion not TRON Hackathon HackaTRON category is for project submissions and posts by admins generally.

I do not really know too much but I am reading through the commentary for well understanding

For May 7 you need a MVP on testnet. For June 28 you need to deploy on mainnet. But between those dates you can keep improving/updating your project.

5 Likes

Thats not how hackathons typically work. Where is this said in the rules?

Let me answer with that question:
Where is it said in the rules that after May 7 you can’t keep improving your project?

Projects are encouraged to keep updating the community. Which means that they should have updates to present. Anyways I’ve been here since season 1 and it has always been encouraged to perfect the product and keep building.
I don’t know how other hackathons usually work, but this is Tron Hackathon. And this is how it works.

3 Likes

What is the point of the deadline then?

It is actually laid out clearly in the rules:

“ Draft Submissions

Prior to the end of the Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the Project in your Devpost portfolio.

Modifications

After the Submission Period. The Sponsor and Devpost may permit you to modify part of your Submission after the Submission Period for the purpose of adding, removing or replacing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Sponsor and Devpost permits.”

Any project that has made changes should be disqualified imo. The rules are for everyone to follow, no?

It is clearly mentioned in the rules that

I think you are not understanding that whatever project you are submitting for hackaTRON can have updates during and after hackathon. In example JustMoney team has submitted a TRON based explorer this season. They can still update the quality of their product with more advanced features.

Nobody is expecting new participants to know what was said and done in previous seasons.

I will say this is not even a typical hackathon is it? Where do we have such big prizes for developers and community?

The purpose of this event is to have as many working projects on TRON/BTTC.

This explicitly states that you cannot add features after submission period. Yes you can update your documentation or explain features or add screenshots or diagrams but not make changes or add features to the actual code.

You can add features. But it should not affect the originally submitted project. The rules do not say that you cannot add features. If you make progress you must update your submission simple.

1 Like

C’mon you are making stuff up. A feature is a change or alteration. All features are integrated in the same product. To use any one feature you must add a button or change logic of that existing application.

Which, according to the rules is not allowed. Which means the project should be disqualified.

How I am making stuff up? I think you do not understand where it states

Updates which do not alter the original submission are fine.

If you make any progress it is advisable you update under your submission.

Right, I think we’re mixing words here. What the rules state is that its fine to change the “description” of the project in Devpost and its fine to update the “forum post” in Tron forum, but it is not allowed to change the “code” of the project that you submitted.

If you want to change the “code”, like adding features you must ask for permission from TRON and Devpost. As per the rules:
" The modified Submission must remain substantively the same as the original Submission with the only modification being what the Sponsor and Devpost permits."

This is what I have been saying

1 Like

Hi, I think you are misinterpreting this rule:

Prior to the end of the Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the submission materials to the Hackathon for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission , but you may continue to update the Project in your Devpost portfolio.

That refers to the project description in Devpost. After deadline you can only post updates, but not change anything in the published description, but it has nothing to do with the code or the functionality.

By May 7th a functioning demo (MVP) should be provided, so that users and judges can evaluate the projects, but work can proceed till June 28th.

4 Likes

No you are wrong, it is the opposite. You can update the project on Devpost (change any part of description or add screenshots). I just checked and its true - I am free to change any part of it right now.

Also it is written very clearly in the hackathon rules. You are not allowed to change the application (submission) “but you may continue to update the Project in your Devpost portfolio”

Rules:

Once the Submission Period has ended, you may not make any changes or alterations to your Submission , but you may continue to update the Project in your Devpost portfolio.