1NIP-652======34Relay List Metadata5-------------------67`draft` `optional`89Defines a replaceable event using `kind:10002` to advertise relays where the user generally **writes** to and relays where the user generally **reads** mentions.1011The event MUST include a list of `r` tags with relay URLs as value and an optional `read` or `write` marker. If the marker is omitted, the relay is both **read** and **write**.1213```yaml14{15 "kind": 10002,16 "tags": [17 ["r", "wss://alicerelay.example.com"],18 ["r", "wss://brando-relay.com"],19 ["r", "wss://expensive-relay.example2.com", "write"],20 ["r", "wss://nostr-relay.example.com", "read"]21 ],22 "content": "",23 // other fields...24}25```2627When downloading events **from** a user, clients SHOULD use the **write** relays of that user.2829When downloading events **about** a user, where the user was tagged (mentioned), clients SHOULD use the user's **read** relays.3031When publishing an event, clients SHOULD:3233- Send the event to the **write** relays of the author34- Send the event to all **read** relays of each tagged user35- Send the author's `kind:10002` event to all relays the event was published to3637### Size3839Clients SHOULD guide users to keep `kind:10002` lists small (2-4 relays of each category).4041### Discoverability4243Clients SHOULD spread an author's `kind:10002` event to as many relays as viable, paying attention to relays that, at any moment, serve naturally as well-known public indexers for these relay lists (where most other clients and users are connecting to in order to publish and fetch those).