MNSEC 2025 · Mongolia · 2025
Completed 418-unit, three-variant MNCERT/CC electronic-badge collection
A completed MNSEC 2025 electronic-badge collection commissioned by MNCERT/CC and documented by Beelog Technologies. Beelog's public project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT/CC; the public MNSEC2025BADGE archive identifies the order with the September cybersecurity conference, says three badge types were completed, and preserves Gerber, schematic, firmware, example-code, and supporting-material directories. The sources do not establish attendee allocation, a per-unit delivery record, final unit-by-unit configuration, safety validation, or reusable image provenance.
People
MNCERT/CC's official post establishes the MNSEC 2025 event, and Beelog's project page identifies MNCERT CC as the customer for the 418-unit electronic-badge custom order. This is an organization and commissioning-context credit, not a claim of individual badge design, manufacture, delivery, or image-rights authority.
SourceBeelog's official project page says it designed, manufactured, and developed the MNCERT CC electronic-badge project, and the public MNSEC2025BADGE archive names Beelog Tech as developer and designer. The credit does not assign a complete production, recipient-distribution, safety, or image-rights role beyond the sourced statements.
SourceIt adds Mongolia to the public hacker and security-conference badge map with a completed, source-backed electronic-badge delivery rather than a speculative ticket or generic conference credential. The record keeps the published quantity and multi-variant source trail distinct from unsupported claims that every MNSEC attendee received the same device or that every archive asset matches every delivered unit.
The public archive contains three named Gerber archives, two schematic PDFs, sensor material, and example sources. Its README identifies an ESP32-C3 BlackCat badge context and references RGB-LED and OLED/TFT display-support libraries. Those source details do not map a complete bill of materials, component population, display, power system, sensor set, board revision, or electrical behavior to each of the three variants or all 418 delivered units.
The public archive preserves a firmware binary, a named sketch, and several component-oriented example sketches. It does not provide a reconciled final firmware manifest, signed release history, source-to-unit mapping, software support policy, complete dependency licence inventory, or a safe operating or reconfiguration procedure for all delivered badges.
MNCERT/CC's official posts place MNSEC 2025 at the Shangri-La Ulaanbaatar Hotel ballroom on September 25 under the Cyber Resilience theme. Beelog's project page describes a custom MNCERT/CC electronic-badge delivery covering hardware, firmware, and deployment-ready work; the badge archive credits Beelog Tech as developer and designer. The record treats that published delivery claim as event-artifact evidence without inventing an attendee-wide entitlement or individual recipient history.
Source-backed hardware metadata
Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.
The public MNSEC2025BADGE archive identifies the MNCERT/CC-commissioned MNSEC 2025 artifact as an electronic badge collection. It does not establish attendee-wide allocation, final unit parity, or image rights.
Signal sourceLifecycle
Beelog's official project page says it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. The companion archive identifies MNSEC 2025 and says the work was completed, but neither source publishes ticket eligibility, recipient identities, handoff records, or evidence that all conference attendees received a badge.
SourceThe repository preserves two schematic PDFs and three Gerber archives alongside support material. These public documents make the collection technically discoverable, but are not presented as build, repair, power, safety, fabrication, or all-unit-parity instructions.
SourceThe project tree contains a firmware binary, a named sketch, and component-oriented examples. This establishes a public software trail without reproducing connectivity, configuration, update, or operating instructions or claiming a final deployed image for every delivered unit.
SourceThe source archive says three badge types were completed and publishes named Gerber archives for Albat, HaruulZangi, and Humun. This preserves the documented multi-variant design trail without assigning a particular unit, role, or feature set to an attendee or assuming each archive exactly matches final delivered production.
SourceOperational history
The catalogue records a completed event-associated badge collection without making an attendee-wide allocation or individual delivery claim.
Public source material remains linkable without claiming a reproducible, supported, secure, current, or uniform operational setup for delivered badges.
The Mongolia record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The entry keeps the collection-level hardware description bounded and does not imply that every unit had identical hardware, display, sensors, power, firmware, or physical finish.
The record documents a real completed electronic badge collection without treating open project material as independently validated operating, fabrication, repair, or safety guidance.
The catalogue links the source archive and license but publishes no local badge image until an image-specific rights-cleared source is available.