From 2ace01cf1ad0a68dae6217111c9286e3de759923 Mon Sep 17 00:00:00 2001 From: Pablo Fernandez Date: Wed, 8 Oct 2025 14:34:47 +0300 Subject: [PATCH] NWC Deep Links (#1777) --- 47.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/47.md b/47.md index e1df915c..13037cb5 100644 --- a/47.md +++ b/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://...`) + +