Car Hacking Village
Official publisher of the DEF CON 34 event and social announcements, and owner of the public `chv_badgetools` repository.
SourceCar Hacking Village at DEF CON 34 · United States · 2026
RP2040 CAN/CAN FD vehicle-network CTF badge, with post-event fulfillment unverified
Car Hacking Village publicly announced its DEF CON 34 CTF badge. Official Village posts identify an RP2040, DB9 CAN 2.0/CAN FD support, interactive power management, and a 12 V 1.5 A power supply; the public `chv_badgetools` repository identifies itself as host-side CAN utilities for the DEF CON 34 badge. The scheduled August 6-9 Las Vegas event window has elapsed, but reviewed post-date sources still do not prove final badge manufacture, allocation, handoff, CTF operation, or a released final firmware.
People
Official publisher of the DEF CON 34 event and social announcements, and owner of the public `chv_badgetools` repository.
SourceIt extends the Car Hacking Village lineage with a CTF hardware platform whose public host tooling makes its CAN workflow concrete. The entry separates explicit engineering and announced on-site CTF claims from unverified details about final board design, firmware, quantities, variants, recipient scope, delivery, and event outcomes.
An official Car Hacking Village announcement lists DB9 CAN 2.0/CAN FD support, interactive power management, a 12 V 1.5 A power supply, and an RP2040. The public tooling README says the badge connects over USB, its detection path uses an RP2040 USB vendor ID, and it supports CAN FD frames up to 64-byte payloads with a default 500 kbit/s CAN bitrate. The reviewed sources do not identify the RP2040 board variant, CAN transceiver part(s), physical bus count, USB bridge details, battery/power-source arrangement, LED/display/input hardware, PCB layout, schematic, BOM, Gerbers, production run, or final physical variants.
The public `chv_badgetools` repository provides Python 3.8+ host tools: `chv-candump`, `chv-cansend`, automatic port discovery, and a `python-can` interface plugin for macOS and Linux. It documents USB serial paths, CAN/CAN FD monitoring and transmission, and `python-can` integrations. It is host-side tooling, not a full released badge-firmware or hardware-design archive, so this record does not claim final firmware, source completeness, flashing instructions, or a license for the badge itself.
Car Hacking Village's official CTF announcement says all DEF CON 34 challenges would be on-premise with no remote component. It says tools would be available through Ethernet/USB or by purchasing the CHV main badge, and that five CHV badges would be available for CTF participants, so purchase was not stated as necessary to compete. These announced logistics are not proof of final badge delivery, a universal attendee issue, CTF execution, or final rules.
Lifecycle
The pre-event CTF announcement says all challenges would be on-premise, purchase would not be necessary to compete, and five CHV badges would be available specifically to CTF participants. The scheduled event dates have elapsed, but final allocation and CTF operation remain unreported.
Source`chv_badgetools` provides `chv-candump`, `chv-cansend`, automatic USB-port discovery, and a `python-can` interface plugin for the DEF CON 34 CTF badge.
SourceThe official badge announcement lists interactive power management and a 12 V 1.5 A power supply, without documenting the underlying design, safety limits, or supported external equipment.
SourceCar Hacking Village's official badge announcement lists DB9 CAN 2.0/CAN FD support for the DEF CON 34 badge.
SourceOperational history
The catalogue does not infer universal distribution, a guaranteed participant badge, a completed CTF, or a final allocation count from the announced CTF access route.
The record retains documented engineering surfaces while withholding a complete implementation claim until Car Hacking Village publishes a final technical archive.
The United States record remains source-backed and image-free rather than copying event-site artwork, LinkedIn images, repository previews, screenshots, placeholders, or generated approximations.
The catalogue preserves a documented hardware project and host tooling without converting a lapsed schedule into a fulfilled-badge, completed-CTF, or delivery claim.