Fleetmesh fleetmesh
meshstr .org

federation spec · alpha draft · 2026-10-02

The fleetmesh Protocol

The technical specification for fleetmesh: an open, permissionless relay network. Nodes deploy across datacenter servers, single-board computers, and mobile devices without centralized dependencies or proprietary infrastructure. The architecture provides coordinated spam defense based on verified operator observations. Nodes identify via W3C DIDs and negotiate over DIDComm v2. Capacity is enforced through declared bilateral budgets and signed accounting receipts.

0-draftdeclared protocol version
3node classes
0required bootstrap hosts
11event kinds, unregistered
0private data in the mesh
3transports in alpha
4open questions
S0–S4severity classes

Outline

Ten parts, in reading order

The specification is one document split for reading. Each part stands on its own and links to the others where they touch. Read it as a single page if you would rather search or print the whole thing.

01

Overview

Protocol definition, operational incentives, and the three node classes.

Scope · Why join · Node classes
02

Boundaries & governance

Isolation boundaries between private infrastructure and the public mesh, alongside decentralized governance.

Two networks · Governance
03

Identity, discovery & transport

Cryptographic node identity, rendezvous discovery, DIDComm signaling, and wire transports.

Identity · Discovery · Control plane · Transports
04

Replication

Gossip synchronization, event filtering rules, and integration with existing relay tooling.

Replication · Prior art · Ecosystem Bridges
05

Grants & receipts

Published budget allocations, signed receipt chains, and bilateral accounting reconciliation.

Grants & receipts
06

Reputation

The five-class deterministic severity ladder, sovereign subjective weighting, and adverse-only reporting.

Severity ladder · Trust weighting
07

Compute market

Verifiable confidential compute execution, cryptographic attestations, and direct Lightning settlement.

Compute market
08

Running a node

Privacy threat modeling, adversary analysis, operator manifests, and reference implementation requirements.

Privacy rules · Attack surface · Alpha contract · Implementation · Operator surface
09

Distribution & conformance

Reproducible distribution channels, verification signatures, and test suite conformance.

Distribution · Conformance · Registration
10

Open questions

Protocol parameters under active empirical evaluation during alpha testing.

Open questions