Roadmap
Phase-based planning — describes scope and intent, not deadlines. Phases 1–3 are complete and live. Phase 4 is active.
Phase 1 — rcpCodex MVP
✓ Complete- • Meshtastic USB gateway agent (rx/tx, telemetry, directory)
- • Meshcore USB gateway agent
- • TAM/KAM cryptographic trust system (Ed25519, CBOR)
- • Local control panel: rooms, routing, node directory, operator tools
Phase 2 — Global Relay
✓ Complete- • relay.remappedprotocol.org — central TAM/KAM federation relay
- • API key authentication + free/paid tier enforcement
- • Node sighting federation — global mesh node map data
- • Background sync and auto-push on trust events
Phase 3 — Portal
✓ Complete- • portal.remappedprotocol.org — user accounts and API key management
- • GitHub + Google OAuth + email magic link sign-in
- • Stripe billing — upgrade to paid tier
- • Admin panel: instance management, tier overrides
Phase 4 — Global Map
In progress- • Leaflet.js interactive map — nodes colored by fabric type
- • Real-time updates for paid tier, 24h delay for free
- • Filter by fabric: Meshtastic / Meshcore / LXMF / Reticulum
- • Map tab added to rcpCodex local dashboard
Phase 5 — LXMF / Reticulum
Planned- • Full LXMF gateway agent (receive + transmit)
- • Reticulum transport integration
- • Cross-fabric routing between Meshtastic, Meshcore, and LXMF
- • Pluggable adapter architecture for new fabrics
Phase 6 — Hosted Panel
Planned- • Cloud-hosted rcpCodex per user — no Pi required to run the panel
- • USB radio agents still run locally and connect back to hosted instance
- • Per-tenant isolation: separate DB, container, subdomain
- • Stripe-managed subscription; cancel to stop container
Phase 7 — Ecosystem
Planned- • Public REST/WebSocket API for third-party integrations
- • Community trust graphs — visualise trust relationships
- • SDK for building on top of the TAM/KAM protocol
- • Broader adoption: emergency comms, field operations, research