Compare commits
9 Commits
c435441ccc
...
c65fe7b015
Author | SHA1 | Date |
---|---|---|
|
c65fe7b015 | |
|
2ace01cf1a | |
|
08a266cb3c | |
|
dee684f62e | |
|
2ffa3fac7c | |
|
907153469c | |
|
57e9e8d92f | |
|
d82b733182 | |
|
3815a6fd09 |
|
@ -0,0 +1,17 @@
|
|||
NIP-163 (DRAFT)
|
||||
======
|
||||
|
||||
`Identicon Sentinel` visual profile hash sentinel for spotting spoofs
|
||||
------------------------------------------
|
||||
|
||||
`draft` `optional`
|
||||
|
||||
Spoofing accounts on any platorm is faily easy using a profile picture, banner image and similiar NIP05.
|
||||
|
||||
`Identicon Sentinel` creates an identicon of an npub using https://github.com/laurentpayot/minidenticons, to sit alongside a profile image - to be used as a visual aid for users to easily spot spoof accounts.
|
||||
|
||||
Interopibilty is key by all using the same identicon library. https://github.com/laurentpayot/minidenticons is excellent, especially for smaller sentinel identicons.
|
||||
|
||||
Minidenticons can be easily experimented with here, just pop in an npub https://laurentpayot.github.io/minidenticons
|
||||
|
||||
Using minidenticons Ben Arc's Identicon Sentinel in a nostr client would look something like this: <img src="https://i.imgur.com/TV7YAwc.png">
|
18
47.md
18
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://...`)
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue