Bitcoin Stack Change is a query and reply web site for Bitcoin crypto-currency lovers. It solely takes a minute to enroll.
Anyone can ask a query
Anyone can reply
One of the best solutions are voted up and rise to the highest
Requested
Seen
33 instances
Right here Antoine stated the next:
This launched absolute timelock functionality via the
nLockTimetransaction area, which is disabled if all of the transactions inputs have annSequencethat’s0xffffffff.
I’ve a few questions:
- Is that this nonetheless a consensus rule?
- Does this imply that If I would like absolute locktime in my transaction I need to set the
nSequenceof some enter to worth !=0xffffffff? - By setting some enter nSequence worth to !=
0xffffffffwe’re enabling relative locktime (32th bit is NOT set to 1) or RBF (32th bit is ready to 1). Does it imply that my transaction, for instance, have to be RBF with a view to use absolute locktime? - If all written above is true, does this imply that by setting all nSequence to == 0xffffffff and by that disabling nLocktime and absolute timelock, we are able to additionally disable CLTV?
LeaBit is a brand new contributor to this web site. Take care in asking for clarification, commenting, and answering.
Take a look at our Code of Conduct.
2
Sure it is nonetheless a consensus rule, as it has been since 2009.
You certainly must set a minimum of one enter’s nSequence to one thing else than 0xffffffff for absolutely the timelock to be taken under consideration. See as an illustration how OP_CHECKLOCKTIMEVERIFY enforces this.
Your transaction might allow nLockTime with out enabling RBF by setting the nSequence to 0xfffffffe. RBF solely will get activated through the use of 0xfffffffd or decrease.
answered 2 hours in the past
3
