omekau on Nostr: Preface - it seems unrelated to Robosats as a platform but still worth noting from an ...

Preface - it seems unrelated to Robosats as a platform but still worth noting from an end to end user experience perspective.

I found an order to take on Robosats with Strike as the payment method. I locked up a certain amount of sats as a hold throughout this transaction and joined a chat with the seller. I confirmed the amount as it was being sent as USD but using USDT so the seller would receive just over 99% of what I was sending due to exchange fees. The problem happens when I click send but Strike shows the tx as (what we’re assuming to be) pending. Instead of the green or white font, it’s grayed out. So we’re in a tricky situation because we can’t collaborative cancel as there’s a possibility the tx send is successful. And there’s no way for me to cancel that tx to try again. And of course I don’t want to try sending another tx as then we’d be relying on trust (if the first tx is successful) which is the whole point of using robosats. I did test a $1 tx to the seller and that was successful instantly which the seller then sent back to me.

Unfortunate because it seems like RoboSats, the seller, and myself (unless I made some mistake somewhere as a first timer) are all working as we’re supposed to but the error fell in the one segment of the handshake that’s out of our control. I’ll update this thread with the outcome, at the moment we’re waiting for Strike support which I opened in the app. I also sent a message to them through Nostr and the seller sent a DM using Twitter. Fingers crossed I guess!