Jason Taylor
Listed under that title on the official OzSec 2026 leadership list. The badge talk lists a speaker named Jason without a surname.
SourceOzSec 2026 · United States · 2026
ESP32-S3 virtual-pet badge with a round display and Bluetooth Chi trading
The Conagotchi, the OzSec 2026 conference badge for the October 23-24, 2026 Wichita conference at the Hyatt Regency. The official site is themed after it, schedules a badge-crew talk called Conagotchi: From Concept to Completion, names Raxis as badge sponsor, and tells attendees to bring a USB data cable for their badge. A community Rust firmware published during the conference describes the stock badge as an ESP32-S3 board with a round GC9A01 display, eight RGB LEDs, five buttons, infrared, and MicroPython firmware that trades Chi with other badges over Bluetooth LE.
People
Listed under that title on the official OzSec 2026 leadership list. The badge talk lists a speaker named Jason without a surname.
SourceListed as Badge Sponsor on the official OzSec 2026 site.
SourceHandle listed with Jason, Angle, and Daniel on Conagotchi: From Concept to Completion and on the official leadership list.
SourceAuthor of the alternative Rust firmware and design notes that document the stock hardware and trading protocol; not presented as official badge firmware.
SourceOrganizer of the Wichita conference and publisher of the Conagotchi-themed official site, schedule, and speaker pages.
SourceIt extends the OzSec badge lineage, whose OzSecICT GitHub organization also holds firmware repositories for the 2023 and 2024 badges and the 2025 CRASHANDBURN archive, and it shows a virtual-pet badge whose stock trading protocol was documented and extended by an attendee within a day of the conference opening.
OzSec has not published a schematic, BOM, or board files for 2026. John Vishnefske's community firmware design notes, which say their pin table comes from the stock firmware's config.py and the board silkscreen, list an ESP32-S3-WROOM-1 module with 8 MB flash and no PSRAM, a 240x240 GC9A01 round SPI display, a chain of eight WS2812B LEDs, a red alert LED and a green raffle LED, five buttons (BOOT, START, SELECT, LEFT, RIGHT), a 38 kHz infrared transmitter and receiver, a link UART, and USB-Serial-JTAG on the native USB pins. The notes mention a removable battery but not its type or capacity. These are a third party's readings of one badge, not an organizer specification.
The same notes describe the stock image as MicroPython 1.27 with a littlefs filesystem and a separate DOOM partition. Stock badges trade Chi over Bluetooth LE using lobby advertisements under manufacturer ID 0x5A4F and, when a radio key is present on the badge, sign packets with a truncated HMAC-SHA256 tag. OzSec has not published the stock firmware source. The community Rust firmware (v0.1.0, October 24, 2026) keeps the stock files, radio key, and DOOM partition, adds an animated pet, contacts, a GATT service, synchronised LED patterns, and a host tool, and can restore the stock image.
The OzSec 2026 website is styled as a Tamagotchi-like handheld, with a stylesheet headed CONAGOTCHI, OzSec 2026 Tamagotchi Design System. The speakers page says the badge creation crew had worked on the badge for the past year; the talk is credited to Jason, Chief Pixel Chef, Angle, and Daniel. The official site has not yet posted a wrap-up, attendance figure, or badge count.
Lifecycle
John Vishnefske's Rust firmware keeps stock Chi trading, adds contacts, a pet screen, a GATT service, LED sync across badges running it, Wi-Fi and BLE scans, and a host tool; its adopt command backs up the stock image first and restore puts it back. Some stock-interop features were still marked pending in the design notes on October 26, 2026.
SourceStock badges advertise in a lobby under manufacturer ID 0x5A4F and trade Chi with nearby badges; with a radio key present, packets carry a 3-byte truncated HMAC-SHA256 tag.
SourceThe stock flash image includes a separate DOOM partition next to the MicroPython firmware and filesystem; the community firmware README says DOOM stays on the badge after reflashing.
SourceOperational history
Component details are attributed to the community notes. Battery type, board revision, enclosure, and production variants stay open.
The record stays image-free instead of copying event, social-media, or repository photos.
The edition is not marked completed, and the record makes no claim about badge count or allocation.