Carolina Code Conference

Carolina Code Conference 2026

The completed August 14-15, 2026 Greenville polyglot and cybersecurity conference. Its organizer's event-week update documents check-in and Circuit Board Badge pickup, while the named badge partner's public source archive documents the ESP32-S3/CircuitPython platform. The public sources do not provide a recipient ledger or a rights-cleared physical-badge image.

Flywheel Coworking, 25 Goldsmith St, Greenville, South Carolina · United States · 2026

Carolina Code Conference 2026 Circuit Board Badge

Carolina Code Conference's organizer documented Circuit Board Badge pickup for its August 14-15 event, and its named badge partner published a source archive for an ESP32-S3 CircuitPython board. The archive identifies five WS2812 LEDs, three buttons, a 1.77-inch ST7735S display, Micro-USB, and CR123A or USB power. It supports a released badge software and hardware reference, not a recipient ledger, an independently audited final production configuration, or a rights-cleared physical-badge image.

Lifecycle

Add-ons & Upgrades

Carolina Code Conference 2026 Circuit Board Badge pre-event organizer statement; final outcome unrecovered

availability context

Initial-event-order availability statement

The organizer said there would be no additional circuit-board badges after the initial event order. That records intended scarcity context only; it does not establish order count, sales, manufacturing quantity, stock, ticket cutoff outcome, fulfilment, or recipient delivery.

Compatibility: Carolina Code Conference 2026 Circuit Board Badge

Carolina Code Conference 2026 Circuit Board Badge event-week organizer logistics and public source archive

electronic badge

Organizer-documented programmable circuit-board badge

The June announcement and August event-week guide identify a programmable circuit-board badge with five LEDs, three buttons, a mini screen, Wi-Fi, and USB programming. The partner archive gives a public hardware/software reference, but neither source independently audits every final board or recipient handoff.

Compatibility: Carolina Code Conference 2026 Circuit Board Badge

Carolina Code Conference 2026 Circuit Board Badge organizer-named partner; matching public source archive

named project partner and source publisher

Circuit Board Medics badge partnership

Carolina Code Conference names Circuit Board Medics as its badge partner, and that organization published the matching public source archive. This establishes a bounded partnership and source-publication trail, not a complete design, manufacturing, fulfilment, or image-rights attribution.

Compatibility: Carolina Code Conference 2026 Circuit Board Badge

Carolina Code Conference 2026 Circuit Board Badge commit-pinned partner source archive

public software experience

CircuitPython editable software surface

Circuit Board Medics' MIT archive documents CircuitPython 10.2.1, editable `code.py`, a preloaded launcher, tutorials, a serial-console guide, and samples. It does not establish a signed or immutable factory image, deployment record, security review, or support commitment.

Compatibility: Carolina Code Conference 2026 Circuit Board Badge

Operational history

Issues & Camp Impact

Wi-Fi, power, electrical-safety, and privacy boundary · public technical reference and sample archive · capability and power paths documented; operating policy unrecovered

The archive documents Wi-Fi samples, Micro-USB or CR123A power, automatic USB-over-battery switching, and no on-board charging. It does not establish radio settings, band/region, antenna configuration, credentials, event network behavior, data collection/retention, privacy policy, security review, current draw, runtime, battery handling, thermal performance, electrical limits, regulatory testing, venue policy, or user safety guidance.

No live network, privacy, lawful-operation, battery-life, charging, or electrical-safety claim is inferred beyond the documented reference behavior.

allocation, color-variant, and availability boundary · official pre-event recipient wording · announced variants documented; quantities and outcome unrecovered

The organizer announced green attendee badges and purple sponsor/speaker versions, and said there would be no additional circuit-board badges after the initial event order. It does not provide counts, ticket-tier mapping, eligibility rules, order quantity, final color/render confirmation, lost-badge policy, transfer policy, scarcity outcome, or completed allocation evidence.

The record preserves the organizer's announced recipient distinction without claiming that all attendees, sponsors, or speakers obtained a particular final unit or color variant.

badge rendering and visual-rights boundary · official announcement image review · official renders visible; local reuse not cleared

The organizer's badge announcement displays renderings of the planned green and purple circuit-board badges, but the page does not provide an image-specific reusable license or explicit local-publication permission, photographer/render author attribution, processing basis, or final physical-artifact identity. It also depicts a planned rather than confirmed delivered object.

No local badge image is published; the record remains source-backed and image-free pending a factual artifact image or official upstream raster with complete reuse basis, attribution, and processing provenance.

event completion and distribution boundary · official dated event-week logistics and elapsed event dates · event complete; per-recipient handoff unverified

The organizer's August 10 guide describes planned check-in badge handoff for attendees and later/single-day arrivals, and the conference dates have passed. Reviewed sources do not provide completed-pickup counts, an individual receipt log, ticket-to-badge mapping, stock, failed delivery, replacement terms, or a recipient ledger.

The catalogue treats the dated conference as completed and its badge platform as source-backed without representing the logistics plan as proof that a particular person received a particular unit.

firmware, release, and support boundary · commit-pinned MIT partner source archive · source and examples public; deployed-image/support scope unrecovered

The archive publishes CircuitPython 10.2.1 documentation, a launcher, examples, libraries, and a final event-day Weather-sample fix. It does not provide a signed/tagged release, immutable factory image, serial-number-to-build mapping, recovery image, release process, vulnerability policy, support owner, service terms, or evidence that every unit carried the same files.

The catalogue can describe a public editable software path without claiming a production-certified firmware release, uniform field deployment, long-term maintenance, or safe configuration.

missing rights-cleared image · local project policy · needs licensed original replacement

No Carolina Code Conference 2026 Circuit Board Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

public technical reference and final-unit parity boundary · commit-pinned partner source archive · technical reference public; production parity unaudited

The public README identifies an ESP32-S3-WROOM-1-N8, ST7735S LCD, WS2812 LEDs, three buttons, Micro-USB, GPIO pads, and CR123A/USB power, but it does not provide schematics, PCB layout, BOM, fabrication package, assembly/test records, component substitutions, manufacturing quantity, compliance evidence, or an independent inspection of distributed units.

The entry is a traceable public platform reference, not a reproducible manufacturing record, safety assessment, interoperability guarantee, or proof that every event unit matched the README.

Resources

Sources