Hacker Con Badges

MNSEC

MNSEC 2025

The completed September 25, 2025 MNSEC Cybersecurity Conference in Ulaanbaatar, themed Cyber Resilience. MNCERT/CC's official event posts establish the conference context, while Beelog Technologies and its public MNSEC2025BADGE archive identify a completed custom MNCERT/CC electronic-badge order: 418 badges across three types. The public project tree preserves source material, but does not establish attendee allocation, final unit-by-unit configuration, delivery recipients, safety validation, or reusable image rights.

Shangri-La Ulaanbaatar Hotel ballroom, Ulaanbaatar, Mongolia · Mongolia · 2025

MNSEC 2025 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.

Lifecycle

Add-ons & Upgrades

MNSEC 2025 Electronic Badge Collection manufacturer-reported completed custom order

completed delivery context

418-unit MNCERT/CC custom-order delivery record

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.

Compatibility: MNSEC 2025 MNCERT/CC-associated badge collection only; not a universal MNSEC admission or attendance entitlement

MNSEC 2025 Electronic Badge Collection source archive published

hardware documentation

Public schematic and Gerber material

The 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.

Compatibility: Published MNSEC2025BADGE design material; no generic fabrication or safe-modification claim

MNSEC 2025 Electronic Badge Collection source archive published

software source context

Public firmware and example-code material

The 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.

Compatibility: MNSEC2025BADGE source material only; final release-to-hardware mapping and support status unknown

MNSEC 2025 Electronic Badge Collection public Gerber and repository description

variant design archive

Three named badge-design variants

The 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.

Compatibility: MNSEC2025BADGE source archive only; final revision and unit distribution not established

Operational history

Issues & Camp Impact

MNSEC 2025 Electronic Badge Collection note

attendee allocation, recipient, and handoff boundary · manufacturer project page and public source archive · completed quantity reported; recipient outcome unrecovered

Beelog reports that 418 electronic badges were delivered to MNCERT CC as a custom order, and the archive says the MNSEC 2025 badge work was completed. The reviewed public sources do not publish ticket eligibility, role allocation, recipient identities, registration linkage, pickup location, handoff report, returns, replacements, or evidence that every conference attendee received a badge.

The catalogue records a completed event-associated badge collection without making an attendee-wide allocation or individual delivery claim.

MNSEC 2025 Electronic Badge Collection note

firmware release and operational-configuration boundary · public firmware directory and README · binary, sketch, and examples available; final deployment record unrecovered

The repository provides a firmware binary, a named sketch, and examples, but it does not document a signed or reconciled final release, source-to-unit mapping, dependency lockfile, update/support policy, final connectivity configuration, service availability, data practice, or privacy policy. No credentials or operational configuration details are reproduced in this record.

Public source material remains linkable without claiming a reproducible, supported, secure, current, or uniform operational setup for delivered badges.

MNSEC 2025 Electronic Badge Collection note

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

No MNSEC 2025 Electronic Badge Collection 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 Mongolia record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

MNSEC 2025 Electronic Badge Collection note

multi-variant hardware and final-unit mapping gap · public repository tree · three design archives visible; production mapping unrecovered

The repository describes three badge types and publishes three named Gerber archives plus two schematic PDFs. It does not publish a reconciled production BOM, revision history, component-substitution record, test plan, final assembly record, per-variant quantity split, or mapping from technical files to each delivered badge.

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.

MNSEC 2025 Electronic Badge Collection note

power, sensor, and electrical-safety gap · public archive review · design materials visible; safety validation unrecovered

The archive includes schematic, Gerber, sensor, and example-code material, but reviewed public sources do not establish final battery chemistry, charging/protection behavior, power budget, electrical limits, thermal result, sensor calibration, component substitutions, assembly quality control, certification, compliance, or a universal safe-use outcome.

The record documents a real completed electronic badge collection without treating open project material as independently validated operating, fabrication, repair, or safety guidance.

MNSEC 2025 Electronic Badge Collection note

source-license, media-rights, and branding scope boundary · repository license and public-site review · BSD source/binary license recorded; selected-image rights unresolved

The repository root publishes a BSD 2-Clause license credited to DavgaBeelog, while Beelog's current public site reserves its own rights. The reviewed archive and event pages do not pair a selected factual physical badge photo or upstream render with a complete source URL, image-specific reuse basis, attribution, and processing provenance. The BSD source/binary statement is not assumed to licence all photographs, renders, artwork, brands, or physical artifacts.

The catalogue links the source archive and license but publishes no local badge image until an image-specific rights-cleared source is available.

Resources

Beelog MNCERT CC Electronic Badge Project manufacturer project record · Beelog's official project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order, including hardware, firmware, and deployment-ready work. The page does not identify individual recipients, per-unit configuration, ticket entitlement, or image-reuse permission. MNCERT/CC MNSEC 2025 conference announcement official event announcement · MNCERT/CC's official announcement identifies the September 25, 2025 MNSEC Cybersecurity Conference, Cyber Resilience theme, and Shangri-La Ulaanbaatar Hotel ballroom. It establishes the completed event context, not badge allocation, hardware, delivery, or image rights. MNCERT/CC MNSEC 2025 conference recap official organizer recap · MNCERT/CC's official organization feed records a post-event MNSEC 2025 recap. It corroborates completed organizer event context but does not identify a badge programme, recipient list, or technical artifact details. MNSEC2025BADGE Gerber directory public Gerber archive · The public directory contains separate Gerber archives for Albat, HaruulZangi, and Humun. It corroborates three named design variants without proving that all archive files correspond exactly to every delivered unit. MNSEC2025BADGE public source archive public badge source archive · The public repository identifies the MNSEC 2025 electronic-badge commission, says three badge types and 418 completed units, names MNCERT/CC and Beelog Tech, and links hardware, firmware, and supporting material. It is a project archive, not a recipient ledger or blanket licence for all media. MNSEC2025BADGE firmware directory public firmware and example-code archive · The public directory contains a firmware binary, a named sketch, and example source folders. It does not establish a reconciled final release, source-to-unit mapping, support lifecycle, or safe operating/reconfiguration instructions. MNSEC2025BADGE schematic directory public schematic archive · The public directory contains two schematic PDFs. It establishes a technical design archive without proving final BOM, final board revision, uniform unit population, production testing, electrical safety, or per-variant delivery state. MNSEC2025BADGE BSD 2-Clause license source archive license · The repository root publishes a BSD 2-Clause license credited to DavgaBeelog. This is recorded as a source-archive licence statement, not assumed to resolve rights in physical artifacts, brands, photos, renders, or a selected local image.

Sources

Beelog Technologies: MNCERT CC Electronic Badge Project Retrieved 2026-05-15 · Primary manufacturer project record stating that Beelog designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. It does not map those units to named event recipients or selected source-media rights. DavgaBeelog / MNSEC2025BADGE: BSD 2-Clause License Retrieved 2026-05-15 · Primary repository license text. It is scoped as the archive's BSD 2-Clause source/binary statement and is not treated as automatic permission for photographs, renders, badges, branding, or a locally published image. MNCERT/CC: MNCERT/CC official MNSEC 2025 recap Retrieved 2026-05-15 · Official organizer feed recording a post-event MNSEC 2025 recap. It corroborates the conference's completion without attributing badge design, manufacture, delivery, or media permission. MNCERT/CC: MNSEC 2025 Cybersecurity Conference Retrieved 2026-05-15 · Primary official event announcement for the September 25, 2025 Ulaanbaatar conference, Cyber Resilience theme, and venue. It does not describe the badge collection or prove an attendee allocation. helicopteresdc / Beelog Tech: MNSEC2025BADGE Retrieved 2026-05-15 · Primary public badge archive identifying the MNSEC 2025 commission, MNCERT/CC customer context, Beelog Tech role, three badge types, and 418 completed units. Its design archive is not treated as proof of every final delivered configuration. helicopteresdc / Beelog Tech: MNSEC2025BADGE Badge PCB Gerber Files Retrieved 2026-05-15 · Primary public source for the three named Gerber archives. It supports the collection's multi-variant design trail, not an exact final manufacturing or recipient record. helicopteresdc / Beelog Tech: MNSEC2025BADGE Firmware Retrieved 2026-05-15 · Primary public source for the preserved firmware binary, named sketch, and examples. It does not establish a complete released software inventory, operational configuration, or support policy. helicopteresdc / Beelog Tech: MNSEC2025BADGE Schematics Retrieved 2026-05-15 · Primary public source for the two schematic PDFs. It establishes design-document availability without a production, safety, or all-unit configuration guarantee.