Skip to content

Commit 7a42757

Browse files
committed
Add missing message on dispute
1 parent fa9705c commit 7a42757

2 files changed

Lines changed: 22 additions & 2 deletions

File tree

src/dispute.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,26 @@ Mostro will send a confirmation message to the admin with the order details:
122122
}
123123
```
124124

125+
Then mostrod send messages to each trade participat, the buyer and seller for them to know the pubkey of the admin who took the dispute, that way the client can start listening events from that specific pubkey, by default clients should discard any messages received from any pubkey different than Mostro node or dispute solver, the message looks like this:
126+
127+
```json
128+
[
129+
{
130+
"order": {
131+
"version": 1,
132+
"id": "<Order Id>",
133+
"action": "admin-took-dispute",
134+
"payload": {
135+
"peer": {
136+
"pubkey": "<Solver's pubkey>"
137+
}
138+
}
139+
}
140+
},
141+
null
142+
]
143+
```
144+
125145
Also Mostro will broadcast a new addressable dispute event to update the dispute `status` to `in-progress`:
126146

127147
```json

src/fiatsent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Mostro send messages to both parties confirming `fiat-sent` action and sending a
4141
"id": "<Order Id>",
4242
"action": "fiat-sent-ok",
4343
"payload": {
44-
"Peer": {
44+
"peer": {
4545
"pubkey": "<Seller's trade pubkey>"
4646
}
4747
}
@@ -59,7 +59,7 @@ And here an example of the message from Mostro to the seller:
5959
"pubkey": "<Seller's trade pubkey>",
6060
"action": "fiat-sent-ok",
6161
"payload": {
62-
"Peer": {
62+
"peer": {
6363
"pubkey": "<Buyer's trade pubkey>"
6464
}
6565
}

0 commit comments

Comments
 (0)