Skip to content

Commit

Permalink
[DOC] Remove nip33 references (#347)
Browse files Browse the repository at this point in the history
  • Loading branch information
@grunch
grunch authored Aug 29, 2024
1 parent 7e791c5 commit 11f65c7
Show file tree
Hide file tree
Showing 12 changed files with 27 additions and 27 deletions.
6 changes: 3 additions & 3 deletions book/src/admin_cancel_order.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,9 @@ Mostro will send this message to the both parties buyer/seller and to the admin:
}
```

## Mostro updates nip 33 events
## Mostro updates parameterized replaceable events

Mostro will publish two nip33 messages, one for the order to update the status to `canceled-by-admin`, this means that the hold invoice was canceled and the seller's funds were returned:
Mostro will publish two parameterized replaceable events, one for the order to update the status to `canceled-by-admin`, this means that the hold invoice was canceled and the seller's funds were returned:

```json
[
Expand Down Expand Up @@ -61,7 +61,7 @@ Mostro will publish two nip33 messages, one for the order to update the status t
]
```

And updates nip33 dispute event with status `seller-refunded`:
And updates parameterized replaceable dispute event with status `seller-refunded`:

```json
[
Expand Down
8 changes: 4 additions & 4 deletions book/src/admin_settle_order.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,9 @@ Mostro will send this message to the both parties buyer/seller and to the admin:
}
```

## Mostro updates nip 33 events
## Mostro updates parameterized replaceable events

Mostro will publish two nip33 messages, one for the order to update the status to `settled-by-admin`, this means that the hold invoice paid by the seller was settled:
Mostro will publish two parameterized replaceable messages, one for the order to update the status to `settled-by-admin`, this means that the hold invoice paid by the seller was settled:

```json
[
Expand Down Expand Up @@ -61,7 +61,7 @@ Mostro will publish two nip33 messages, one for the order to update the status t
]
```

And updates nip33 dispute event with status `settled`:
And updates parameterized replaceable dispute event with status `settled`:

```json
[
Expand All @@ -86,7 +86,7 @@ And updates nip33 dispute event with status `settled`:

## Payment of the buyer's invoice

At this point Mostro is trying to pay the buyer's invoice, right after complete the payment Mostro will update the status of the order nip33 event to `success`:
At this point Mostro is trying to pay the buyer's invoice, right after complete the payment Mostro will update the status of the order parameterized replaceable event to `success`:

```json
[
Expand Down
4 changes: 2 additions & 2 deletions book/src/cancel.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Mostro will send a message with action `cancel` confirming the order was cancele
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `canceled`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `canceled`:

```json
[
Expand Down Expand Up @@ -106,7 +106,7 @@ And this message to the buyer:
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `cooperatively-canceled`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `cooperatively-canceled`:

```json
[
Expand Down
10 changes: 5 additions & 5 deletions book/src/dispute.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,11 +48,11 @@ And here is the message to the buyer:
}
```

Mostro will not update the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `dispute`, this is because the order is still active, the dispute is just a way to let the admins and the other party know that there is a problem with the order.
Mostro will not update the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `dispute`, this is because the order is still active, the dispute is just a way to let the admins and the other party know that there is a problem with the order.

## Mostro send a nip 33 event to show the dispute
## Mostro send a parameterized replaceable event to show the dispute

Here is an example of the nip 33 event sent by Mostro:
Here is an example of the event sent by Mostro:

```json
[
Expand Down Expand Up @@ -103,7 +103,7 @@ Mostro will send a confirmation message to the admin with the Order details:
"id": "ede61c96-4c13-4519-bf3a-dcf7f1e9d842",
"kind": "sell",
"status": "active",
"amount": 0,
"amount": 3333,
"fiat_code": "VES",
"fiat_amount": 100,
"payment_method": "face to face",
Expand All @@ -118,7 +118,7 @@ Mostro will send a confirmation message to the admin with the Order details:
}
```

Also Mostro will broadcast a new nip33 dispute event to update the Dispute `status` to `in-progress`:
Also Mostro will broadcast a new parameterized replaceable dispute event to update the Dispute `status` to `in-progress`:

```json
[
Expand Down
2 changes: 1 addition & 1 deletion book/src/fiatsent.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -68,7 +68,7 @@ And here an example of the message from Mostro to the seller:
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `fiat-sent`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `fiat-sent`:

```json
[
Expand Down
4 changes: 2 additions & 2 deletions book/src/release.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Right after seller release sats Mostro will try to pay the buyer's lightning inv
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `settled-hold-invoice`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `settled-hold-invoice`:

```json
[
Expand Down Expand Up @@ -89,7 +89,7 @@ Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d8
]
```

Seconds later Mostro will try to pay the buyer's invoice, if the payment is successful Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `success`:
Seconds later Mostro will try to pay the buyer's invoice, if the payment is successful Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `success`:

```json
[
Expand Down
4 changes: 2 additions & 2 deletions book/src/seller_pay_hold_invoice.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Mostro also send a message to the buyer, this way they can both write to each ot
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `active`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `active`:

```json
[
Expand Down Expand Up @@ -158,7 +158,7 @@ And this message to the buyer:
}
```

And updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:
And updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:

```json
[
Expand Down
6 changes: 3 additions & 3 deletions book/src/take_buy.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Mostro respond to the seller with a message with the following content:
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:
Mostro updates the event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:

```json
[
Expand Down Expand Up @@ -123,7 +123,7 @@ After seller pays the hold invoice Mostro send a message to the seller with the
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:

```json
[
Expand Down Expand Up @@ -203,7 +203,7 @@ Buyer sends the LN invoice to Mostro.

Now both parties have an `active` order and they can keep going with the trade.

Finally Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `active`:
Finally Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `active`:

```json
[
Expand Down
4 changes: 2 additions & 2 deletions book/src/take_sell.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ In order to continue the buyer needs to send a lightning network invoice to Most
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:

```json
[
Expand Down Expand Up @@ -129,7 +129,7 @@ Mostro send a nip 04 event to the buyer with a wrapped `order` in the content, i
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:

```json
[
Expand Down
2 changes: 1 addition & 1 deletion book/src/take_sell_ln_address.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Mostro send a nip 04 event to the buyer with a wrapped `order` in the content, i
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `WaitingPayment`:

```json
[
Expand Down
2 changes: 1 addition & 1 deletion book/src/take_sell_range_order.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ In order to continue the buyer needs to send a lightning network invoice to Most
}
```

Mostro updates the nip 33 event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:
Mostro updates the parameterized replaceable event with `d` tag `ede61c96-4c13-4519-bf3a-dcf7f1e9d842` to change the status to `waiting-buyer-invoice`:

```json
[
Expand Down
2 changes: 1 addition & 1 deletion book/src/user_rating.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ If Mostro received the correct message, it will send back a confirmation message
}
```

Mostro updates the nip 33 rating event, in this event the `d` tag will be the user pubkey `00000ba40c5795451705bb9c165b3af93c846894d3062a9cd7fcba090eb3bf78` and looks like this:
Mostro updates the parameterized replaceable rating event, in this event the `d` tag will be the user pubkey `00000ba40c5795451705bb9c165b3af93c846894d3062a9cd7fcba090eb3bf78` and looks like this:

```json
[
Expand Down

0 comments on commit 11f65c7

Please sign in to comment.