Karl Johan Alm [ARCHIVE] on Nostr: 📅 Original date posted:2018-03-15 📝 Original message:On Thu, Mar 15, 2018 at ...
📅 Original date posted:2018-03-15
📝 Original message:On Thu, Mar 15, 2018 at 6:43 AM, Jim Posen <jim.posen at gmail.com> wrote:
> How are scripts with OP_CLTV and OP_CSV handled by verifiers? Do they always
> succeed? Or should an nLockTime and nSequence also be included in the proof
> in a way that can be parsed out and displayed to verifiers?
Good question.. Since you don't really have the input(s), I think it's
fine to always assume sufficient time/height on CLTV/CSV checks.
> I assume any signatures in the scriptSig/witness data would have no sighash
> type?
I think it would just use the default (SIGHASH_ALL?) for simplicity.
Is there a good reason to tweak it?
-Kalle.
📝 Original message:On Thu, Mar 15, 2018 at 6:43 AM, Jim Posen <jim.posen at gmail.com> wrote:
> How are scripts with OP_CLTV and OP_CSV handled by verifiers? Do they always
> succeed? Or should an nLockTime and nSequence also be included in the proof
> in a way that can be parsed out and displayed to verifiers?
Good question.. Since you don't really have the input(s), I think it's
fine to always assume sufficient time/height on CLTV/CSV checks.
> I assume any signatures in the scriptSig/witness data would have no sighash
> type?
I think it would just use the default (SIGHASH_ALL?) for simplicity.
Is there a good reason to tweak it?
-Kalle.