BASE EXTENDER // RADIX ENCODING ARCHITECTURE & CRYPTOGRAPHIC DESIGN
Technical breakdown of RFC 4648 Base32 5-bit groupings and Bitcoin Base58 alphanumeric compression.
RFC 4648 Base32: The 2FA & Authenticator Backbone
Base32 represents binary data in an ASCII string format by translating blocks of 40 bits (5 octets) into 8 Base32 characters (each encoding 5 bits).
- Case Insensitivity: Base32 symbols only utilize capital letters `A-Z` and digits `2-7`. It can be dictated over voice channels or typed on mobile keypads without shift keys.
- Padding Requirements: When the input byte count is not divisible by 5, output is padded with `=` characters to reach 8-character multiples.
- Dominant Applications: Used universally in RFC 6238 TOTP (Time-based One-Time Passwords like Google Authenticator keys), Tor `.onion` addresses, and DNS record serialization.
Bitcoin Base58: The Satoshi Nakamoto Alphabet
Designed specifically by Satoshi Nakamoto for Bitcoin addresses, Base58 is an alphanumeric binary-to-text encoding that eliminates visual human transcription errors.
- Ambiguity Elimination: Four visually confusing characters are explicitly banned: `0` (zero) and `O` (capital O), plus `I` (capital i) and `l` (lowercase L).
- Punctuation Free: Avoids non-alphanumeric symbols like `+` and `/` found in Base64, ensuring that double-clicking text selects the entire address.
- Leading Zero Preservation: Leading null bytes (`0x00`) are mapped directly to the character `1`, preserving cryptocurrency network prefix identifiers.
Airgap Zero-Log Privacy Architecture
Base Extender performs all radix transformations client-side inside the browser memory space using vanilla JavaScript typed arrays and BigInt arithmetic. No confidential private keys, seed passphrases, or binary digests are ever sent over network sockets.