How It Works
rcpCodex is a self-hosted control panel that bridges mesh radio networks, manages node identity through cryptographic keys, and coordinates trust across a global federation of operator instances.
1. The control panel
What rcpCodex runs on
- • Raspberry Pi 4+ (or any Linux machine with Docker)
- • One or more USB-connected radio devices
- • Docker Compose — single command to start everything
- • SQLite database — all data stays on your machine
What it gives you
- • Live node directory with telemetry (SNR, RSSI, GPS, battery)
- • Rooms + routing: public channels and direct messages
- • Operator tools: search, filters, send, quick actions
- • Radio health monitoring and USB port assignment
- • Trust panel: issue and view TAMs for any node
2. The TAM/KAM trust system
Trust in RemappedProtocol is cryptographic — not reputation scores, not central authority. Two message types form the foundation:
Key Announcement Message
When rcpCodex starts, it generates an Ed25519 key pair. The KAM broadcasts your public key to the network — this becomes your operator identity. All TAMs you issue are signed with your private key.
Trust Assertion Message
TAMs are signed claims about nodes: Vouch (trust this node), Warn (be cautious), or Revoke (remove prior trust). Each TAM is CBOR-encoded, Ed25519-signed, and timestamped with an expiry.
How trust scores are calculated
Scores require multiple independent signers — a single operator can't fully trust or flag a node alone. This is by design: anti-sybil through consensus.
3. Mesh fabric integration
rcpCodex connects to radio networks via fabric agents — separate Docker containers that handle the hardware-specific protocol and forward events to the control panel.
USB serial agent. Full rx/tx, telemetry, directory, GPS.
USB serial agent. Node directory, telemetry, operator tools.
Reticulum stack integration — adapter in development.
Architecture designed for new fabrics with minimal changes.
4. Global federation
Each rcpCodex instance can connect to relay.remappedprotocol.org —
a central server that aggregates TAMs and node sightings from all connected instances.
TAMs you issue are automatically pushed to the relay and become visible to other operators. You pull down TAMs from the global store on a configurable schedule. Your API key tier controls how much detail you receive.
Node sightings — every radio node seen by any instance — are batched to the relay every 5 minutes, powering the global mesh map.
Two paths: self-hosted or hosted
Docker Compose on a Raspberry Pi. You control the hardware, the data, and the keys. Connect USB radios directly. Join the global relay with a free API key.
Setup guide →We run rcpCodex in the cloud. Your USB radio agents still run locally on your hardware and connect back to your hosted instance. No server setup required.
Get a hosted account →