Technology · Chapter 03

Blockchain Hackathon

Build decentralized solutions that work on-chain.

Techverse Blockchain Hackathon invites participants to build practical, transparent, and secure decentralized solutions. Teams apply blockchain technologies, smart contracts, and decentralized application (dApp) development to solve real-world challenges, demonstrate technical skills, and present their work to judges.
Winner
PKR 20,000
Entry
PKR 1,500 per team
Fee
PKR 1,500 per team
Team size
2 to 4 members
Duration
Proposed 48 hours
Eligibility
Students, developers, designers, blockchain enthusiasts
Cross-institutional teams
Permitted
Networks
Local chains or approved public testnets

Problem statement

The official theme and problem statement(s) will be announced at the start of the hackathon. Teams must design and build an original solution within the official 48-hour period. Suggested challenge areas include supply-chain traceability, digital identity and verifiable credentials, transparent donations, document verification, decentralized governance, and secure asset tracking. These are examples, not pre-announced competition themes.

Prizes

What's on the line.

  • Winner

    PKR 20,000

    • Runner-up

      PKR 10,000

Participation certificates and special awards: certificates and shields.

Judging

How you are scored.

Know the rubric before you build. Judges score against these criteria.

  • Innovation & real-world relevance

    25%

  • Blockchain implementation & technical execution

    30%

  • Security, reliability & responsible design

    20%

  • Feasibility, usability & impact

    15%

  • Presentation, documentation & demonstration

    10%

01

Important guidelines

  • Duration: proposed 48 hours; exact start and end times will be published by organizers.
  • Teams must develop their original competition-specific solution during the event. Existing frameworks, libraries, starter templates, and SDKs are allowed with attribution; prebuilt complete projects are not.
  • A functioning blockchain component is required. A blockchain-themed presentation or conventional web app alone is insufficient.
  • Use local development chains or approved public testnets. Real-money transactions and mainnet deployments are not required and should not be used for judging.
  • Judges: industry and academic professionals, subject to organizer confirmation.
02

Hackathon rules

  • Team participation: each person may join only one team. Teams must follow organizer check-in and identification procedures.
  • Original work: the core solution, smart contracts, and integration work must be created during the hackathon. Declare reused code, open-source packages, templates, and external APIs.
  • Blockchain technology: Ethereum-compatible chains (Solidity), Solana (Rust/Anchor), or other public blockchain ecosystems are permitted if the team can demonstrate genuine on-chain functionality.
  • Safety and security: use test tokens only. Never submit seed phrases or private keys. Do not exploit live networks, attack other teams, or use unauthorized third-party systems.
  • Responsible AI assistance: AI coding tools may be used, but teams must disclose meaningful use and explain, understand, and defend their code.
  • Fair play: plagiarism, fabricated demos, copied finished projects, deliberate disruption, and harassment may result in disqualification.
  • Deadline: all repositories and required materials must be submitted before the official cutoff. Late submissions may be rejected.
  • Organizer instructions: participants must follow venue safety, conduct, and competition announcements.
03

Project submission requirements

  • Source-code repository link (GitHub/GitLab), with README and setup instructions.
  • Smart contract source code, relevant deployment scripts, and network details.
  • Deployed contract address(es) on an approved testnet, or reproducible local-chain instructions.
  • Working demo or prototype showing a real on-chain transaction or state change.
  • 2–3-minute demonstration video and a short project description.
  • Brief documentation: problem, proposed solution, architecture, blockchain justification, security considerations, limitations, and team contributions.
  • Live pitch and Q&A with judges; final time allocation will be announced.
04

How judges assess

  • Judges will assess whether blockchain is meaningfully necessary, whether the prototype works, and whether claims can be verified.
  • Team collaboration may be considered within the presentation and execution assessment.
06

Use of AI and third-party services

  • AI tools, documentation, APIs, and open-source dependencies are allowed with appropriate attribution.
  • Teams must explain which parts were generated, adapted, or written by members.
  • Externally hosted services may be used, but the essential blockchain workflow must remain demonstrable.
07

Dispute resolution

  • Report rule concerns or appeals to the organizing committee promptly.
  • The committee may investigate originality, safety, eligibility, and submission compliance.
  • Final scoring and ranking decisions rest with the appointed judging panel, subject to published event procedures.
08

Preparation checklist

  • Required: laptop, charger, valid identification, and reliable access to project accounts.
  • Required: development environment, Git, wallet software, and relevant SDKs installed in advance.
  • Required: testnet wallet funded with faucet tokens (never real funds); keep recovery phrases private.
  • Recommended: IDE such as VS Code; local blockchain tooling; browser and API testing tools.
  • Recommended: backup connection or offline documentation where feasible.
  • Recommended: extension cord (subject to venue policy), headphones, notebook, and water bottle.

Contact & support

Build responsibly.

For event announcements, technical clarifications, or participant support, contact the module lead.

Good luck, and build responsibly!

Module lead