Central Protocol V2.0

GUIDELINES

A comprehensive manual for innovation, technical integrity, and competitive discipline.

[01]

Event Overview

VHACK 2.0 is an 24 hours innovative, multi domain based hackathon conducted over two days.

All solutions must be conceptualized, designed, and developed entirely during the official hackathon duration.

Development may begin only after the official kickoff announcement.

Refer to schedule: vhack.online/#schedule

[02]

Mandatory Arrival, Check-In & Presence

2.1 Arrival & Registration

All participants must arrive at the campus by 8:45 AM without fail.
Teams must complete the initial check-in at the registration desk.
Workspace access will be granted only after successful check-in.
Late arrival may affect participation eligibility.

2.2 Mandatory Team Presence

Team must consist of all registered members.
All team members must remain available at the assigned desk/workspace throughout the hackathon.
Members may step out only during officially announced break hours.
During evaluation rounds, all team members must be present.
Absence during evaluation may impact scoring or eligibility.

[03]

Problem Statement & Innovation Policy

Teams are free to choose their own problem statement.
The problem must strictly align with one of the officially declared domains.
Irrespective of domain, the idea must demonstrate clear innovation and originality.

Projects must not be clones of existing products without meaningful differentiation.
Visible added value must be clearly explained if inspired by existing solutions.
Innovation is a primary evaluation parameter.

[04]

Hackathon Structure & Rounds

Day 01 Protocol

Idea Presentation • 10:00 – 10:30 AM

Present initial ideas and form teams. Finalize problem statements.

First Evaluation • 12:30 – 01:00 PM

Initial progress assessment and technical roadmap review.

Elimination Round • 04:00 – 05:00 PM

Second level assessment with team elimination phase.

Progress Check-in • 10:00 – 11:00 PM

Idea suggestions round: Evaluators and mentors will provide guidance and technical feedback.

Day 02 Protocol

Top 10 Selection • 06:00 – 07:00 AM

Picking the strongest projects for the grand pitch.

Final Presentations • 07:30 – 08:30 AM

Final live pitch and judge demonstrations.

[05]

Domain Guidelines & Technical Scope

To maintain technical integrity, projects must genuinely align with the selected domain. Superficial branding will not qualify.

5.1 Agentic AI & Intelligent Automation

Projects must demonstrate structured AI orchestration and intelligent workflow design.

Valid Implementations

• Large Language Models (LLMs) in structured workflows
• Retrieval-Augmented Generation (RAG) systems
• Tool-calling or API execution agents
• Context memory systems / Multi-step reasoning
• Graph-based orchestration frameworks (LangChain, LlamaIndex)

Will Not Qualify

× Simply calling Gemini/OpenAI APIs
× Basic chatbots
× Static prompt-based systems
× Labeling an API key as 'Agentic AI'

5.2 Fintech

Fintech projects must involve financial systems, financial modeling, or transaction-based logic.

Valid Implementations

• Digital payment systems
• Fraud detection / Risk analysis engines
• Credit scoring systems
• Investment analytics platforms
• Financial automation / Transaction architectures

Will Not Qualify

× Generic dashboards labeled as fintech
× Basic CRUD applications
× Static calculators
× Budget trackers without financial modeling logic

5.3 Cybersecurity

Projects must focus on system, network, or data protection.

Valid Implementations

• Intrusion detection systems
• Threat monitoring platforms
• Encryption or cryptographic solutions
• Secure authentication frameworks
• Vulnerability assessment tools

Will Not Qualify

× Basic login forms
× UI-only security dashboards
× Simple password validation systems

5.4 Blockchain / Web3

Meaningful blockchain logic and decentralization are required.

Valid Implementations

• Smart contracts
• Decentralized applications (dApps)
• On-chain/off-chain integrations
• DAO systems / Tokenization platforms

Will Not Qualify

× Centralized apps labeled as Web3
× Storing arbitrary data on blockchain without purpose

5.5 IoT (Internet of Things)

IoT projects must involve real interaction between hardware and software systems.

Valid Implementations

• Sensor-based data systems
• Edge processing architectures
• Real-time device monitoring
• Microcontroller integration (ESP32, Arduino, Pi)
• Hardware-driven automation systems

Will Not Qualify

× Simulated IoT dashboards
× Projects without real device integration

Misaligned projects may be reclassified or deemed ineligible.

[06]

Central Repository Policy

Development must occur strictly within the official forked repository. Development outside the repository will result in disqualification.

6.1 Commit & Contribution Policy

• Frequent and meaningful commits are mandatory.
• Commit history will be reviewed during evaluation.
• Sudden bulk uploads without progressive history will lead to disqualification.

• No outsourced development or external code.
• No copying from other teams.
• No pre-built complete solutions.

[07]

AI & Modern Tool Usage

Use of AI-assisted platforms is encouraged (Antigravity, Windsurf, Cursor, ChatGPT, Claude).

Major tools used must be disclosed in the repository.
Teams must fully understand and explain generated code.
Inability to explain implementation will impact scoring.

[08]

API & Third-Party Service Disclosure

All APIs and paid tools must be declared in the repository. Teams are responsible for managing their own API credits.

[09]

Technical & Infrastructure Requirements

Each team must bring:

LaptopsChargersHardware ComponentsUSB-to-Ethernet Connector

Internet access and workspace provided. Organizers are not responsible for hardware damage, theft, or data loss.

[10]

Evaluation Stability & Conduct

10. Demo Stability

Projects must function during evaluation. Judges are not responsible for technical failures. Demo failure impacts scoring.

12. Code of Conduct

Professional behavior mandatory. Harassment, plagiarism, or misconduct results in immediate disqualification.

[11]

Facilities, Meals & Transport

13. Meal Provisions

Day 1 LunchBring Your Own

Day 1 Snacks & DinnerProvided

Day 2 BreakfastProvided

14. Transportation

Services available from LB NAGAR to campus. Report strictly on time. Organizers not responsible for delays caused by late arrival.

Detailed timings along with contact details will be shared before the hackathon in the official group.

[12]

Venue & Intellectual Property

15. Discipline

Maintain workspace cleanliness. Intentional property damage leads to financial liability.

16. Emergency

Participants responsible for personal health and safety during the event duration.

17. IP Rights

Teams retain ownership. VHACK may showcase projects for promotional/reporting purposes.

VHACK 2.0 PROTOCOL

Central Protocol V2.0

GUIDELINES

A comprehensive manual for innovation, technical integrity, and competitive discipline.

[01]

Event Overview

VHACK 2.0 is an 24 hours innovative, multi domain based hackathon conducted over two days.

All solutions must be conceptualized, designed, and developed entirely during the official hackathon duration.

Development may begin only after the official kickoff announcement.

Refer to schedule: vhack.online/#schedule

[02]