FeV
WorkAbout
0%//NAV
INDEX //BLECHAT
Systems / Mobile ProtocolsP2P ProtocolOffline-FirstState MachinesAndroid BLE

BLEchat

Constraint-driven peer-to-peer messaging protocol over Bluetooth Low Energy. Custom 4-step mutual handshake state machine, dynamic MTU negotiation, reliable packet chunking, and session hardening on Android 13–16.

// System Dossier2025
ROLELead Protocol Architect & Android Developer
CATEGORYSystems / Mobile Protocols
TECHNOLOGY STACK
KotlinJetpack ComposeAndroid BLE GATTCoroutinesState Machines
Live Platform↗Source Repository ↗
★Verified ReceiptsEMPIRICAL
✓Guaranteed reliable message delivery over lossy Bluetooth transport with zero packet loss or race-condition crashes across Android 13–16 devices.
✓100% serverless peer-to-peer operation requiring zero internet, cellular signal, or centralized coordination.
✓Frozen protocol specification (BLEChat Protocol v1.0) with formal state machine transitions and audit verification contracts.
NAVIGATE DOSSIER01 · Media Hub & Theater02 · Engineering Challenge03 · 4-Step Pipeline04 · System Blueprint05 · Adjacent Systems
2K FLUID THEATER
BLEchat
OFFLINE-FIRST ARCHITECTURE // BLECHAT2025 ARTIFACT SPECIFICATION
// 01 · THE PROBLEM STATEMENT & ARCHITECTURAL CONSTRAINTS

Bluetooth Low Energy is an inherently lossy, asynchronous, and fragile transport: packets drop silently, MTU limits vary by radio chipset, and concurrent callbacks cause hard GATT race conditions.

Bluetooth Low Energy is an inherently lossy, asynchronous, and fragile transport: packets drop silently, MTU limits vary by radio chipset, and concurrent callbacks cause hard GATT race conditions. Building a serverless chat system required designing a formal communication protocol from scratch with guaranteed message delivery, flow control, and session hardening.

// 02 · 4-STEP SYSTEM ENGINEERING PIPELINE
STEP 01

Engineered a strict 4-step mutual handshake state machine (HANDSHAKE_INIT → ACK → CONFIRM → CONFIRM_ACK) enforcing mutual SUCCESS verification and deterministic client/server role allocation before data transmission.

STEP 02

Defined a frozen wire-frame protocol ([TYPE][FLAGS][MSG_ID][CHUNK_IDX][TOTAL][TTL][PAYLOAD]) with dynamic MTU adaptation and serialized single-chunk transmission locked to BLE write callbacks.

STEP 03

Implemented atomic message reassembly and explicit ACK/NACK signaling emitted only after full payload verification, eliminating partial message corruption.

STEP 04

Hardened session security against hostile transport states: enforced rolling message IDs for replay protection, TTL packet expiration, link-drop recovery, and detailed protocol audit logging.

// 03 · SYSTEM BLUEPRINT & DATA FLOW SCHEMATIC
PURE SVG VECTOR ENGINE
mutual 4-step handshake protocol (state machine)client → init · server → ack · client → confirm · server → confirm_ack (mutual success lock)frozen wire-frame protocolTYPEFLAGSMSG_IDCHUNK_IDXTOTALTTLPAYLOAD (MTU-ADAPTIVE)reliable gatt chunking enginedynamic mtu negotiation · 1 chunk per write callbackatomic reassembly · ack emitted only on full verifyzero packet drops across android 13–16session hardening & audit loggingrolling msg_id replay defense · ttl packet expirationlink-drop recovery · deterministic peer selectionstrict state transition logs as protocol contractsblechat protocol v1.0 · zero cloud/wifi/cellular · 4-step mutual handshake · frozen wire format
MORE SYSTEMS ARCHITECTUREFull Works Index →

Next System

Blinky

AI / Desktop Agent

Next System

VoiceNotes

Local-First / AI Platform

Next page

About me

→

You are one click away

Let's build something.

Open to collaboration, hackathons, and interesting systems problems.

EmailGitHubLinkedInX / TwitterAbout

© 2026 Gourish Julka

Amritsar, India