Mermaid diagrams

[bilthon]

I've mapped the set of states that each party follows in the happy case. This is similar to what's described in https://mostro.network, but a different version for each of the following situations:

• Buyer as the taker
• Buyer as the maker
• Seller as the taker
• Seller as the maker

The "states" are the different values for the status attribute that an order can assume. The transitions are depicted by a solid line if this the state transition was caused by the something the current user has triggered. A dashed line indicates that something other than the user has triggered the state transition.

An event of kind 4 with an action mediating the state transition is sometimes delivered. For some other cases we can detect this just by the events of kind 30000.

The idea here is to lay out a visualization of all states and state transitions from all possible perspectives in order to make things more clear and maybe suggest changes that would make things more homogeneous. For instance one thing that can be noticed is that the final state of some orders is Success while others end in SettledHoldInvoice.

Buyer as the taker

flowchart TB
    p[Pending] -- TakeSell --> wbi[WaitingBuyerInvoice]
    wbi[WaitingBuyerInvoice] -- AddInvoice --> wp[WaitingPayment]
    wp[WaitingPayment] -. HoldInvoicePaymentAccepted .-> a[Active]
    a[Active] -- FiatSent --> f[FiatSent]
    f[FiatSent] -. Release .-> shi[SettledHodlInvoice]
    shi[SettledHodlInvoice] -. PurchaseCompleted .-> s[Success]

Loading

Notes: After I send a message with the action AddInvoice I get a DM with the action WaitingSellerToPay. That action is kind of like an ACK to my AddInvoice. And because we're just listing actions that produce state changes here, that is not mapped.

Buyer as the maker

flowchart TB
    p[Pending] -. WaitingSellerToPay .-> wp[WaitingPayment]
    wp[WaitingPayment] -. AddInvoice .-> wbi[WaitingBuyerInvoice]
    wbi[WaitingBuyerInvoice] -- AddInvoice --> a[Active]
    a[Active] -- FiatSent --> f[FiatSent]
    f[FiatSent] -. Release .-> shi[SettledHodlInvoice]
    shi[SettledHodlInvoice] -. PurchaseCompleted .-> s[Success]

Loading

Similarly to the case above, an event with action HoldInvoicePaymentAccepted is delivered as some kind of ACK to the AddInvoice created by the buyer.

Seller as the taker

flowchart TB
    p[Pending] -- TakeBuy --> wp[WaitingPayment]
    wp[WaitingPayment] -. WaitingBuyerInvoice .-> wbi[WaitingBuyerInvoice]
    wbi[WaitingBuyerInvoice] -. BuyerTookOrder .-> a[Active]
    a[Active] -. FiatSent .-> f[FiatSent]
    f[FiatSent] -- Release --> shi[SettledHoldInvoice]

Loading

Seller as the maker

flowchart TB
    p[Pending] .-> wbi[WaitingBuyerInvoice]
    wbi[WaitingBuyerInvoice] -. PayInvoice .-> wp[WaitingPayment]
    wp[WaitingPayment] -. BuyerTookOrder .-> a[Active]
    a[Active] -. FiatSent .-> f[FiatSent]
    f[FiatSent] -- Release --> shi[SettledHoldInvoice]

Loading

Notes: Strangely here, just an event of kind 30000 is delivered to the seller. The buyer will receive a DM with the AddInvoice action, but on the side of the seller only an order update in the form of an event of kind 30000 is received.