diff --git a/book/src/admin_cancel_order.md b/book/src/admin_cancel_order.md index 6aa6e1aa..08d672cf 100644 --- a/book/src/admin_cancel_order.md +++ b/book/src/admin_cancel_order.md @@ -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 [ @@ -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 [ diff --git a/book/src/admin_settle_order.md b/book/src/admin_settle_order.md index 86f811b2..467cef2f 100644 --- a/book/src/admin_settle_order.md +++ b/book/src/admin_settle_order.md @@ -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 [ @@ -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 [ @@ -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 [ diff --git a/book/src/cancel.md b/book/src/cancel.md index 0e907abb..572523bd 100644 --- a/book/src/cancel.md +++ b/book/src/cancel.md @@ -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 [ @@ -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 [ diff --git a/book/src/dispute.md b/book/src/dispute.md index 0e3cdf18..8ac7e23d 100644 --- a/book/src/dispute.md +++ b/book/src/dispute.md @@ -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 [ @@ -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", @@ -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 [ diff --git a/book/src/fiatsent.md b/book/src/fiatsent.md index a156b6e4..ddf50d0d 100644 --- a/book/src/fiatsent.md +++ b/book/src/fiatsent.md @@ -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 [ diff --git a/book/src/release.md b/book/src/release.md index 22564774..724bd1d6 100644 --- a/book/src/release.md +++ b/book/src/release.md @@ -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 [ @@ -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 [ diff --git a/book/src/seller_pay_hold_invoice.md b/book/src/seller_pay_hold_invoice.md index 1405260e..8df73835 100644 --- a/book/src/seller_pay_hold_invoice.md +++ b/book/src/seller_pay_hold_invoice.md @@ -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 [ @@ -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 [ diff --git a/book/src/take_buy.md b/book/src/take_buy.md index 35b76256..81e510eb 100644 --- a/book/src/take_buy.md +++ b/book/src/take_buy.md @@ -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 [ @@ -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 [ @@ -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 [ diff --git a/book/src/take_sell.md b/book/src/take_sell.md index 20472ffc..33bfaed8 100644 --- a/book/src/take_sell.md +++ b/book/src/take_sell.md @@ -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 [ @@ -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 [ diff --git a/book/src/take_sell_ln_address.md b/book/src/take_sell_ln_address.md index 689436a0..85ceb0ce 100644 --- a/book/src/take_sell_ln_address.md +++ b/book/src/take_sell_ln_address.md @@ -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 [ diff --git a/book/src/take_sell_range_order.md b/book/src/take_sell_range_order.md index 1160df83..94df251e 100644 --- a/book/src/take_sell_range_order.md +++ b/book/src/take_sell_range_order.md @@ -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 [ diff --git a/book/src/user_rating.md b/book/src/user_rating.md index 601edbe1..6ec9f6c0 100644 --- a/book/src/user_rating.md +++ b/book/src/user_rating.md @@ -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 [