
TIP: 24-HOUR NON-STOP BUILD SPRINT AHEAD


TIP: 24-HOUR NON-STOP BUILD SPRINT AHEAD

Official directives, squad eligibility criteria, deliverable benchmarks, and zero-tolerance compliance standards for HACKVERSE '26.
Each squad must comprise 3 to 4 members. Enrolled UG, PG, and Diploma students are eligible. Interdisciplinary roles encouraged.
All squads must submit a functional working prototype / MVP, technical architecture documentation, and a compelling pitch deck.
Participants must NOT contact or message jury members before official results. The jury’s decision is final.
Adherence to the hackathon timeline and format is mandatory. Intellectual property rights of original solutions remain fully with the teams.
A participant can be registered in only one team. Participation in multiple teams is strictly prohibited across all hackathon tracks.
Teams must register with their final members (3 to 4 members). No addition, removal, or substitution of members will be allowed after registration, except when specifically approved in advance by the organizing committee.
All participant, mentor, college, and contact details must be accurate and authentic. False, forged, or misleading information may result in immediate disqualification.
Plagiarism, copying existing projects/solutions, or presenting someone else's work as your own is strictly prohibited. Permitted open-source tools, libraries, APIs, and datasets may be used in accordance with their licenses.
Select your problem statement carefully. Changes to problem statements or themes after final registration will not be permitted without committee clearance.
Duplicate registrations, use of another person's identity/details, or attempts to bypass registration restrictions and team caps are strictly prohibited.
Cheating, impersonation, unauthorized assistance, score manipulation, fraudulent activity, or any other unfair practice is strictly prohibited at all stages of the hackathon.
Any attempt to exploit vulnerabilities, bypass validations, manipulate data, gain unauthorized access, disrupt services, or misuse the hackathon website, APIs, servers, databases, or related systems is strictly prohibited.
Registration does not guarantee final participation. All submitted details may be verified by the organizing committee before participation credentials and slots are confirmed.
Teams must provide valid contact details (email and mobile) and regularly check official hackathon communications, discord announcements, and website bulletins.
Participants must not contact or attempt to contact jury members regarding the hackathon until its official conclusion, including through LinkedIn, email, phone, messaging platforms, or social media. Any communication concerning evaluation, scoring, results, requests, or influence may result in immediate disqualification of the entire team.
Participants must not create or spread false, misleading, defamatory, or unverified information about the hackathon, organizers, jury, teams, evaluation, or results through any channel. Violations may result in disqualification and appropriate disciplinary or legal action.
Participants must not disclose or share any non-public or confidential hackathon information, including internal communications, unpublished results, evaluation details, jury discussions, participant/project data, or credentials. Unauthorized disclosure may result in disqualification.
Teams are expected to maintain the highest levels of professionalism, collaborative spirit, and ethical conduct throughout the 24-hour sprint.
Teams are expected to maintain utmost decorum, respect, and technical conciseness during all evaluations, mentoring reviews, and Q&A interactions with the jury.
The jury's decision regarding project evaluation, scoring, prize distribution, and rank assignment is final and binding on all participating squads.
The organizing committee reserves the right to verify registrations, investigate violations, reject/disqualify teams, and take necessary corrective action to maintain fairness. Its decision regarding eligibility and rule violations shall be absolute and final.
A fully functioning Minimum Viable Product demonstrating core algorithmic logic, features, and UI.
High-impact presentation deck detailing problem scope, solution architecture, market feasibility, and scalability.
Comprehensive technical document covering data flows, API specifications, and deployment topology.
Live prototype demonstration during jury evaluation defending edge-cases and technical architecture.
Plagiarism, submitting pre-built commercial software, or presenting someone else's codebase as your own will lead to immediate squad disqualification.
Directly or indirectly contacting jury members via LinkedIn, email, or social media prior to official results declaration will lead to immediate squad disqualification.
Any penetration testing, API tampering, DDoS attempts, or malicious interference against hackathon servers and contestant submissions is strictly forbidden.
CodeBreakers Club and the Government College of Engineering Kalahandi (GCEK) Hackathon Organizing Committee reserve the right to disqualify any registered team at any stage of the hackathon — including before, during, or after the event — should any discrepancy, misrepresentation, or violation of the hackathon rules and guidelines be identified.
Furthermore, CodeBreakers GCEK and the Institute Organizing Committee reserve the right to cancel, postpone, or call off the hackathon at any point, without being obligated to furnish any reason or explanation for such a decision. In all matters pertaining to the hackathon, the decision of CodeBreakers Club and GCEK Kalahandi shall be final and binding on all registered participants.
Equip your team with an original idea, align with the 24-hour sprint format, and compete for ₹35,000+ in cash prizes.