0 sats \ 1 reply \ @nout 29 Mar \ parent \ on: Hedgehog: A protocol for asynchronous layer two bitcoin payments bitcoin
On further thought I think my comment was not useful, so feel free to disregard.
What I meant is that the usual social tricks that apply to other solutions apply here too. As soon as you have a setup where money can be "clawed back" later, that opens multiple scam opportunities.
- Alice pays bob in person in some physical corner store, Bob has static address displayed. Alice pays, shows nice checkmark that she paid, Bob believes her and gives the produce in return. Bob doesn't claim the sats for 2 weeks because he's not technical. Alice reverts the payment. Bob notices a week after that and feels scammed.
- Alice can create scam scheme where she uses a visual proof of payment to gain social engineering leverage over Bob. Most of current "fake microsoft phone support center for seniors" scams are based on this. They make you believe that they accidentally send you extra money and ask you to return it. But you never actually received the money in the first place.
Alice can do this a lot easier by screenshotting a green checkmark and showing that to Bob
In person merchants need to, and easily can, check their own device immediately. In doing so, it can automatically secure the funds permanently against Alice's pullback by withdrawing to a "real" lightning wallet
Hedgehog is more for situations like online payments and zaps where the recipient might not get online for a few days. Once you do it should automatically secure your funds. And if you don't get the money for two weeks I am of the opinion Alice should have an opportunity to recover it
reply