BitPads — What It Is, How It Works, Why It Exists
What it does
BitPads is a universal binary communication protocol. It encodes structured records — from a single heartbeat byte to a fully identified, timestamped, valued, tasked, and annotated civilisational record — in as few as one byte.
BitPads is not hardware. It is not a device. It is a protocol: a specification for how to encode, transmit, and decode structured information across any channel, including channels too constrained for JSON, XML, or even CSV. SMS messages, satellite links, sub-GHz radio, KaiOS feature phones, low-bandwidth field operations across sub-Saharan Africa — BitPads works where other formats cannot fit.
BitPads sits as a meta-layer wrapping BitLedger (the double-entry financial transmission protocol) and providing mode declarations, type identification, and enhancement commands that extend any base record with additional structured data.
How it works
BitPads uses an 8-bit meta layer that declares the mode and type of each frame. A frame is the fundamental unit — a self-contained binary packet that carries a payload and enough metadata to be independently verifiable.
The protocol operates across a frame spectrum: different packet structures for different purposes, from a 1-byte heartbeat (alive signal) through compact sensor readings, financial transactions, task records, and fully annotated compound documents.
Key architectural elements:
- Mode declarations — the first bits of a frame declare what kind of data follows, allowing receivers to parse without prior negotiation.
- Enhancement commands — a grammar for extending base records with nested, structured annotations. Enhancements can be chained, nested, and composed according to a formal grammar documented across the enhancement specification.
- CRC-15 validation — every frame carries integrity verification.
- Bit-level function coloring — different regions of a frame serve different functions (mode, data, enhance, identity, time, task), each visually and structurally distinct in the specification.
The protocol is designed for conservation: the same structural guarantees that apply to financial double-entry (nothing created or destroyed without a balancing counterpart) apply to any domain — spatial coordinates, IoT telemetry, manufacturing records, agricultural data.
A companion CLI tool (bitpads-cli) provides decoding, inspection, and validation of BitPads frames, with a separate assembly encoder for constructing frames from human-readable input.
Why it exists
The world runs on text formats — JSON, CSV, XML — that were designed for machines with abundant bandwidth, storage, and processing power. But much of the working world does not have those luxuries. A sensor on a remote pipeline, a feature phone in a rural market, a satellite uplink with 30 seconds of window — these channels need a format that respects their constraints.
BitPads exists because structured communication should not require structured luxury. A protocol that can encode a complete financial transaction in 40 bits, or a full operational record in a few hundred, opens channels that text formats cannot enter.
The protocol also exists because Babb believes the encoding layer matters for durability. Text formats are ambiguous, version-dependent, and brittle across decades. A binary protocol with a fixed, formally specified structure can be read in 50 years by any system that has the specification — no parser updates, no library dependencies, no format migrations.
Current status
- Protocol: BitPads v0.1.0 (initial formal release)
- Specification: 14+ reference documents covering BitLedger, BitPads v2, CLI, Compound Mode, Enhancement Grammar, Enhancement Nesting, Enhancement Telegraph, Universal Domain, and Engineering guides
- CLI:
bitpads-cli— decoder, inspector, validator - Standard: BitPads Standard (normative)
- Documentation site: bitpads.org
Where to find it
- Protocol site: bitpads.org
- Standard: BitPads Standard
- CLI: bitpads-cli
- Tools: bitpads-tools