the downside of #[1] is not the service, but the use of hodl invoices for the bonds which locks the funds for the nodes along the route.
nostr:npub1p2psats79rypr8lpnl9t5qdekfp700x660qsgw284xvq4s09lqrqqk3m82 is amazing. If you haven't tried it yet, you should.
Discussion
Oops, you mentioned the bond hold invoice. But the same still applies, as the seller's escrow is also a hold invoice too.
it’s not the locking of the sellers nor byers liquidity that is the issue, but more the locking for the nodes routing the payment. and since nodes cannot determine whenever an invoice is a hodl invoice or not there is a bigger chance for force closing to happen.
Ah I see. I agree holding invoices could be done to attack the network, but RoboSats' use of hodl invoices is quite a ways away from being considered "malicious". This concern has actually been discussed at length in the RoboSats public chat/support groups. For a better response (I'm just a social media volunteer and not a dev and don't want to speak incorrectly), it might be best to direct this type of concern to the RoboSats Matrix public dev group chat (https://matrix.to/#/#robosats:matrix.org)
I'm sorry to redirect you 😅 please do spark the conversation on Matrix!
thanks much appreciated!