fleetmesh connects independent relays into an accountable multi-protocol federation. Relays coordinate through published budgets, cryptographic receipts, zero-knowledge and multi-provider AI compute, live video reflection, sovereign key login, and declarative orchestration manifests — spanning Nostr, AT Protocol, ActivityPub, Secure Scuttlebutt, p2panda, and Rhio/Bao.
Foundations · Core Principles
fleetmesh provides relay operators with verifiable resource bounds while preserving independent local policies.
The mesh evaluates protocol compliance through verifiable arithmetic. Rate limits and sync rules follow explicit contracts. Content moderation remains local to each edge relay face.
Nodes publish signed grant budgets (kind 30801). Peers exchange monotonic receipt hash chains (budget/1.0) to confirm transfer volumes.
Nodes retain complete control of stored data upon joining or leaving the federation. Shard synchronization uses NIP-77 Negentropy range bisection to prevent duplicate transfers.
Protocol compatibility is determined by the SHA-256 digest of published JSON schemas. Nodes with matching schema digests peer directly across the network.
Interoperability · Standards Architecture
fleetmesh builds upon established IETF, W3C, Nostr, AT Protocol, ActivityPub, Secure Scuttlebutt, p2panda, and Bao specifications to provide identity, multi-protocol transport, replication, accounting, and compute.
| Standard / Specification | Category & Footing | Implementation Role in fleetmesh | Specification Anchor |
|---|---|---|---|
| W3C DID Core (did:nostr, did:key, did:peer, did:plc, did:web) | W3C Recommendation | Multi-method node and actor identity resolution without central registries. Emits standard DID documents with Multikey bindings. | Spec § Identity |
| DIDComm Messaging v2 | DIF Specification | Bilateral private control plane with ECDH-1PU and ECDH-ES envelope authentication across 10 owned protocols. | Spec § Control plane |
| BIP-340 Schnorr & Ed25519 Signatures | Cryptographic Standard | secp256k1 x-only keys signing descriptors, grants, receipts, and hop paths; Ed25519 for iroh, libp2p, SSB, p2panda, and RFC 9421. |
Spec § Multi-key identity |
| NIP-07, NIP-46 & NIP-98 (fleetmesh_auth SSO) | Nostr Web Auth | Passwordless browser extension challenge-response, bunker:// remote signing, and NIP-98 (kind 27235) cross-app portable passes (fmpass_...). |
Details § Subsystems |
| RFC 5869 (HKDF-SHA256) | IETF RFC Standard | Extract-and-expand key derivation for blinded pair grant (kind 30801) and compute receipt (kind 30811) identifiers. |
Spec § Blinded tags |
| FIPS 140-3 Cryptographic Boundary | Enterprise / NIST | Full cryptographic inventory showing approved symmetric layers and sovereign relay edge isolation. | Design Note: FIPS 140 |
| FIPS Native Overlay (fips-native) | Mesh Routing | Native overlay mesh routing via the fleetmesh-fips sidecar at transport ladder rank 5. |
Design Note: FIPS Peering |
| iroh (QUIC & Hole Punching) | Modern Decentralized | Direct P2P UDP streams (ALPN fleetmesh/didcomm/1, rank 10) with automatic NAT traversal and BLAKE3 verified streaming. |
Spec § Transports |
| libp2p (Gossipsub v1.1 & Circuit Relay v2) | Modern Decentralized | Swarm peer discovery via topic /fleetmesh/announce/1, Kademlia DHT, and Noise + Yamux streams (rank 20). |
Spec § Discovery |
| Secure Scuttlebutt (SHS, Box Stream & MuxRPC) | Offline-First P2P | 4-phase Curve25519/Ed25519 Secret Handshake, Box Stream encryption, MuxRPC (createHistoryStream, blobs), and SSBRung transport (rank 25). |
Spec § Ecosystem Bridges |
| NIP-59 / NIP-44 (Gift Wrap Fallback) | Nostr Protocol | Universal fallback transport (rank 100) over standard relays: kind 21059 live and kind 1059 store-and-forward envelopes. | Spec § Nostr binding |
| TLS 1.3, WebSocket (wss://) & Neutral Discovery | IETF / Web Standard | Public relay faces, POST /didcomm HTTPS binding, and optional rendezvous via wss://relay.fleetmesh.org. |
Guide: Running a Node |
| NIP-77 (Negentropy V1) | Nostr Protocol | Deterministic 16-byte range-bisection set reconciliation across SQLite (SqliteDialect) and PostgreSQL (PostgresDialect). |
Spec § Replication |
| p2panda (v0.4.0 CBOR Operation Logs) | Append-Only Bamboo Logs | Deterministic RFC 8949 CBOR operation headers with Ed25519 author keys, backlink/seq validation, log pruning, and P2PandaRung transport (rank 15). |
Spec § Ecosystem Bridges |
| Rhio & Bao (BLAKE3 Merkle Tree CAS & NATS) | Verified Streaming CAS | 1 KiB chunked Bao Merkle tree verification (RhioBaoTree), HTTP 206 Range serving, S3 CAS, NATS JetStream routing, and RhioRung transport (rank 12). |
Spec § Replication |
| AT Protocol (com.atproto.*, MST & CAR v1) | Federated Social / PDS | XRPC server, Merkle Search Trees over DAG-CBOR, CAR v1 repo slices, CIDv1 ↔ Blossom SHA-256 mapping, and Cashu-metered subscribeRepos firehose. |
Spec § Ecosystem Bridges |
| ActivityPub, WebFinger (RFC 7033) & HTTP Signatures (RFC 9421) | W3C / IETF Standard | W3C ActivityStreams 2.0 JSON-LD Inbox/Outbox federation, actor discovery, Ed25519 HTTP message verification, and StrainLedger spam shielding. |
Spec § Ecosystem Bridges |
| Blossom Media Protocol & blob/1.0 Wire | Nostr Protocol | SHA-256 content-addressed blob storage, IPFS CIDv1 (0x55) mapping, and chunk-streamed blob/1.0 replication with bilateral metering. |
Spec § Blossom |
| CMAF / LL-HLS & video-transit/1.0 (MoQ Reflection) | Live Media & Barter | Low-latency fMP4/WebM live packaging, cross-protocol addressing, p2panda segment logs, HTTP 307 load-shedding redirects, and bilateral transit work-barter. | Spec § Replication |
| NIP-5A (nsite) & NIP-34 (grasp/1.0) | Nostr Hosting | Static site gateway (kinds 15128/35128) with COOP/COEP headers, plus manifest-verified Git smart-HTTP hosting (kinds 30617/30618/1617–1633). | Spec § Ecosystem Bridges |
| OCI Containers (ncontainer/1.0) & Magpie (magpie/1.0) | OCI / Content Repository | OCI image distribution (kind 30624) backed by Blossom SHA-256 blobs and content-addressed media catalog sidecars with Cashu Paid Fetch. | Spec § Ecosystem Bridges |
| Signed Hop Delivery Envelopes & gossip/1.0 | fleetmesh Normative | Multi-hop forwarding with cryptographic hop signatures (fleetmesh/hop/1) and admin-signed (kind 30804) epidemic topic fanout. |
Spec § Delivery envelopes |
| JSON Schema (Draft 2020-12) | IETF Standard | 67 formal schemas for every event kind, DIDComm payload, manifest, and decrypted payload. | Schema Browser |
| Schema.org (v30.1 Linked Data) | W3C JSON-LD / Schema.org | Deterministic JSON-LD projections mapping descriptors, grants, reports, and compute offers to standard Schema.org types. | Schema Browser |
| AIMD Rate Windows & budget/1.0 | Internet Congestion | Load-weighted Additive Increase, Multiplicative Decrease rate control with disuse decay over bilateral relay capacity. | Spec § Window arithmetic |
| NIP-85, NIP-66 & NIP-32 Projections | Nostr Protocol | Projects relay scores (kind 30385), face capabilities (kind 30166), and moderation labels (kind 1985) to standard clients. | Spec § Projections |
| Kubernetes CRDs, Declarative YAML & Ansible Ops | Cloud Native / OCI | Declarative manifests (fleetmesh.org/v1alpha1) consumed by meshnode init --manifest, reconciled live via meshctl apply, and deployed via the ops Ansible suite. |
Spec § Operator surface |
| WASI (fleetmesh-wasi-v1 Sandbox) | Bytecode Alliance / W3C | Deterministic WebAssembly sandbox execution (Wasmtime / Wasmer) with virtualized clocks, seeded entropy, and fuel-bounded isolation. | Spec § Compute market |
| RISC Zero & SP1 zkVM + Groth16 zk-SNARKs | Zero-Knowledge Proofs | Non-interactive zero-knowledge verification for RISC-V zkVM receipts (zkvm-risc0, SP1) and Groth16 circuits over alt_bn128, plus prover delegation (zk-prove-groth16). |
Spec § Verification |
| Multi-Provider AI Inference & Streaming compute/1.1 | Distributed AI Routing | Unified LLM routing across OpenRouter, Anthropic, OpenAI, Gemini, Copilot, Routstr, vLLM, Ollama, and NIP-90 DVMs under declared verification modes. | Spec § Compute market |
| Model Context Protocol (MCP) & ReAct Agents | Agent Interoperability | McpClientBridge and McpToolAdapter exposing JSON-RPC MCP tools inside fuel-bounded multi-turn ReAct agent loops (agent-react). |
Spec § Compute market |
| Deterministic FFmpeg (media-ffmpeg) & Bacalhau | Media & Batch Compute | Bitwise-reproducible single-threaded FFmpeg media transcoding (-bitexact) and containerized compute-over-data over Blossom storage. |
Spec § Compute market |
| Bitcoin Lightning Network (BOLT11 / BOLT12 / L402) | Payment Layer | Trustless micropayment settlement for compute fuel, accountable sealed delivery, and asymmetric rate capacity. | Spec § Settlement |
| Cashu Ecash (NIP-61 / NUT-18 / NUT-24) & NWC (NIP-47) | Chaumian Ecash & Wallets | Sub-satoshi ecash settlement, HTTP 402 Paid Fetch for Blossom/ATProto/sidecars, and Nostr Wallet Connect automated payment delegation. | Spec § Settlement |
Architecture · Network Topology
fleetmesh supports heterogeneous network roles. Dedicated servers provide backbone routing, local relays peer directly over QUIC, and client applications sync lightweight shards.
Backbone mesh infrastructure. Provides DIDComm mediation for firewalled nodes, publishes regular liveness heartbeats (kind 21801), routes gossipsub topics, and maintains high-capacity bilateral grants.
Community relays. Connects to peers via direct QUIC hole punching, stores authoritative shard data (kind 30803), and participates in bilateral NIP-77 range reconciliation.
Phones and browser tabs. @fleetmesh/leaf runs the leaf in Chromium, Firefox
and WebKit: one outbound WebSocket to its mediating anchor, a bounded local store,
and no public inbound ports.
Economics · Bilateral Rate Accounting
Transfer rates are governed by published signed grants, monotonic receipt hash chains, and deterministic remedy schedules.
Remedies for protocol non-conformance follow predefined contractual actions:
| Severity | Condition | Wire Evidence | Deterministic Remedy |
|---|---|---|---|
| S0 · Drift | Traffic within 110% of limits with matching receipts. | Receipt hash chain links. | Clean window period; limits increase along the AIMD schedule. |
| S1 · Overrun | Volume 10–100% over the limit, accurately reported. | Signed receipts referencing the grant. | Capacity halved; private notification sent over complaint/1.0. |
| S2 · Misreport | Double the limit or more, receipts more than 10% off measured traffic, or traffic with no receipt at all. | Divergent signed receipts or traffic logs. | Limit cut to a quarter and peer moved to probation. A private complaint/1.0 notice and one window come before the public report (kind 30802); traffic with no receipt gets no public report, because there is no signed evidence to cite. |
| S3 · Abuse | Five times the limit or more, traffic outside granted shard filters, or malformed frames. | Malformed envelopes or out-of-filter events. | Limits at zero for 24 hours, then probation; adverse kind 30802 may be published at once, with evidence. |
| S4 · Malice | Invalid signatures, corrupted hash chains, or identity spoofing. | Cryptographic signature verification failure. | Peering revoked; active grants deleted; permanent adverse attestation recorded. |
Compute & Media · Execution Fabric, AI Routing & Video Transit
Nodes exchange compute requests and live video transit grants over private DIDComm channels, settling through Bitcoin Lightning (L402/BOLT11/BOLT12), Cashu ecash, or bilateral work-barter.
Compute asks (kind 30810) specify fuel limits, target runtime engines, and bid prices.
Payloads and execution parameters are encrypted end-to-end between client and executor over compute/1.0 and streamed over compute/1.1.
Job receipts (kind 30811) use blinded identifiers to maintain confidential execution records.
zk-verify-groth16 (over alt_bn128), zk-prove-groth16 prover delegation, and zkvm-risc0 / SP1 receipt verification.agent-react) with Model Context Protocol (McpClientBridge) tool execution.media-ffmpeg transcoding, CMAF/LL-HLS live segmentation, and video-transit/1.0 reflection with work-barter.Compute asks specify an agreed verification mode prior to job execution:
proof
Zero-Knowledge Verification: Groth16 or RISC Zero / SP1 zkVM proof validated against public input digests.
schema-bounds
Syntactic Grammar: Output validated against Draft 2020-12 JSON Schema or grammar rules.
tee-attestation
Hardware Enclave: Hardware signature (NVIDIA CC, AMD SEV-SNP) over model, inputs, and outputs.
quasi-deterministic
Multi-Executor Consensus: Greedy T=0 decoding compared across a 2-of-3 executor quorum.
delivery
Accountable Sealing: Preimage delivery verification with out-of-band evaluation.
Roadmap · Completed & Upcoming Phases
fleetmesh progresses through structured engineering phases. Ten foundational phases are completed and verified across 523 conformance cases; two upcoming phases target cross-protocol semantic translation and live public federation.
NIP-77 range-bisection synchronization across SqliteDialect and PostgresDialect with multi-replica store_lease coordination and causal graph projections (ProjectedNodeStore).
Strict gateway boundary architecture with dedicated key namespaces, pluginIn/pluginOut policy seams, strfry-bridge egress enforcement, and automated unplug tests.
W3C DID Core (did:nostr, did:key, did:peer, did:plc, did:web), kind 11801 multi-key descriptors, kind 11802 revocations, and fleetmesh_auth NIP-07/46/98 SSO & portable passes.
DIDComm Messaging v2 with ECDH-1PU/ECDH-ES across 10 owned protocols, NIP-59 gift-wrap fallback, mediator routing, and neutral rendezvous via wss://relay.fleetmesh.org.
Kind 30801 blinded budgets, monotonic receipt hash chains (budget/1.0), load-weighted AIMD schedules, the S0–S4 Severity Ladder, and Cashu NUT-18/NUT-24 HTTP 402 Paid Fetch.
Pluggable ProtocolPackage & ProtocolHostRouter for Nostr, AT Protocol, ActivityPub, Secure Scuttlebutt, p2panda, and Rhio/Bao across the 7-rung transport ladder (fips-native, iroh, rhio, p2panda, libp2p, ssb, nostr).
Python meshnode daemon, Rust meshctl CLI (523/523 conformance cases across 111 ops in all 6 planes), ops Ansible roles, npack distribution, and grasp/ncontainer/magpie sidecar gateways.
@fleetmesh/leaf 0.1.0 in TypeScript: zero-inbound-port mediated leaf with IndexedDB storage, Web Locks tab coordination, NIP-77 sync, and live browser E2E verification across Chromium, Firefox, and WebKit.
Deterministic fleetmesh-wasi-v1 runtime, Groth16 & RISC Zero/SP1 zkVM verification, deterministic media-ffmpeg transcoding, CMAF/LL-HLS live packaging, and video-transit/1.0 reflection with work-barter.
Unified LLM router (OpenRouter, Anthropic, OpenAI, Gemini, Copilot, Routstr, vLLM, Ollama), streaming compute/1.1, and fuel-bounded ReAct agents with Model Context Protocol (MCP) tool bridges.
Automated bidirectional content and social graph translation across Nostr events, AT Protocol Lexicon records, ActivityPub objects, SSB messages, and p2panda logs with provenance-preserving signatures.
fleetmesh/0)Live 2-of-3 quasi-deterministic multi-executor arbitration for non-deterministic AI disputes, per-step streaming agent escrow, and multi-operator public mesh stress testing to freeze fleetmesh/0.
Tooling · Operator & Developer Suite
Tools to deploy, peer, test, monitor, and settle network nodes.
The reference implementation runs under Python 3.10 or newer; its one runtime dependency is the cryptography package.
Kubernetes-style resources under apiVersion: fleetmesh.org/v1alpha1: MeshNode, Peering, GrantPolicy, ComputeProvider, InferenceRouter. Schema-checked against the normative constants and consumed by meshnode init. The standalone meshctl CLI (built in Rust) provides production declarative manifest management, non-destructive hot-reconciliation, and multi-target compilation.
meshnode init --manifest meshnode.yaml
The core 43-subcommand daemon in fleetmesh_node/. Manages keys, relay endpoints, rate windows, peering grants, and the local UNIX control socket.
python3 -m fleetmesh_node.meshnode --help
Autonomous monitoring tool, meshctl watch (Rust, from the meshctl repository). Audits connections, storage integrity, and rate limits, returning exit codes 0, 1, or 2 for monitoring systems.
meshctl watch
Bidirectional bridge in fleetmesh_node/planes/transport/bridge/compartment.py connecting the mesh with standard Nostr relays. Routes topic shards and backfills historical events.
meshnode bridge sync --relay ...
Local testnet simulator in fleetmesh_node/testnet/cluster.py. Launches multi-node topologies to validate synchronization and peering.
meshnode cluster start --nodes 5
Payment daemon in fleetmesh_node/settlement/. Manages escrows, Cashu NUT-18/NUT-24 Paid Fetch, and micropayments across Bitcoin Lightning, Cashu ecash, and Nostr Wallet Connect.
meshnode settle nwc-pay --amount 5000
Pluggable protocol suite in fleetmesh_node/protocols/base.py hosting Nostr, AT Protocol, ActivityPub, Secure Scuttlebutt, p2panda, and Rhio/Bao on one node with hostname and path routing.
protocols.enabled: [nostr, atproto, activitypub, ssb, p2panda, rhio]
CMAF/LL-HLS & WebM live segmenter and MoQ reflector in fleetmesh_node/planes/services/video/compartment.py. Negotiates video-transit/1.0 bandwidth grants, HTTP 307 load-shedding redirects, and compute-for-transit work-barter.
GET /video/<stream_id>/live.m3u8
TypeScript leaf node for Chromium, Firefox, and WebKit. Runs over a single mediated WebSocket with IndexedDB storage, Web Locks multi-tab coordination, NIP-77 range sync, and budget/1.0 receipt signing.
npm install @fleetmesh/leaf
Drop-in Python & FastAPI authentication library for NIP-07 browser signers, NIP-46 remote bunkers, and NIP-98 (kind 27235) cross-app portable passes (fmpass_...) with zero central IdP.
from fleetmesh_auth.fastapi_ext import create_auth_router
Step through live deployment commands or author declarative manifests:
# 1. Initialize node directory, keys, and self-signed descriptor
python3 -m fleetmesh_node.meshnode init /var/lib/meshnode \
--operator <your-pubkey> \
--class edge \
--relay wss://relay.example.org \
--endpoint wss=wss://mesh.example.org:443 \
--face-port 7777
Need production reverse-proxy (Caddy) and systemd daemon configurations?
Read the Operator Manual →Architecture · Design Notes & Deep Dives
Explore the reference implementation, capacity model, protocol economics, and cryptographic compliance behind fleetmesh.
Architectural overview: distributed compute, shard replication, and protocol resilience.
The 23 core reference node compartments plus up to 9 optional (p2p, gossip, compute, compute_wire, bridge, dvm, nsite, video, updates), typed contracts, SQLite storage models, wire stack, and bilateral accounting loop.
Deployment setup, reverse proxy configuration, 46 CLI commands, systemd service units, and troubleshooting checklist.
The 3-rung load-shedding ladder (Rungs 0–2) and directional strain ledger to maintain reliability under load.
Rosters (kind 30830), join policies, roster-protected relays, capability grant chains, revocation, and how a node enrols in a fleet.
Why fleetmesh settles discrete retrieval requests rather than charging continuous storage rent.
How published budgets and receipt chains establish measurable trust weighting across the mesh.
How fleetmesh compares to the Free Internetworking Peering System (FIPS): packet routing and relay federation.
Algorithm evaluation against the NIST approved list, isolating non-approved signature curves at sovereign edges.
The fleetmesh protocol rendered in ten glass emblems: identity, topology, replication, reputation, and compute.