Merge b7535ed096 into 2ace01cf1a

For use with a nostr mesh network https://github.com/lnbits/nostrmesh/tree/main, but prob useful elsewhere

121.md

@@ -0,0 +1,19 @@
+NIP-121
+======
+
+Unicast event `"tags": "r"`
+-------------------------------
+
+`draft` `mandatory` `author:benarc` 
+
+`route` list of relays as a new tag `"r"`, to help create a unicast route for an events.
+
+```json
+{
+  "tags": [
+    ["r", "<csv of relay IDs>"]
+  ]
+}
+```
+
+A client receives an event with tag `"r"`, if the client received the event from a relay in the list and it has a connection with the next relay in the list, the client will pass the event to that relay.

47.md

@@ -667,3 +667,21 @@ Here are some properties that are recognized by some NWC clients:
   "sig": "31f57b369459b5306a5353aa9e03be7fbde169bc881c3233625605dd12f53548179def16b9fe1137e6465d7e4d5bb27ce81fd6e75908c46b06269f4233c845d8"
 }
 ```
+
+### Deep-links
+
+Wallet applications can register deeplinks in mobile systems to make it possible to create a linking UX that doesn't require the user scanning a QR code or pasting some code.
+
+`nostrnwc://connect` and `nostrnwc+{app_name}://connect` can be registered by wallet apps and queried by apps that want to receive an NWC pairing code.
+
+All URI parameters, MUST be URI-encoded.
+
+URI parameters:
+ * `appicon` -- URL to an icon of the client that wants to create a connection.
+ * `appname` -- Name of the client that wants to create a connection.
+ * `callback` -- URI schema the wallet should open with the connection string
+
+Once a connection has been created by the wallet, it should be returned to the client by opening the callback with the following parameters
+ * `value` -- NWC pairing code (e.g. `nostr+walletconnect://...`)
+
+