LayerOne
The May 23-24, 2015 LayerOne edition whose official Hardware Hacking Village archive and CharlieX Hackaday.io project document two electronic badges: a PSoC4/ESP8266/WS2812B blinky badge and a VoCore/OpenWRT RT5350F network badge.
Sheraton Gateway LAX, Los Angeles, California · United States · 2015
LayerOne 2015's badge effort produced two electronic badge designs documented by the official Hardware Hacking Village archive and CharlieX's Hackaday.io project: a battery-powered PSoC4, ESP8266, and WS2812B blinky badge plus a VoCore/RT5350F OpenWRT network badge with Wi-Fi and dual Ethernet intent.
Lifecycle
The second badge is documented around a VoCore/RT5350F module running OpenWRT with Wi-Fi, two Ethernet ports, USB host/storage goals, and heatsink work.
The Hackaday.io project describes a battery-powered blinky badge using PSoC4, ESP8266 Wi-Fi, WS2812B LEDs, I/O ports, and 3.3 V logic with LED level-shifting work.
The project details say PSoC routines were back-ported from a PC lightserver and left able to receive patterns or blocks of RGB values over UDP from another Wi-Fi device.
The VoCore notes document OpenWRT buildroot setup, LuCI and USB-storage package choices, sysupgrade flashing, first-login password setup, SSH/telnet access, and opkg package work.
Project details and build logs document two CR123A cells, diode reverse-polarity protection, battery tests, WS2812B failure observations, and boards chainable by VCC, ground, and LED data output.
The building-badges log says kits were made, speaker and staff badges were built, and LED badges were being assembled with a TM-220A pick-and-place shortly before the conference.
Operational history
Readers see the two-source-backed badge designs without treating one board's hardware, firmware, or production state as universal to the other.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The catalogue records the source-backed architecture and build status while avoiding unsupported claims about every final shipped component, firmware image, quantity, or attendee role.