Damus

Recent Notes

JackTheMimic · 1w
Dude, I'm not going to argue with you suffice it to say, that's not how it works. This is not an inclient function this is a coordinated out-of-band operation. You don't just get to "set your fees." G...
Kruw profile picture
I just explained how your design lets a payjoin sender could drain the receiver's wallet. Do some research before spreading misinformation:

"In exchange for the privacy benefit, the sender has to pay more fees than a normal transaction. It is a con for the sender, but a pro for the receiver, since the receiver does not have to consolidate its coin later." - @nopara73 (coinventor of payjoin)


https://nopara73.medium.com/pay-to-endpoint-56eb05d3cac6
1
JackTheMimic · 6d
That is not a given, the reciever can obviously include fees in their input. I don't why you feel like you can talk to me like a whiney little cunt but, it's becoming pretty annoying, especially since you continue to be incorrect. I have done an asynchronous payjoin using my own server PAYING THE FE...
JackTheMimic · 1w
Dude, I'm not going to argue with you suffice it to say, that's not how it works. This is not an inclient function this is a coordinated out-of-band operation. You don't just get to "set your fees." Go read this: https://payjoin.org/docs/category/how-it-works/
JackTheMimic · 1w
You are not both inputs, therefore you only pay for your portion of the transaction.
SuiGenerisJohn · 1w
This response can be compressed to Go Fork Yourself.
Daedalus · 1w
Is it not a soft fork? Am I using the terminology wrong?
Daedalus · 1w
You're right I looked it up, I got the term wrong, optional feature not soft fork.
Ben Justman🍷 · 1w
Don't senders usually pay the fee?
JackTheMimic · 1w
No, you pay your fee portion. There's not any more data than your normal transaction.
Kevin Ravens₿erg ⚡️ ☁️ · 3w
Yeah, I want to know how to get this lower, seems to calculate in 1 sat/vbyte steps
2Pac · 3w
Thank you!