mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-11-10 06:09:08 -05:00
add motivation
This commit is contained in:
parent
a98977d2be
commit
87912244bf
18
55.md
18
55.md
|
@ -1,4 +1,12 @@
|
||||||
# NIP-55 - Unix Domain Socket Communication
|
NIP-55
|
||||||
|
======
|
||||||
|
|
||||||
|
Unix Domain Socket Communication
|
||||||
|
--------------------------------
|
||||||
|
|
||||||
|
`optional`
|
||||||
|
|
||||||
|
For the purpose of this NIP, we will define a standard way to communicate via Unix Domain Sockets (UDS). UDS is a way to communicate between processes on the same machine. This NIP will define a standard way to communicate between the client and the server.
|
||||||
|
|
||||||
## Defining the file path for UDS
|
## Defining the file path for UDS
|
||||||
|
|
||||||
|
@ -8,4 +16,10 @@ The file path will be chosen as `/tmp/nip55`
|
||||||
|
|
||||||
## Communication
|
## Communication
|
||||||
|
|
||||||
There are potentially many ways to communicate over this socket, one way would be the JSON-RPC collection found in NIP-46.
|
Communications over this socket will be done via the JSON-RPC collection found in NIP-46. This will allow for a standard way to communicate between the client and the server.
|
||||||
|
|
||||||
|
## Motivation
|
||||||
|
|
||||||
|
Managing private keys across multiple applications can be tedious and insecure.
|
||||||
|
|
||||||
|
By centralizing key management, users can store their private keys in a single, secure application. This key management application will handle all signing requests from other applications via UDS, ensuring that private keys are never exposed to individual applications.
|
||||||
|
|
Loading…
Reference in New Issue
Block a user