Nibble to Exbibit

A nibble is 4 bits, or half a byte. It encodes one hexadecimal digit (values 0–15, represented as 0–9 and A–F). Nibbles are important in BCD (binary-coded decimal) encoding, where decimal digits are packed two per byte (each digit occupying one nibble). Packed BCD is used in financial systems and legacy databases to represent decimal numbers without floating-point rounding errors.

Hexadecimal (base 16) maps perfectly to nibbles because 4 bits can represent exactly 16 values (2⁴ = 16). One byte = two nibbles = two hex digits. A byte value of 0xFF (255 in decimal) is two nibbles: F (1111) and F (1111). This mapping makes hexadecimal the natural notation for expressing binary data — programrs use hex because one hex digit always represents a fixed number of bits.

Binary-Coded Decimal (BCD) encodes each decimal digit (0–9) as a 4-bit binary value (nibble). Two decimal digits fit in one byte using "packed BCD". For example, the decimal number 47 is stored as 0100 0111 in packed BCD — each nibble holds one digit. BCD avoids the rounding errors of binary floating-point, which is why it is used in financial software, calculators, and legacy banking systems.

A nibble = 4 bits (1 hex digit). A byte = 8 bits (2 hex digits, 2 nibbles). A word = typically 16, 32, or 64 bits depending on the processor architecture (see the "word" unit for details). These are the fundamental granularities of digital data: nibble for hex/BCD, byte for text and addressing, word for native processor arithmetic.

Nibbles are rarely referenced directly in modern high-level programming but remain fundamental at the hardware level. Embedded systems, FPGA design, network packet parsing, and hardware description languages (VHDL, Verilog) regularly manipulate nibbles. The nibble is also the key concept behind hexdump utilities — the canonical way to inspect raw binary files and network packets.

An exabit (Ebit) = 10¹⁸ bits (SI decimal). An exbibit (Eibit) = 2⁶⁰ bits ≈ 1.1529 × 10¹⁸ bits (IEC binary). Exbibit is 15.29% larger — the cumulative product of using 1,024 instead of 1,000 at each of six prefix steps. This is the largest practically relevant SI vs IEC gap for bit units in current storage contexts.

Exbibit is used in: computer science academic literature on exascale computing, theoretical storage system design papers, and formal IEC/IEEE standards. No commercial product, OS, or consumer application currently displays exbibits. It is primarily a unit for academic and standards consistency — ensuring the IEC prefix family extends uniformly from kibi- to exbi- (and beyond to zebi- and yobi-).

After exbibit (Eibit, 2⁶⁰ bits) come: zebibit (Zibit, 2⁷⁰ bits) and yobibit (Yibit, 2⁸⁰ bits). These are defined in the IEC 80000-13 standard but have no current practical applications. The IEC binary prefix family deliberately mirrors the SI prefix family, ensuring consistent naming as computing scale continues to grow.

Frontier (Oak Ridge, 2022) achieved 1.194 exaFLOPS, with its Slingshot-11 fabric moving data at aggregate rates measurable in exbibits per second across 9,408 nodes. Aurora (Argonne, 2024) targets similar throughput with over 63,000 GPUs. At these scales, a single checkpoint of a full-system simulation can exceed 1 Eibit of state data, making exbibit a natural unit for describing I/O bandwidth requirements.

The IEC currently defines up to yobibit (Yibit, 2⁸⁰ bits). In 2022, the SI system added ronna- (10²⁷) and quetta- (10³⁰), but the IEC has not yet created matching binary prefixes (ronnibit? quettibit?). With global data creation projected to exceed 1 yottabit annually by the 2030s, pressure is mounting for the IEC to extend the binary prefix family — though the naming convention ("ronnibi-"?) remains an open question.