Aaron Christophel
The Hardwear.io badge post points attendees to the OpenEPaperLink workflow; Aaron Christophel is the public project owner of the OpenEPaperLink repository.
SourceHardwear.io Netherlands 2023 · Netherlands · 2023
Reused retail e-paper price-tag badge
A Hardwear.io Netherlands badge built from reused e-paper price tags, with attendee-facing firmware behavior documented after the conference.
People
The Hardwear.io badge post points attendees to the OpenEPaperLink workflow; Aaron Christophel is the public project owner of the OpenEPaperLink repository.
SourceThe badge extends the European badge map into hardware-security conference reuse culture: a retail e-paper label became a conference identity object, a firmware target, and a post-event hacking prompt.
The public Hardwear.io writeup identifies the badge as an e-paper price tag. It points attendees toward OpenEPaperLink-style access-point infrastructure for talking to the tags after the event.
The writeup documents attendee behavior such as exiting presentation mode around the 6:30 mark, uploading pictures through access-point tooling, and using OpenEPaperLink documentation for the badge's post-event workflow.
Hardwear.io framed the badge follow-up as a practical 'what can you do with the e-paper badges you received' post, making the badge part of the after-conference hacking surface rather than only an entrance token.
Lifecycle
The badge post directs attendees toward OpenEPaperLink access-point tooling so the reused e-paper tags can be updated after the conference.
SourceHardwear.io documents leaving the badge's presentation mode around the 6:30 mark and uploading pictures afterward, turning the attendee object into a reusable e-paper display target.
SourceOperational history
The Netherlands record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The compendium treats it as a badge-hacking object and post-event firmware target while avoiding unsupported claims about custom hardware design.
Future work should add chip-level tag models, packet captures, firmware forks, and attendee writeups if they are published.