Rusty Russell [ARCHIVE] on Nostr: 📅 Original date posted:2015-08-02 📝 Original message: Christopher Jamthagen ...

📅 Original date posted:2015-08-02
📝 Original message:
Christopher Jamthagen <cjamthagen at gmx.com> writes:
>>> If the timestop feature would activate only when the CLTV transaction
>>> is included in a block, it would allow for a pretty serious DoS attack
>>> vector where hubs can be forced to close channels with other hubs by
>>> having the attacker, as the receiver, never reveal R and create a
>>> block-filling attack.
>
>> I don't think so. Let's say the rule is "time doesn't pass if a block
>> is full".
>
> But it would be necessary to explicitly supply the block-height at which the transaction that includes the CLTV was signed. Otherwise miners would have no other info but the block it is included in from which to count the number of full blocks to add to the expiration time of the CLTV.

No, it would increase over time. The CLTV block time and real block
time would diverge by 1 block / ~ 10 minutes every time a block is full.

It's the only sane way to do it, as you point out.

It doesn't help that we don't have a formal BIP to point at, but it's
probably a bit premature.

Hope that helps,
Rusty.