10 sats \ 20 replies \ @justin_shocknet 26 Mar \ parent \ on: Hedgehog: A protocol for asynchronous layer two bitcoin payments bitcoin
On twitter you confirmed the opposite, but even so that gets back to it not being asynchronous because the receiver being offline (without latest state) is trusting the sender to provide the promise
On twitter you confirmed the opposite
Link?
the receiver being offline (without latest state) is trusting the sender to provide the promise
If the sender doesn't send the payment info then he didn't make a payment
This seems a bit like saying "bitcoin is trusted because you haven't received anything unless someone sends it to you"
reply
If the sender doesn't send the payment info then he didn't make a payment
You're the one that brought up taking down the LNURL-W server, sure if the server goes down the payment isn't made
So calling this asynchronous is false, because you're trying to compare it to Bitcoin in where the receiver doesn't need to do anything
reply
if the server goes down the payment isn't made
True
With hedgehog, if the sender closes after sending you a payment, the payment is still available for another 2016 blocks
So calling this asynchronous is false
It sounds asynchronous to me
you're trying to compare it to Bitcoin in where the receiver doesn't need to do anything
You can compare things that are different
Hedgehog is different from bitcoin because the recipient must act within a certain amount of time
It is unlike lnurlw because he does have a certain amount of time to act after a channel closure (assuming the sender did actually send him a payment)
reply
The use of the term asynchronous seems only to serve as a distinction from other solutions as being synchronous, which is why I wanted to clarify about LNURL-W/LN
Hedgehog is different from bitcoin because the recipient must act within a certain amount of time (num blocks)
LNURL-W is different from bitcoin because the recipient must act within a certain amount of time (before the server goes down)
So its either async but not an improvement, or its an improvement but not async... seems it can't be both
reply
If those are the only two options, I prefer "improvement but not async"
reply
Then I think it'd be responsible to correct this description, lest we perpetuate a mis-understanding about how things work that'll inevitably lead people to scams
reply
I don't immediately agree with you, I have to let your reasoning marinate with me for a bit
But I will remove the word asynchronously from the github and the youtube video just in case you're right
reply
You are like the world champion in dealing with people who I'm not entirely sure are operating in good faith. Very commendable.
"asynchronous" is a term used in computer science and programming languages for ages. Asynchronous requests can time out, asynchronous payments can fail after some time, so not sure what the fuss is about. Yes, it's not final settlement until it's settled - but when did we put that in the definition of asynchronous?