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
I notice that the nSequence for the input under consideration is kept inside the signed data. Interesting to consider the implications for Eltoo:
If nSequence is signed, then the 10 OP_CSV in the Eltoo paper is unnecessary since both of the settlement signatures will be already enforcing a specific maturation delay using BIP68.
If nSequence is unsigned, then the 10 OP_CSV is needed. But, perhaps leaving nSequence unsigned opens the door for more flexibility in other smart contract schemes.