From d6aa686623356e76ba2d049a09c7323f7bce3f63 Mon Sep 17 00:00:00 2001 From: steliosrammos Date: Tue, 2 Aug 2022 14:54:33 +0200 Subject: [PATCH] Update 04.md Add an optional `wallet` query param to indicate to the `LN_SERVICE` which wallet was used to authenticate. --- 04.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04.md b/04.md index 133fbf5..6a362ad 100644 --- a/04.md +++ b/04.md @@ -32,7 +32,7 @@ Later, once `LN SERVICE` receives a call at the specified `LNURL-auth` handler, - `k1` (hex encoded 32 bytes of challenge) which is going to be signed by user's `linkingPrivKey`. - optional `action` enum which can be one of four strings: `register | login | link | auth`. 2. `LN WALLET` displays a "Login" dialog which must include a domain name extracted from `LNURL` query string and `action` enum translated into human readable text if `action` query parameter was present. -3. Once accepted by user, `LN WALLET` signs `k1` on `secp256k1` using `linkingPrivKey` and DER-encodes the signature. `LN WALLET` Then issues a GET to `LN SERVICE` using `?&sig=&key=` +3. Once accepted by user, `LN WALLET` signs `k1` on `secp256k1` using `linkingPrivKey` and DER-encodes the signature. `LN WALLET` Then issues a GET to `LN SERVICE` using `?&sig=&key=`. Optionally, `LN_WALLET` can append `&wallet=` to inform `LN_SERVICE` of the wallet used to authenticate. This may be used by `LN_SERVICE` to show the user which wallets they have connected to it. 4. `LN SERVICE` responds with the following JSON once client signature is verified: ```JSON {"status": "OK"}