P2P MURMUR.
REGISTRY: ONLINE murmur.debyte.space
⚡ PROTOCOL: RUSTP2P-QUIC // MULTIPLEXED MESH

TALK DIRECTLY.
NO SERVERS.
NO SURVEILLANCE.

Murmur is a peer-to-peer terminal chat application built in Rust. Powered by QUIC streams, NAT hole-punching, and the Ratatui TUI engine. Your conversations flow direct from machine to machine with zero intermediate cloud servers reading your packets.

Claim Your Global Handle → Launch Terminal Simulator
$ cargo install murmur-cli
QUIC // STREAM_DISPATCHER
TRANSPORT QUIC / UDP
TOPOLOGY Zero-Relay Mesh
DISCOVERY murmur.debyte.space
HANDSHAKE 0-RTT Resumption
HEAD-OF-LINE BLOCKING ELIMINATED
STRICT PEER-TO-PEER 100% RUST
INTERACTIVE PREVIEW

THE RATATUI TERMINAL SUITE

Sub-millisecond keyboard response, ASCII borders, and live peer streams. Try the simulated terminal below or interact with live controls.

murmur-tui // session: @debyte (id: 0x10000001)
QUIC: CONNECTED RTT: 14ms PEERS: 3
┌─ #global-mesh ──────────────────────────────────────────┐
[15:00:02] >>> Initialized rustp2p-quic endpoint on UDP 8080
[15:00:03] >>> Connected to global registry: murmur.debyte.space (3 active peers discovered)
[15:01:10] <@alice> Punched NAT hole over UDP! QUIC stream opened cleanly with 0-RTT.
[15:01:42] <@neo> No centralized servers storing our chat history. Just raw datagrams and direct encryption.
[15:02:15] <@debyte> Running Murmur on Linux Arch WSL with Ratatui 0.30. Latency is virtually 0ms.
>
SIMULATE PACKETS:
GLOBAL IDENTITY RESOLVER

CLAIM YOUR UNIQUE P2P HANDLE

To guarantee unique identities across the globe without a centralized chat gatekeeper, Murmur checks handles against our lightweight registry hosted at murmur.debyte.space.

@
GET https://murmur.debyte.space/api/check?username=:handle LIVE ON VERCEL
Need to register your node automatically from the Rust CLI? Murmur calls POST /api/register with your node public key and IP/QUIC addresses during murmur init.
THE ARCHITECTURE

WHY RUSTP2P-QUIC OVER TRADITIONAL CHAT?

Most chat apps force your data through corporate silos. Here is what happens when you switch to direct QUIC streams.

OLD SCHOOL // CENTRALIZED

Corporate Client-Server

You
──▶ [Central Server] ──▶
Friend
  • ❌ Your DMs are logged in a central database
  • ❌ Server downtime kills communication worldwide
  • ❌ Subject to arbitrary bans and corporate surveillance
  • ❌ Head-of-line blocking on sluggish TCP connections
NEW PARADIGM // P2P QUIC

Murmur Direct Mesh

Your Node
◀══ Multiplexed QUIC ══▶
Peer Node
Registry (murmur.debyte.space) only resolves peer addresses, never relays chats.
  • ✔ 100% Peer-to-Peer: Packets travel directly between machines
  • ✔ Multiplexed Streams: Loss in one stream does not freeze others
  • ✔ 0-RTT Connection Resumption: Instant reconnection across network shifts
  • ✔ Built for Terminal Power Users: Low CPU, zero bloat, pure Rust
ENGINEERING HIGHLIGHTS

BUILT FOR SPEED & SOVEREIGNTY

01

rustp2p-quic Multiplexing

Independent bidirectional streams for messages, file transfers, and peer status updates without head-of-line blocking.

TRANSPORT
02

STUN & NAT Traversal

Automated UDP hole-punching punches through complex home routers and symmetric NATs so you can talk anywhere on earth.

NETWORKING
03

Sub-Millisecond Ratatui UI

Zero webview, zero Electron, zero memory leaks. Written with Ratatui 0.30 and Crossterm for instant keystroke rendering.

INTERFACE
04

Global Handle Registry

Hosted on Vercel at murmur.debyte.space. Instant handle lookups and peer bootstrap routing with zero central chat storage.

DISCOVERY
GET RUNNING IN 60 SECONDS

FIRE UP YOUR MURMUR NODE

STEP 1

Install via Cargo

Build the high-performance binary directly from source or install via cargo.

cargo install murmur-cli
STEP 2

Claim Handle & Start Node

Spins up your QUIC listener on UDP 8080 and registers your handle at murmur.debyte.space.

murmur run --handle yourname --port 8080
STEP 3

Connect & Chat Direct

Establish direct encrypted QUIC streams to any peer by their handle.

murmur connect @alice