How Backspace Encryption Works

Why Encryption Matters

Every message you send over the internet passes through infrastructure you do not control. Routers, ISPs, data centers, CDN nodes — any of them can inspect, copy, or log what flows through. End-to-end encryption is the baseline defense against this, ensuring only sender and recipient can read a message. But encryption alone is not enough.

Centralized messengers can encrypt your message content while still harvesting who you talk to, when you talk, how often, and from where. This metadata paints a detailed picture of your life — sometimes more revealing than the messages themselves. A truly private system must address both the content and the context.

Backspace was designed from the ground up to solve both problems simultaneously.

Ed25519 Identity

When you launch Backspace for the first time, a cryptographic key pair is generated locally on your device using the Ed25519 elliptic curve algorithm. There is no registration form. No phone number. No email. No central authority issuing or approving identities.

Your identity is your key. Your public key acts as your address on the network, and your private key proves you are who you claim to be. Every message you send is signed with your private key, allowing recipients to verify authenticity without trusting any intermediary.

Because keys are generated locally using cryptographically secure randomness, no two users will ever collide. There is no database of identities to breach — because no such database exists.

AES-256-GCM Message Encryption

Every message is encrypted before it leaves your device. Backspace uses AES-256-GCM — the same authenticated encryption standard used by governments and financial institutions to protect classified and sensitive data.

GCM (Galois/Counter Mode) provides two critical properties in a single operation:

• Confidentiality — the message content is scrambled into ciphertext that is computationally infeasible to reverse without the key.
• Authentication — a built-in integrity tag detects any tampering. If a single bit is altered in transit, decryption fails entirely rather than producing corrupted output.

The P2P Advantage

Most traditional chat apps route every message through a central server. Even with end-to-end encryption, that server sees the metadata: who sent it, who received it, the timestamp, the IP addresses involved, the message size. The server operator can be compelled to hand this over, or it can be stolen in a breach.

Backspace uses a peer-to-peer architecture built on Hyperswarm. Messages travel directly between peers or through relay nodes that forward encrypted blobs without any ability to decrypt them. There is no central server that aggregates traffic. There is no single point to subpoena, hack, or pressure.

This architecture means there is no "master key" that unlocks all conversations. There is no database of messages sitting on a corporate server. The network is the users, and when they disconnect, their data goes with them.

Zero Metadata Design

Privacy is not just about encrypting content. Metadata — the data about your data — can be just as revealing. Who you talk to maps your social graph. When you talk reveals your routines. Where you connect from traces your movements.

Backspace is designed to produce as close to zero metadata as possible:

• No IP logging — the network does not record which IP addresses connect or when.
• No contact lists — there is no server-side social graph. Your contacts exist only on your device.
• No usage analytics — no telemetry, no tracking pixels, no behavioral profiling.
• No message storage — relay nodes forward and forget. Messages are not persisted on any infrastructure you do not control.

The result: even if every relay node in the network were compromised simultaneously, an attacker would gain nothing useful. There is nothing to harvest.

7-Day TTL

Backspace enforces a 7-day time-to-live on all messages by design. Messages are not permanently archived. They exist for seven days and then they are gone — truly gone, not "marked as deleted" while sitting in a backup somewhere.

This is a deliberate architectural choice, not a feature toggle. You cannot disable it. The system enforces impermanence because permanent records are a liability — for users, for operators, for everyone.

Proof of Uptime

Backspace uses a Proof of Uptime consensus mechanism for its name minting system. Instead of requiring computational waste (proof of work) or capital lockup (proof of stake), users earn the right to mint a human-readable name by contributing uptime to the network.

Run a node, stay connected, relay messages for others — and the network rewards you with the ability to claim a permanent identity name. This aligns incentives: the more you give to the network, the more the network gives back.

Your identity is earned, not purchased. It cannot be revoked by a central authority because no central authority exists.

Open Source

Every claim on this page can be independently verified. Backspace is fully open source. The encryption implementation, the networking layer, the relay logic, the key generation — all of it is published and auditable.

Trust in a privacy system must be verified, not assumed. Closed-source messengers ask you to take their word for it. Backspace asks you to read the code.