Replying to Avatar Five

Thanks!

I read most of the spec.

So I understand this is a great improvement if p2p platforms unite around a common protocol (nostr) on how to do this. Seems like the spec covers most possible scenarios of a trade.

I am still wondering if a Mostro needs to hold the orderbook. I think essentially a Mostro is a P2P LN escrow. But it also handles order making/taking and DMs. I thought these functionalities could be achieved without a Mostro instance:

1. I create a maker order on *my relays*.

2. Alice finds my order (by requesting for this kind of event, possibly filtered by web of trust or pow or whatever mechanism) and takes it (publishes the taker event on nostr on my read relays) .

3. We send our trade details to a Mostro instance to its relays. Most likely the maker would decide about the specific Moatro in the order. He can only select a Mostro that has the right params for the trade (e.g. within the order amount limit)

4. Mostro instance concludes our trade the way it's described in the spec

- We can communicate via nip17 DM chat during the whole trade.

- We can rate each other and Mostros as well. Ratings are also filtered by web of trust of the logged-in user to prevent gaming reputation.

Privacy: I think gift-wrapped orders don't really _add_ to privacy because they are publicly available in reality. Anyone can download the order book from a Mostro. I Iike the ephemeral nostr key option though.

Overall I just still don't see the purpose why Mostro-s must handle so much and be middle-men for the non-financial part of the trade.

Can you explain why you made this decision or misconceptions in my understanding? Many thanks!

Testing zaps on this note… we made seven attempts to⚡zap this note, at five@npub.cash, over a period of 1 day. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 2931ms (2.9 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.

Reply to this note

Please Login to reply.

Discussion

No replies yet.