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
This is a DoS which arguably doesn't matter as the counterparty never locks their own funds and can simply kill their ASMR instance if this happens. That said, the time to decide to kill, hit Ctrl^C, and kill could theoretically overlap with the BTC actually being sent which would cause ASMR to move forward (assuming it still has a valid timelock).
If ASMR is expanded past the PoC point, this could cause issues. As of right now, even if ASMR moved forward, I believe it'll solely print an address to send the XMR to? So it's not an issue if it's killed because the user who kills won't then send to the address, if it does proceed to that point.
The text was updated successfully, but these errors were encountered:
This is a DoS which arguably doesn't matter as the counterparty never locks their own funds and can simply kill their ASMR instance if this happens. That said, the time to decide to kill, hit Ctrl^C, and kill could theoretically overlap with the BTC actually being sent which would cause ASMR to move forward (assuming it still has a valid timelock).
If ASMR is expanded past the PoC point, this could cause issues. As of right now, even if ASMR moved forward, I believe it'll solely print an address to send the XMR to? So it's not an issue if it's killed because the user who kills won't then send to the address, if it does proceed to that point.
The text was updated successfully, but these errors were encountered: