DEF CON 34 · United States · 2026

IFLFU SAO (DEF CON 34)

Independent PFC161 two-LED message SAO update announced for DEF CON 34

BigFuckingBadge's public DEF CON 34 Badgelife response calls IFLFU SAO an update to an existing SAO, lists it at $20, and says it illuminates the words "I FUCKING LOVE FUCKING YOU" with the two "FUCKING" illuminations randomized. The same maker's live DEF CON 34 page has an unlabeled $20 OffensiveSAO card about a simple rectangle that sends a message at random; the roster supplies the direct IFLFU name/repository mapping. Hexum064's public `iflfu-v2-pfc161` C source includes PFC161 headers and drives two active-low LED outputs, each with an LFSR-based timing state, while the public hardware repository carries KiCad front/back boards and schematics, BOM/position files, Gerbers, and SAO-spacer models. These sources establish a real planned independent electronic SAO update associated with DEF CON 34—not official conference issuance, admission, a fully recovered earlier lineage, completed fulfillment, final production parity, safe/electrically characterized hardware, a source-license grant, or a rights-cleared image.

EventDEF CON 34
SeriesDEF CON
LocationLVCC West Hall, Las Vegas, Nevada
CountryUnited States

People

Authors & Credits

public IFLFU firmware and hardware repository publisher

Hexum064

The IFLFU Badgelife response links the public `Hexum064/iflfu-v2-pfc161` and `Hexum064/iflfu-hardware` repositories. This credit records visible repository-publisher context only, not sole authorship, final production responsibility, message/artwork rights, DEF CON issuance, completed distribution, or image-reuse authority.

Source

public IFLFU seller-page publisher and Badgelife roster submitter context

BigFuckingBadge

BigFuckingBadge publishes the cited DEF CON 34 badges/SAOs page, and the public Badgelife response names BigFuckingBadge / Hexum064 for IFLFU. This credit records visible seller/submission context only, not sole design, manufacture, message/artwork rights, DEF CON organizer status, completed fulfillment, or image-reuse authority.

Source

Why It Mattered

IFLFU is a useful example of an explicit current update whose public roster supplies the artifact name and visible behavior while its code exposes a small but concrete randomized-light implementation. The dossier retains the distinction between an advertised, source-backed message SAO update and a complete historical lineage, final manufactured unit, official event credential, or reusable media package.

Hardware

The public `iflfu-hardware` repository contains a PFC161 datasheet, KiCad PCB/schematic/project files for full and front boards, BOM/position material, front/back/prototype Gerbers, and multiple SAO-spacer model files. The public C source targets PFC161 headers and declares two LED outputs on PA4 and PA5 using active-low current sinking. These files do not identify the final shipped board population, PFC161 package/marking, LED type/color/optics, exact lettering/illumination construction, resistor values, SAO connector version/pinout, host requirements, input voltage/current limits, power source, battery/charging path, protection, dimensions, materials, assembly/test results, safety instructions, compliance, or compatibility with any specific badge host.

Software & Apps

The public `iflfu-v2-pfc161` repository contains a Makefile, Easy PDK material, and a 173-line C implementation. The code disables the watchdog, selects an internal high-frequency clock divider, configures PA4/PA5 as active-low LED sinks, keeps independent per-LED LFSR state, derives subsequent delays from each LFSR, and performs a short flash when an LED transitions on. That supports a source-level randomized two-channel-light behavior, but it does not establish the exact final illuminated words, random-distribution characteristics, source flashing workflow, toolchain versions, final binary, release/version mapping, signed updates, recovery path, security review, accessibility, support, warranty, or an explicit LICENSE/COPYING grant.

Lore

The public roster spells the artifact IFLFU SAO, calls it an update to an existing SAO, gives a $20 price, and describes the explicit phrase and random illuminated-word behavior. BigFuckingBadge's current page separately describes an unlabeled $20 OffensiveSAO as its original/first SAO and a simple rectangle that sends a romantic-and-raunchy message at random. This record uses the roster for the exact mapping and preserves the seller's presentation without asserting which older edition the update replaces, who authored the message/artwork, any recipient consent, content-rating suitability, or authorization, affiliation, or endorsement from DEF CON or another person/organization.

Lifecycle

Add-ons & Upgrades

hardware design archive public source tree; production parity and license unconfirmed

Public KiCad, BOM, position, and Gerber trail

The hardware repository visibly contains KiCad board/schematic/project material, BOM/position data, front/back/prototype Gerbers, backup files, and a PFC161 datasheet. The published tree is traceability evidence, but this pass did not reconcile it to a final populated unit, fabrication order, component sourcing, test procedure, connector/power design, or explicit license.

Compatibility: IFLFU SAO (DEF CON 34)

Source
mechanical accessory source surface public model files; final fit and license unconfirmed

SAO-spacer model trail

The hardware archive includes several `iflfu-sao-spacer` model-file variants in OBJ, MTL, and 3MF forms. Their presence documents an accessory-design trail, not a shipped spacer, a particular revision, a compatible host, printed-material safety, fit, durability, included accessory, or permission to republish model or image assets.

Compatibility: IFLFU SAO (DEF CON 34)

Source
pre-event maker and self-submission availability record limited presale and $20 update wording published; fulfillment unconfirmed

Public IFLFU $20 update statement

The BigFuckingBadge page supplies a limited DEF CON 34 presale setting and an unlabeled $20 OffensiveSAO card, while the public Badgelife response names IFLFU SAO as an update to an existing item and gives $20. Those source statements do not prove current inventory, payment, final price, manufacture, shipment, pickup, event sale, recipient allocation, refund, replacement, support, or a completed handoff.

Compatibility: IFLFU SAO (DEF CON 34)

Source
public firmware interaction surface source code published; final-unit behavior unverified

PFC161 two-channel LFSR light behavior

The public C source includes PFC161 headers, configures active-low PA4/PA5 LED outputs, keeps separate LFSR state per channel, derives individual delay targets, and flashes channels from its main loop. This is source-level evidence for a two-channel randomized-light implementation, not proof of the exact final illuminated words, distribution of outcomes, timing, brightness, physical LED population, or behavior of every produced unit.

Compatibility: IFLFU SAO (DEF CON 34)

Source

Operational history

Issues & Camp Impact

explicit message, authorship, content, and endorsement boundary note

The public roster supplies an explicit phrase and describes randomized illumination of two words; the maker page characterizes an unlabeled card as romantic and raunchy. No reviewed source identifies the artwork/message author, rights holder, intended audience, content rating, venue suitability, recipient consent, permission for the phrase/artwork, or authorization, affiliation, or endorsement from DEF CON or another person/organization.

The entry preserves factual source language without claiming that any named/unnamed party authored, approved, sponsored, designed, endorsed, licensed, or consented to the message, artwork, or presentation.

Confidence
maker language and public self-submission only
Status
seller/self-submission wording recorded; authority and content rights unsubstantiated
Timeframe
current source pass
Source note
DEFCON 34 Badgelife Form response and BigFuckingBadge DEF CON 34 page.
firmware, release, flashing, and source-license gap note

The public code repository includes a Makefile, Easy PDK material, and C source, but reviewed roots did not visibly expose a README, release, or explicit LICENSE/COPYING file. Sources do not establish a final firmware binary, tag, release notes, version-to-production mapping, reproducible build, programmer/toolchain setup, supported flashing path, rollback/recovery, signed update, security assessment, vulnerability process, warranty, support policy, or a license grant for code/hardware/media.

The catalogue links the source trail without representing the artifact as fully open source, reproducibly buildable, safe to reflash, support-guaranteed, security-reviewed, or licensed for redistribution.

Confidence
public repository and current root review
Status
development source visible; release and license unconfirmed
Timeframe
repositories rechecked 2026-08-04
Source note
iflfu-v2-pfc161 and iflfu-hardware public repository roots plus IFLFU main.c.
hardware, power, connector, and safety documentation gap note

The public hardware repository shows KiCad, BOM/position, Gerber, spacer, and PFC161 material, and the code declares a two-LED PFC161 path. Reviewed sources do not establish final board revision/population, component substitutions, LED type/brightness, exact phrase construction, resistor/current design, SAO connector version/pinout, input supply range, power source, battery/charging path, current draw, voltage limits, protection, dimensions, materials, assembly process, test coverage, user instructions, safety warnings, EMC/RF/compliance evidence, or a host compatibility matrix.

The entry can point to a concrete archive without representing the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.

Confidence
public hardware tree and firmware pin declarations
Status
source files published; final electrical and mechanical specification incomplete
Timeframe
current source pass
Source note
iflfu-hardware repository and IFLFU main.c.
independent DEF CON association and credential boundary note

The maker uses DEF CON 34 presale language and the public Badgelife row identifies IFLFU SAO, but no reviewed source says DEF CON issued it, includes it with registration, grants admission, replaces a Human badge, has organizer endorsement, is required for BadgeLife, or has verified venue authorization.

The catalogue records a source-backed independent event association without portraying the SAO as official conference hardware, a credential, access item, universal attendee handout, or completed official distribution.

Confidence
maker page and public Badgelife self-submission
Status
independent planned SAO update associated with DEF CON 34
Timeframe
2026 pre-event source pass
Source note
BigFuckingBadge DEF CON 34 page and DEFCON 34 Badgelife Form response.
missing rights-cleared image note

No IFLFU SAO image is published because the reviewed BigFuckingBadge page, public Badgelife response, and Hexum064 repositories do not pair a selected factual artifact image with a reusable license or explicit permission basis, attribution, source URL, and processing notes.

The planned 2026 record remains source-backed and image-free rather than copying storefront media, roster-linked media, repository previews, KiCad/schematic renders, spacer-model previews, screenshots, placeholders, or generated imagery.

Confidence
local project policy
Status
needs selected, attributable, cleared original
Timeframe
current catalogue build
Source note
badge.gallery image policy and reviewed BigFuckingBadge, public Badgelife, and Hexum064 sources.
pre-event price, stock, and fulfillment boundary note

BigFuckingBadge advertises a limited DEF CON 34 presale, and its page plus the IFLFU roster row give $20 context, but DEF CON 34 has not yet begun in this source pass. Sources do not establish inventory, order/payment outcome, completed manufacture, packing, shipment, pickup, on-site sale, recipient count, refund, replacement, support, or final delivery.

Readers can distinguish public pre-event availability language from a completed sale, finished production run, or confirmed holder handoff.

Confidence
maker page, public self-submission, and current event timing
Status
limited presale and $20 claim published; outcome not recovered
Timeframe
as reviewed 2026-08-04
Source note
BigFuckingBadge DEF CON 34 page, DEFCON 34 Badgelife Form response, and calendar timing.
update lineage and prior-edition boundary note

The roster calls IFLFU SAO an update to an existing item and the public code repository is named `iflfu-v2-pfc161`, but this pass did not recover a source-backed earlier event edition, older product listing, release date, technical delta, production record, attribution, recipient scope, or compatibility statement. The maker card calls an unlabeled item its original/first OffensiveSAO, but does not print IFLFU.

The record preserves the visible update/v2 trail without inventing a previous event, assigning an exact earlier version, merging unknown revisions, or treating the seller card as standalone proof of historical IFLFU distribution.

Confidence
public roster update label and v2 repository name
Status
current update evidenced; prior lineage not reconstructed
Timeframe
current source pass
Source note
DEFCON 34 Badgelife Form response, BigFuckingBadge DEF CON 34 page, and iflfu-v2-pfc161 repository.

Resources

Sources