2. Nostr Event Kinds Registry
Fleetmesh utilizes Nostr (NIP-01) as its decentralized event dissemination and discovery substrate. Every event published or routed by a Fleetmesh node belongs to a standardized kind registered in schema/kinds.json.
2.1. Event Kind Classifications
Nostr defines four distinct event lifecycles:
Regular (1000–9999): Stored permanently; historic events are retained.
Replaceable (10000–19999): Only the latest event per author (
pubkey) is retained by relays and eventstores.Ephemeral (20000–29999): Not stored permanently; forwarded in real-time to active subscribers.
Parameterized Replaceable (30000–39999): Only the latest event per
(pubkey, d)coordinate is retained.
2.2. Registered Fleetmesh Event Kinds
Kind |
Name |
Class |
Description & Key Tags |
|---|---|---|---|
|
Node Descriptor |
Replaceable |
Advertises node capabilities ( |
|
Node Revocation |
Replaceable |
Revokes a compromised or decommissioned node identity. Required tag: |
|
Compute Offer |
Replaceable |
Advertises verifiable and non-deterministic compute capabilities (Wasm, ZK-SNARKs, Bacalhau, LLM). Required tags: |
|
Node Heartbeat |
Ephemeral |
Broadcasts liveness telemetry without per-peer attribution. Required tag: |
|
Diagnostic Telemetry |
Ephemeral |
Opt-in coarse-binned node-wide diagnostic counters over a sample window. Required tag: |
|
Peer Grant Envelope |
Addressable |
Blinded bilateral peering capacity grant encrypted to the subject with NIP-44 v2. Required tags: |
|
Conformance Report |
Addressable |
Adverse-only divergence report (outcomes |
|
Coverage Claim |
Addressable |
Attests shard event coverage ( |
|
Gossip Topic Membership |
Addressable |
Admin-signed roster of authorized member pubkeys for a |
|
Compute Ask |
Addressable |
Order-book entry requesting compute execution with a pre-bound workload commitment. Required tags: |
|
Job Receipt |
Addressable |
Blinded compute execution receipt encrypted to the buyer with NIP-44 v2 (or cleartext with buyer consent). Required tags: |
2.3. Kind 11801: Node Descriptor Specification
The Node Descriptor is the cornerstone of network discovery in Fleetmesh.
2.3.3. Example Node Descriptor Event
{
"kind": 11801,
"pubkey": "d4e2a7b8c9f1...",
"created_at": 1791835000,
"tags": [
["class", "anchor"],
["protocol", "fleetmesh/0.1-draft"],
["c", "peering/1.0"],
["c", "budget/1.0"],
["c", "blob/1.0"],
["c", "grasp/1.0"],
["endpoint", "iroh://z6Mkh...198.51.100.10:11801"],
["endpoint", "wss://node-1.fleetmesh.org/relay"],
["mint", "https://mint.fleetmesh.org"],
["price", "fetch", "100", "msat"],
["grasp-endpoint", "https://git.fleetmesh.org"],
["expiration", "1791921400"]
],
"content": "Fleetmesh Tier-1 Anchor Node (Bristol Core)",
"id": "7a3f8b91...",
"sig": "e5c2b09a..."
}