For developers

Build the mesh into your client

The mesh address is one new entry form, fipsmesh://<npub>/, in lists you already use: the media server list (kind:10063) and, later, the relay list (kind:10002). No new event kinds. Requests are plain Blossom GET /<sha256>, with the same hash check.

A client that doesn't know the form skips it and carries on with the other servers in the list. A client that does can ask the device for the photo by its fingerprint, the same way it asks any media server, and throws the photo away if the fingerprint doesn't match.

Draft, not yet submitted

NIP-F1: Nostr over the FIPS Mesh

The address form, transport, safety rules for serving and reading, and where Nostr Vault implements each part.

Read the draft →

How it works for people using the app is on The mesh.