BSidesPDX
The October 14-15, 2016 Portland Security BSides edition at Oregon Convention Center, corroborated by Calagator event metadata for PCB badge giveaway language while official BSidesPDX pages preserve the schedule, speakers, workshops, contests, and hardware-security context. PDX Badgers preserves the public ATTiny85 Eagle board/schematic/BOM/firmware archive.
Oregon Convention Center, Portland, Oregon · United States · 2016
The BSidesPDX 2016 badge is a source-backed Portland Security BSides PCB badge record tied to Calagator's event listing, official BSidesPDX 2016 schedule and speaker pages, and the public PDX Badgers ATTiny85 Eagle board, schematic, BOM, and Arduino firmware archive.
Lifecycle
The firmware imports CapacitiveSensor and defines two capacitive sensors across pins 3/2 and 3/4, with capacitive readings changing the alternate animation resolution.
The BOM lists D1-D35 plus DNOSE as 36 yellow 0603 LEDs, while the schematic preserves the LED array around PWM0 and PWM1 control nets.
The schematic maps J1 to VCC, GND, RST, PWM0, PWM1, CAP0, and CAP1-related nets, preserving a six-pin header trail for programming or badge hacking.
The Calagator listing says Security BSides Portland had PCB badges, T-shirts, and bags to give away, with donors receiving them first.
The BOM lists an ATTINY85-20SUR microcontroller and the Eagle schematic instantiates U1 as a Tiny85-20-SMT device.
The BOM lists a CR2032 battery holder and the Eagle schematic carries BT1 as a CR2032 holder tied into the badge power rails.
Operational history
The event page uses the schedule/Calagator October 14-15 dates and preserves the mismatch as a provenance caveat instead of silently normalizing it.
The catalogue records the source-backed BSidesPDX 2016 PCB badge without claiming that every attendee received one.
The entry remains source-backed and image-free rather than copying event-page images, board files, repository artwork, social photos, screenshots, or generated visuals.
The catalogue cites the repository as evidence but does not republish repository media or treat the design files as reusable image assets.
Hardware and firmware claims remain limited to the public repository files plus event-context wording.