UST.

UST d3code Campus Hackathon'22

842 Registered Allowed team size: 2 - 4
842 Registered Allowed team size: 2 - 4

Winners are announced.

CHECK OUT OTHER HACKATHONS
Idea Phase and Team Formation
Online
starts on:
Nov 04, 2022, 12:30 PM UTC (UTC)
ends on:
Nov 20, 2022, 06:29 PM UTC (UTC)
24-Hour Finale
Online
starts on:
Dec 11, 2022, 03:30 AM UTC (UTC)
ends on:
Dec 12, 2022, 04:05 AM UTC (UTC)

Winners

About Top 5 - Finale Teams Top 10 Teams Guidelines Judges Ideation Template FAQs Teams About UST Terms & Conditions Discussion

Guidelines

  1. The programming challenge will be conducted on the official D3CODE hackathon platform
  2. Participating teams will require to complete three challenges with increasing complexity in three hours. A challenge will be presented, and the clock starts. Only when the challenge is completed successfully will the next challenge be presented.
  3. The programming challenge will be of three hours duration. Teams will need to take all three challenges during one continuous block of three hours at the specified date and time.
  4. The Programming Challenge round is also a team round. Teams can be collocated or use conferencing tools to coordinate and communicate. However, only one member of the team will be inputting the code into the system at a time. Different team members can input the code for each challenge.
  5. Proctoring is enabled on the platform and if a team is deemed to be cheating or making use of illegal assistance, they will be disqualified.
  6. The platform will notify the participants if they have successfully completed all three challenges but will not provide their placements right away.
  7. The D3CODE organizing committee will review the results and select the top 10 teams to progress to the next round.
  8. If there are more than 10 teams who successfully complete all three challenges in the three hours, the D3CODE organizing committee will use the following to break any ties.
  9. Total time taken to complete all three programming challenges will be accounted for to break ties.
  10. In the event there are more than 10 teams after application of tie break rule #1, the time taken to complete the third programming challenge will be accounted for.
  11. In the event there are more than 10 teams after application of tie break rule #2, the time taken to complete the second and third programming challenge will be accounted for.
  12. In the event there are more than 10 teams after application of tie break rule #3, code quality of the submitted code for the third programming challenge will be accounted for. The D3CODE technical committee’s opinion and ranking of code quality will be final and not debatable.
  13. The theme is ‘Metaverse’
  14. Your idea needs to be aligned with the theme. Idea can be foundational, something that can be leveraged to build features in the Metaverse, a reusable Metaverse feature, a private metaverse or a product or service to be offered in a metaverse. Ideas based on AI, AR/VR, IoT, Blockchain and Edge Computing are all acceptable if the idea can be leveraged in a Metaverse.
  15. Ideas need to be implementable. You should be able to articulate the technologies, methods and processes that you will deploy to build a fully working prototype of your idea.
  16. During the hackathon round, you will be asked to develop a proof-of-concept of your idea. Given that, you should identify key foundational concepts in your idea. For example, if your idea is to develop a digital currency that leverages a blockchain algorithm, you will need to identify and call out this algorithm in the response questionnaire. You may be asked to develop a working prototype of the algorithm during the hackathon round.
  17. Ideas must be unique or have a unique differentiator. Ask yourself if your idea is patentable? For example, an idea for creating Avatars in the Metaverse is not, but a framework for creating Avatars might be.
  18. Ideas need to be original and your own and should be transferable to UST in the event you are one of the top 5 teams and you accept UST’s offer of employment.
  19. Qualifying teams go through a 60-minute interview with the D3CODE technical committee, over Zoom or MS Teams.
  20. Interviews will be recorded.
  21. All teams will adhere by the D3CODE code of conduct during the video interviews.
  22. Everyone in the team will be asked to introduce themselves followed by a short individual Q&A. Individuals are advised to prepare a short bio of themselves which they can use to introduce themselves.
  23. Idea presentation – The team presents the idea in a D3CODE presentation template. The entire presentation can be anchored by an individual in the team.
  24. The presentation will be followed by a Q&A
  25. Teams are queried on the idea and their presentation.
  26. Panel will address a question to a specific individual in the team, to ensure everyone in the team is an active contributor to the idea.
  27. In addition to questions on the idea, panel will discuss established and currently trending technology subjects.
  28. The intent and objective of the video interview is to establish a rapport with teams, get introduced to individual team members, gather details to better assess the submitted idea, confirm that the team is one of equals to the extent possible.
  29. Each of the teams qualifying for the hackathon round will be provided a problem statement based on their idea. The D3CODE technical committee will review the idea submitted and define the problem statement. The problem statement will be made available to each team at 9:00 AM IST on the 11th of December 2022 at the hackathon venue in the UST campus at Trivandrum, India.
  30. No development will start before the actual date and time of the hackathon round of D3CODE. Any teams that violate this rule will be automatically disqualified. The first line of code should be written on or after Sunday, December 11th, 2022, at 9 am IST.
  31. Any software development tools, game engine, IDE, and/or programming language can be used for the event. UST or the D3CODE organizing committee will not provide or support any software, hardware or tools. Participating teams must bring their own laptops or desktops, software and tools for the event.
  32. Teams can use commercially licensed tools and IDEs to develop code but UST or the D3CODE committee will not be able to support these tools or licenses or be liable for any tools, software or hardware procured illegally. It is the responsibility of each team to ensure they have any required licenses that are legally obtained.
  33. Teams cannot use pre-built commercial components, software or tools as part of their code, that do not offer OEM licensing and such components, software or tools cannot be the core foundational aspect of your idea and solution.
  34. You are permitted to use publicly developed and openly licensed APIs and SDKs for your project.
  35. During the hackathon you can use design and assets that were created prior to D3CODE. All assets should conform to the Creative Commons License agreement standard or are freely available and you have permission or license to use them. Proof of permission must be given upon request.
  36. Assets, SDKs, APIs or other tools or components available under a trial license may be used.
  37. Any intellectual property developed during and within the scope of the hackathon is considered property of UST. This rule does not apply to any intellectual property that was developed prior to the hackathon and is leveraged within the guidelines described.
  38. A team may not code applications that violate the D3CODE code of conduct. For example, racially insensitive ideas for an application will automatically be disqualified.

 

Social Share

Notifications
Mark All as Read
View All Notifications

?