-
Notifications
You must be signed in to change notification settings - Fork 7
Docs/update dispute chat #35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+50
−33
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,49 +1,70 @@ | ||
| # Dispute Chat | ||
|
|
||
| Once an admin takes a dispute, both the admin and the involved parties (buyer and seller) can communicate through an encrypted chat using Gift Wrap messages (NIP-59). | ||
| The dispute chat uses the same shared key encryption scheme as the [Peer-to-peer Chat](./chat.md). Instead of computing a shared key between buyer and seller, each party computes an independent shared key with the admin who took the dispute. | ||
|
|
||
| ## Sending a message | ||
| ## Establishing the shared key | ||
|
|
||
| Users and admins send messages using action `send-dm`. The message content is wrapped in a Gift Wrap event (kind 1059) to ensure privacy and encryption. | ||
|
|
||
| ### User sending a message | ||
|
|
||
| Here is an example of a user sending a message to the admin: | ||
| When an admin takes a dispute, Mostro sends an `admin-took-dispute` message to each party (buyer and seller) containing the admin's pubkey: | ||
|
|
||
| ```json | ||
| [ | ||
| { | ||
| "dm": { | ||
| "order": { | ||
| "version": 1, | ||
| "action": "send-dm", | ||
| "id": "<Order Id>", | ||
| "action": "admin-took-dispute", | ||
| "payload": { | ||
| "text_message": "Hello, I need help with this order" | ||
| "peer": { | ||
| "pubkey": "<Admin's pubkey>" | ||
| } | ||
| } | ||
| } | ||
| }, | ||
| null | ||
| ] | ||
| ``` | ||
|
|
||
| ### Admin sending a message | ||
| Upon receiving this message, the client computes the shared key using ECDH: | ||
|
|
||
| Admins use the same format to send messages to users: | ||
| ``` | ||
| Shared Key = ECDH(tradeKey.private, adminPubkey) | ||
| ``` | ||
|
|
||
| The admin computes the same shared key from their side: | ||
|
|
||
| ``` | ||
| Shared Key = ECDH(adminPrivateKey, tradeKey.public) | ||
| ``` | ||
|
|
||
| Each party (buyer and seller) has its own independent shared key with the admin. A session can have both a peer shared key (for the P2P chat) and an admin shared key (for the dispute chat) simultaneously. | ||
|
|
||
| ## Sending and receiving messages | ||
|
|
||
| Messages are wrapped and unwrapped using the same simplified NIP-59 scheme described in [Peer-to-peer Chat](./chat.md#example). The inner event is a kind 1 event signed by the sender's key, encrypted with NIP-44 and placed inside a kind 1059 Gift Wrap event. | ||
|
|
||
| The `p` tag in the wrapper event points to the **admin shared key's pubkey**, not the trade key: | ||
|
|
||
| ```json | ||
| [ | ||
| { | ||
| "dm": { | ||
| "version": 1, | ||
| "action": "send-dm", | ||
| "payload": { | ||
| "text_message": "I'm reviewing the evidence, please wait" | ||
| } | ||
| } | ||
| }, | ||
| null | ||
| ] | ||
| { | ||
| "content": "<Encrypted content>", | ||
| "kind": 1059, | ||
| "created_at": 1703021488, | ||
| "pubkey": "<Ephemeral pubkey>", | ||
| "id": "<Event Id>", | ||
| "sig": "<Ephemeral key signature>", | ||
| "tags": [["p", "<Admin Shared Pubkey>"]] | ||
| } | ||
| ``` | ||
|
|
||
| ## Receiving messages | ||
| ## Subscribing to messages | ||
|
|
||
| Clients subscribe to kind 1059 events filtered by the admin shared key's pubkey: | ||
|
|
||
| ```json | ||
| { | ||
| "kinds": [1059], | ||
| "#p": ["<Admin Shared Pubkey>"] | ||
| } | ||
| ``` | ||
|
|
||
| Clients must subscribe to kind 1059 events with a `p` tag matching their pubkey. The Gift Wrap protocol (NIP-59) ensures that only the intended recipient can decrypt and read the messages, while preserving the sender's identity through the SEAL layer | ||
| Clients should discard any messages received from pubkeys other than the Mostro node or the dispute solver. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.