Hackathon Expansion Program Pilot

🌱 ENS Ecosystem
1

Hackathon Expansion Program Pilot

The Ecosystem Working Group is launching a $50,000 Hackathon Expansion Pilot starting November 1, 2025 to broaden ENS participation at in-person hackathons and strengthen relationships with builders worldwide.

Purpose

This pilot tests new ways of scaling ENS presence at hackathons by leveraging the community as a force multiplier. Historically, the Ecosystem Working Group funded hackathons mostly when ENS Labs Developer Relations staff were able to attend. As ENS grows, our participation must grow with it.

The program seeks to:

  • Expand ENS visibility into new regions and communities
  • Increase direct developer contacts and strengthen the builder network
  • Provide hands-on support to teams building on ENS
  • Cultivate long-term contributors and extend global reach

The goal is not just to fund more hackathons, but to create meaningful connections with developers and ensure ENS continues to attract high-quality projects and talent.

Program Requirements

  • Format: Events must be fully in-person (no hybrid).
  • Attendance: Minimum of 50 hackers.
  • ENS Technical Specialists:
    • At least 2 required; the program will fund up to 3 per event.
    • Technical Specialists must be approved by the ENS Labs Developer Relations team, who evaluate ENS knowledge and suitability.
  • Travel Grants: Each Technical Specialist may receive a $1,500 travel grant, paid retroactively after the event once ENS Labs Developer Relations confirms attendance and meaningful participation.
  • Sponsorship: Up to $10,000 per event, excluding travel grants. Sponsorship is not guaranteed and depends on the availability of approved Technical Specialists.
    • For first-time events, typical sponsorship is $3,000: $1,000 for bounties and $2,000 for operations.

How to Apply

Hackathon organizers should contact the Lead Steward of the ENS Ecosystem Working Group via the ENS Forum or Telegram.

  • Applications must be submitted at least 45 days before the event to allow time to secure Technical Specialists.
  • Proposals are reviewed on a rolling basis, with funding decisions based on program requirements and Specialist availability.

Validation

  • The hackathon organizer must submit proof of the hackathon after the event:
    • Photos of the room with hackers
    • List of all project submissions, including participant contact details (Name, Telegram, Email, GitHub, Wallet Address/ENS Name)
    • Bonus: Distribute ENS subnames to each hacker
9 Likes
2

Great Idea.

Feedback:

  1. Can we add what was accomplished from past hackathons? And how much money was given to them in order to have some sense of contrast with the Pilot program?
  2. Does the program includes what happens after and the scope of intent (related to point 4)?
  3. It can be complicated, but how would you measure success from this program and eventually what would be the indicator that can make this move from pilot to a operational program?
  4. The scope that says “ENS participation and strengthen relationship” is too wide and inexact. We have new relationships and partnerships almost every months, as well as Namechain potential, and other related things that can be topic for hackathons, even if the purpose describes what it seeks with that, it is no different from what is currently in place.
3

Is there a public spreadsheet of the previous hackathons run to review efficacy (PII) redacted where possible.

Looking for stats/details on winners, technical leads, participants and attendees.

1 Like
4

Hi, Simon here, Developer Relations Lead at ENS Labs since June.

Generally speaking, the success of a hackathon is hard to measure objectively. It’s a mixture of (1) how many new, high quality developers we have contact with, (2) brand exposure, and (3) what projects are being built, in that order.

Let’s say, there is a hackathon with 50 hackers in a city with good builders who are new to web3, investing $5000 in total in such a hackathon, 100 per hacker, is money well spent in my opinion. There is a high chance that these hackers will start their own projects or get hired and then integrate ENS in these products.

I’ll join the Ecosystem call today and am happy to answer further questions. I’m also working on getting better data about past hackathons. What I can say for now about past engagements in hackathons of ENS: Over the years, we’ve built an impressive database over 2000 hackers, a lot of them now in important positions at big companies/protocols.

8 Likes