Defcon stiffs badge HW vendor, drags FW author offstage during talk

A hacking conference is facing backlash after allegedly failing to fully pay the hardware vendor for its custom electronic badge, scrubbing that vendor’s branding from the device, and then having the unpaid firmware author physically removed from a badge talk over an Easter egg that credited the vendor and solicited donations. Commenters dissect possible contract and copyright implications, including whether the conference has a valid license to distribute the firmware, while also criticizing the optics of calling security and police over a nonviolent dispute. Many see the episode as emblematic of how once-grassroots tech events can slide into corporate-style control and reputational self-harm.

Badge functionality and development

  • Conference badge is a Game Boy emulator; firmware also runs PalmOS.
  • Hardware was designed and built by an external company; firmware was written separately, reportedly as unpaid volunteer work.
  • An Easter egg in the firmware credits the hardware company, notes that their credits were removed, and provides a donation address.

Alleged non‑payment and credit removal

  • Multiple comments allege the hardware vendor was not fully paid, with some mentioning a six‑figure shortfall (described as second‑hand).
  • Reported actions by organizers: vendor uninvited from the badge talk, their logo removed or obscured from plastics, and references removed from materials.
  • The firmware author says they worked for free; they emphasize the loss of credit as more painful than the missing money.
  • The hardware company later published its own statement (linked) to present its side.

On‑stage removal and police involvement

  • Video shows conference security escorting/carrying the firmware author off stage before the badge talk.
  • Accounts say organizers were angered by the Easter egg, labeled it “unauthorized code,” and removed the speaker; some note the speaker refused to leave voluntarily.
  • The speaker then held an impromptu talk outside; police were called but, per accounts, observed a peaceful gathering on public property and left.
  • Discussion is split on how “aggressive” the physical removal was and whether calling police is comparable to “swatting” (most say it is not).

Licensing, copyright, and contracts

  • Firmware author claims organizers have no license and suggests DMCA/copyright action; says they are now granting individual non‑transferable licenses to attendees.
  • Others argue there may be an implied or verbal license, given that firmware was supplied with the expectation it would be flashed to badges and showcased.
  • Some note that any license might be revocable for lack of consideration; others argue liability may fall on the hardware vendor, depending on contracts and indemnification.
  • There is disagreement over how strong any potential legal case would be and whether DMCA is the right tool.

Community reaction and broader context

  • Many commenters view this as a major PR failure and a sign of the event becoming more corporate, less “hacker‑spirited.”
  • Some express skepticism pending more facts or organizer statements; others say firsthand accounts and video are convincing.
  • Comparisons are made to other conferences (Black Hat, CCC, European and Dutch hacker camps, EMF), with several suggesting those as better alternatives.
  • There is side discussion on moderation of the story on HN, but no clear conclusion.
  • Several comments praise the technical quality of the badge work and the engineer’s broader body of projects, independent of the dispute.