Summary of Proposal
Ethereum lost over $1 billion to hacks in the first half of 2026 alone, across more than 200 separate incidents. Behind those numbers are organized state-sponsored groups like North Korea’s Lazarus, professionalized scam operations, and infrastructure failures that erode trust in the entire ecosystem. Security is not a niche technical concern, it’s existential to Ethereum’s credibility as a financial system.
The Security Hub will bring together the people best positioned to change this: researchers, auditors, builders, incident responders, investigators, and infrastructure teams, alongside students and newcomers who want to contribute. For four days, the hub will be a working space, not just a place to hear talks, but a place to coordinate on what it will actually take to make Ethereum safer than the banks.
Motivation and Rationale
Ethereum has a strong security community, but its contributors rarely get the chance to gather in one place for more than a talk, panel, or quick meeting. Researchers, auditors, developers, incident responders, investigators, educators, infrastructure teams, and open-source contributors often work on connected problems from different parts of the ecosystem. Devcon gives us a rare opportunity to bring those people together, help them learn from one another, and create new relationships across the security community.
Many builders, students, and Ethereum community members care about security but do not know where to begin. They may not know who to approach, where to find reliable resources, or how their skills could contribute. The Security Hub will give them a clear place to start.
Someone should be able to walk into the hub with a question, meet people who understand the problem, discover a useful resource, join an open discussion, or find a community they can continue learning from after Devcon.
Implementation
The Security Hub will need a flexible and welcoming setup that supports talks, workshops, games, roundtables, office hours, and informal conversations throughout all four days.
To run the hub, we will need:
-
Flexible seating for group sessions and smaller conversations
-
Tables for workshops, games, and interactive activities
-
A screen for presentations, demonstrations, and shared resources
-
A microphone for talks and group discussions
-
Whiteboards or writable boards
-
Reliable Wi-Fi
-
Enough power outlets for attendees and contributors
-
A visible daily schedule
We also plan to use simple materials for security games and interactive activities, along with a community board where attendees can share questions, ideas, resources, and collaboration opportunities.
Programming
The Security Hub will run from 9:00 AM to 6:00 PM across all four days of Devcon. The program will combine talks, workshops, office hours, games, open discussions, and networking.
We want the Ethereum security community to help shape the hub. We already have a proposed core team to coordinate the hub and oversee the program. We will add five volunteers who can help us keep the space running seamlessly throughout the four days. Three people from SEAL have already expressed interest, and we plan to invite TheDAO ETHSecurity Badge holders to join as well.
Anyone interested in volunteering, speaking, hosting an activity, or helping shape the program can comment on this proposal.
We will keep building out the program as Devcon approaches, adding confirmed speakers, sessions, workshops, and activities as contributors join. The outline below is our starting point and will evolve into a more structured daily schedule closer to the event.
Sample Four-Day Program:
Day 1: Meet the Security Community
Welcome, contributor introductions, open discussions, and networking.
Day 2: Security for Builders
Practical workshops, builder questions, tool demonstrations, and security clinics.
Day 3: Incident Response and Coordination
Incident-response exercises, investigations, lessons learned, and community coordination.
Day 4: Getting Involved in Ethereum Security
Contributor pathways, open-source opportunities, community-led sessions, and closing conversations.
The core team will provide the structure and daily coordination, while volunteers and contributors will help keep the hub welcoming, active, and useful throughout Devcon.
Audience
The Security Hub is for everyone who cares about Ethereum security: from the most experienced researchers, auditors, and incident responders in the ecosystem to builders, students, and newcomers who are simply curious about the field.
This is deliberately a dual-track space. On one hand, it’s where some of the sharpest minds in Ethereum security can sit down together and work through what it will actually take to make Ethereum safer than banks - coordination gaps, infrastructure priorities, and hard open problems. On the other, it’s a welcoming entry point for people who don’t yet know where to start, but want to. We think both groups benefit from being in the same room: newcomers get direct access to the people shaping the field, and experienced contributors get fresh energy, new talent, and grounded perspective from the builders and users actually facing these risks. We also want contributors from India to shape the hub, share their perspective, and build lasting connections with the wider Ethereum security community.
Team
The Security Hub will be organized and supported by:
-
Anamarija, Communications Lead at TheDAO Security Fund
-
Griff Green, TheDAO curator
-
Lanski, TheDAO curator
-
Jake, Partnerships Lead at TheDAO Security Fund
-
Cotabe, Business Development at TheDAO Security Fund
-
SEAL contributors
-
ETHSecurity Badge holders
-
Other Ethereum security contributors interested in helping shape the hub
The Security Hub will stay neutral and non-promotional. We want contributors from different teams, projects, and areas of security to take part without any one organization owning the conversation. Sessions should focus on useful knowledge, open discussion, and challenges that matter to the wider Ethereum community.
The current team can support content in English and Spanish. We would also love to involve India-based security contributors who can bring local knowledge, perspectives, and languages into the hub. Anyone interested in helping us shape the space is welcome to reach out or comment on this proposal.