You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need on-chain gas swaps for users who don't know about lightning.
We can try to accept 0-conf payments by the method of burning the whole deposit to fees, this somewhat works, but requires the feerate to be low enough so that the burned amount results in a big-enough CPFP fee increase.
Users sends a transaction of 2000 sats with all inputs confirmed at a fee of 3 sats/vB (paying ~2450 sats in total)
LP accepts the transaction and pays out the gas token
User tries to double spend the transaction by creating a tx at slighly higher fee rate, and 1-input & 1-output, paying 110 sats more, since it needs to cover the bandwidth cost (so user pays a total of 550 sats on fees, and keeps the deposit).
LP detects the attempted double-spend and proceeds to burning the whole 2000 sats deposit to miner fees to CPFP the incoming transaction, bumping the fee rate to ~10 sats/vB (2000 sats new fee + 450 sats original fee), replacing the user's attempted double-spend attempt
According to the mempool policy rules the user should now be unable to push any new double-spend through, unless paying more than 2450 sats + relay fee in total, making this uneconomical for user, in reality however this seems to not be the case, and the transaction which just pays the highest feerate is prioritized, i.e. the user is able to double-spend if he pays more than 11 sats/vB for his double spend attempt (paying ~1540 in fees in total).
The text was updated successfully, but these errors were encountered:
We need on-chain gas swaps for users who don't know about lightning.
We can try to accept 0-conf payments by the method of burning the whole deposit to fees, this somewhat works, but requires the feerate to be low enough so that the burned amount results in a big-enough CPFP fee increase.
The text was updated successfully, but these errors were encountered: