📅 Dates
Milestone Date & Time
Hackathon Start Today — December 5, 2025
Team Formation Opens December 5, 2025
Submission Deadline December 21, 2025 at 11:59 PM PT (California time)
Judging Period December 22–24, 2025
Winners Announced December 26, 2025
🧑‍💻 Eligibility
  • Open to: In-person participants located in Ukraine (or with team members attending the in-person event)

  • Team Size: 1–5 participants

  • Project Requirements: Must be submitted on Devpost and demonstrated live at the venue

  • Age: 13+, or with guardian permission if under 18

  • Crypto-Compliance: No need to hold tokens to participate. Token functionality should be testnet or simulated unless on GitBanks.

📦 Project & Submission Requirements

Your submission must include:

  • A working prototype of one or more of the following:

    • Embeddable widget (e.g., for a word like Spring constant from ety.ai)

    • Telegram Mini App connected to ety.ai

    • Token migration script from Polygon to GitBanks EVM

  • A brief README or Devpost description explaining:

    • The goal of your hack

    • What tools/libraries you used

    • How to test/interact with it

  • GitHub link (or zipped project files)

  • (Optional) Short demo video (1–3 min)

🏆 Prizes
Prize Tier Reward
🥇 Best Overall Hack $400 USD equivalent (Crypto or USD)
🥈 Best Mini App $250 USD equivalent
🥉 Best Embed Widget $150 USD equivalent
🌱 Community Award $100 — voted by in-person attendees
💡 Most Original Idea ety.ai token NFT + featured listing
🧠 Judging Criteria & Winner Selection

Submissions will be judged by a mix of organizers, community advisors, and technical experts using the following criteria:

1. Technical Achievement (30%)
  • How well does it work?

  • Any clever or difficult implementation details?

2. Creativity & Originality (25%)
  • Is the idea new or insightful?

  • Does it use language, identity, or AI in unexpected ways?

3. Utility & Impact (25%)
  • Could this grow into a useful tool?

  • Is it shareable, scalable, or helpful to the wider community?

4. Presentation (20%)
  • Is the Devpost writeup clear?

  • Does the demo explain what’s going on?