User Tools

Site Tools


dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0065

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0065 [2021/07/26 17:17]
murphy
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0065 [2021/07/27 11:35] (current)
murphy
Line 33: Line 33:
 //​Otherwise,​ script execution will continue as if a NOP had been executed.// //​Otherwise,​ script execution will continue as if a NOP had been executed.//
  
-//The nLockTime field in a transaction prevents the transaction from being mined until either a certain block height, or block time, has been reached. By comparing the [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​argument|argument]] to CHECKLOCKTIMEVERIFY against the nLockTime field, we indirectly verify that the desired block height or block time has been reached; until that block height or block time has been reached the transaction output remains unspendable//​+//The nLockTime field in a transaction prevents the transaction from being mined until either a certain ​[[dido:​public:​ra:​xapend:​xapend.a_glossary:​b:​block_height|block height]], or block time, has been reached. By comparing the [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​argument|argument]] to CHECKLOCKTIMEVERIFY against the nLockTime field, we indirectly verify that the desired block height or block time has been reached; until that block height or block time has been reached the transaction output remains unspendable//​
  
dido/public/ra/xapend/xapend.b_stds/defact/bitcoin/bips/bip_0065.1627334236.txt.gz · Last modified: 2021/07/26 17:17 by murphy