📅 June 13-15, 2025 | 🏆 €30,000 Prize Pool | 🏠 Berlin, Germany
- 🌐 Hackathon Website
- 📋 Hackathon Manifesto
- 📖 Hacker Manual ← RTFM!
The W3PN_Hacks Berlin 2025 has concluded. After evaluation by the judges, the winning projects have been selected. Congratulations to the winning teams!
| Track | Winner | Description |
|---|---|---|
| Advanced Cryptography | canary | Automated deadman switch |
| Applied Encryption | Gnosis VeilPay | Private noncustodial crypto card |
| Censorship Resistance | Aside | Ephemeral peer-to-peer chat |
| Privacy-First AI | Texcoco | AI workbench for Aztec |
| Public Goods | Portal | P2P location-based chat |
| Design (UI/UX) | OpenLavatory | Decentralized wallet connection protocol |
| User Onboarding | MagicENS | Private ENS receiving addresses |
| Project | Description | Team |
|---|---|---|
| ACTivate Groups | Decentralized private group chat | Bálint @bosi95, József @Kexort, András @aranyia |
| Aside 🏅 | Ephemeral peer-to-peer chat | Alisher, Sasha |
| BlindMatch | Private dating via FHE | Raphaël Deknop, Fabian Ferno |
| canary 🏅 | Automated deadman switch | Kieran P, Lina P, Ryan C |
| DeeperTruth | Verifiable video authenticity | Romario Kavin |
| Encrypt it! | Wallet-based encryption standard | Timotheus, six, MarcelJay, James, Mörk |
| Gnosis VeilPay 🏅 | Private noncustodial crypto card | Sebastian, Druv, Mohammed |
| goblow.it | Anonymous Telegram whistleblowing | Coco the dog, Manu, Peter, Paulo |
| HELIX | Private cross-border dividends | Julian Nalenz, Yvanik |
| Hopline | User-friendly decentralized VPN | tolbrino, mjadach, ilge ustun, 1uiz |
| Jedi | Private AI business co-founder | Gabriel Antony Xaviour |
| LiveBlur | Real-time video face blurring | Agustin Schiariti |
| MagicENS 🏅 | Private ENS receiving addresses | zkfriendly, sembrestels, FaezehShakouri |
| Midnight Vote | Anonymous DAO voting platform | Armando Medina |
| OpenLavatory 🏅 | Decentralized wallet connection protocol | luc.eth, v1rtl.eth, Daniel |
| PLottoPGF | Private lottery for PGF | Danish, nodestarQ |
| Portal 🏅 | P2P location-based chat | sunsakis, belakm, yellowBirdy, weboko |
| Preserving Consumer Privacy in 5G | ZK-based 5G link authentication | Dungeon, Applied Engineering |
| Private Stargate Finance | Encrypted cross-chain finance | Ben Hooper |
| PrivateRPC | Private MetaMask RPC middleware | Erik Valle, Artur Vargas |
| PrivacyPal | Local privacy policy tracker | Daniel Silberschmidt, ChatGPT |
| ProofLeak | ZK-verified whistleblowing platform | steelfeel.eth, 0xxdana.eth |
| psuedo-grant-analysis | Private grant funding analysis | Rashmi V Abbigeri |
| ShadowPay | Confidential on-chain payroll | Levan Ilashvili, Guy at the Coffee Stand |
| SNPools | Encrypted genetic data marketplace | Khaled, Bear Mo, Kevo |
| SocialRecovery4Everyone | Biometric-based social recovery | S001.28 (signal handle) |
| Squaredance Captable | Compliant anonymous DAO framework | Artiom, Evgeny, Elena, Vika, Ben |
| StealthGrant | Private quadratic funding platform | Leo Franklin |
| Texcoco 🏅 | AI workbench for Aztec | Kevin Stubbs |
| Zero-Sig | Private multisignature solution | Frank & Drone |
| zkTender | Private AI-powered government tenders | mell |
- Fork this repository
- Create a folder with your project namie:
/projects/your-project-name/ - Copy the submission template (see below)
- Submit via Pull Request (PR) before deadline
What's next?
- Prepare for Project Presentations - get ready to present your project after submissions close
- Share openly - help others and get help
Sunday, June 15, 2025 at 16:00 CEST (countdown)
We encourage everyone to send a Pull Request with Submission earlier than a few minutes before the deadline to allow for fixes and avoid disqualification based on missing information.
⚠️ Important: Keep your project repository/demo public and accessible for at least 14 days after the hackathon ends.
After the submission deadline, all teams must be prepared to present their submitted projects to judges.
More information: 📊 Judging Process @ Hacker Manual
All submissions will be evaluated by expert judges according to the Judging Criteria after the deadline and the project presentations.
Your project folder must include:
README.md(using our template)
Your project folder can include:
- Presentation files (
.odp/.odg/.otppreferred) - Any additional documentation
Choose one/two track(s) for your submission (see detailed descriptions):
- Advanced Cryptography - MPC, TEE, ZK, DID, FHE
- Censorship Resistance - Tor, mixnets, Nostr, mesh networks
- Applied Encryption - Strengthen existing tools
- Privacy-First AI - Secure AI interactions
- Public Goods - Privacy-preserving public infrastructure
- Design (UI/UX) - Better privacy app experiences
- User Onboarding - Improving privacy tech adoption
Copy this template to your project's README.md:
# [Project Name]
- **Track(s):** [Choose one or two from above]
- **Team/Contributors:** [All who contributed - diverse skills welcomed]
- **Repository:** [Link to your code repository]
- **Demo:** [Link to live demo, video, or screenshots]
## Description (TL;DR)
[Brief description of your project]
## Problem
[What problem does this solve?]
## Solution
[How does your project address the problem?]
## Technology Stack
[List technologies, frameworks, libraries used]
## Privacy Impact
[How does this improve privacy?]
## Real-World Use Cases
[Who would use this and how?]
## Business Logic
[Sustainability/monetization considerations]
## What's Next
[Future development plans]- Hard deadline: Sunday, June 15, 2025 at 16:00 CEST
- No late submissions accepted
- Pull requests must be created before deadline
- One project per Pull Request
- Folder naming:
/projects/your-project-name/(no spaces, use hyphens) - Required files: README.md
- Tech-agnostic: Use any programming language, framework, or protocol
- Chain-agnostic: No restrictions on blockchain platforms
- Open source encouraged (but not mandatory)
- Individual or team submissions welcome
- Team size: No limits, consider collaboration over competition
- Cross-team collaboration encouraged
- One submission per team/individual
- Original work: Created during the hackathon (June 13-15)
- Track selection: Choose one or two tracks for judging
- Complete template: All sections must be filled
- Working links: Repository and demo links must be accessible
- Privacy focus: Must address privacy improvements
- Repository persistence: Keep your project repository/demo public and accessible for at least 14 days after the hackathon
- Pre-existing projects (unless significantly extended during hackathon)
- Plagiarism or copying existing solutions
- Incomplete submissions missing required components
- Commercial promotions without technical innovation
No GitHub account? Technical issues? Question?
Contact our submissions coordinator Tree via Signal for assistance.
Good luck and happy hacking! 🔥
Read the Hacker Manual for complete event details.
"Cypherpunks write code. We publish our code so that our fellow Cypherpunks may practice and play with it." - Eric Hughes