I create a transaction in my regtest enviroment with OP_CHECKLOCKTIMEVERIFY it's my transaction data:

  "txid": "55bfb3b57ad2fe3d3c70d5696e3a7cd0fd4e25c8bf41d7bfa3ab57a457b31776",
  "hash": "55bfb3b57ad2fe3d3c70d5696e3a7cd0fd4e25c8bf41d7bfa3ab57a457b31776",
  "version": 2,
  "size": 223,
  "vsize": 223,
  "weight": 892,
  "locktime": 1591344300,
  "vin": [
      "txid": "f7abaa72e71a823fed9cb715aad4026918acd9aa67d3245b7cafa422034149b9",
      "vout": 0,
      "scriptSig": {
        "asm": "3045022100ded7ee34b12e829a0957a852049546ff909d33129c8c1d3769db227cafffcbdd022033b1e9ed37682470b77450d791c8b5dde67f4de2d14b772d2bbcfbe22b3a453b[ALL] 03f99b855c961eb142cc237d37db22ae67b4a80f2d2f178762110087c1e54f90c5 76a914d1d03865cf22d10d9d1ed68889be6bc99513cd6d88ac",
        "hex": "483045022100ded7ee34b12e829a0957a852049546ff909d33129c8c1d3769db227cafffcbdd022033b1e9ed37682470b77450d791c8b5dde67f4de2d14b772d2bbcfbe22b3a453b012103f99b855c961eb142cc237d37db22ae67b4a80f2d2f178762110087c1e54f90c51976a914d1d03865cf22d10d9d1ed68889be6bc99513cd6d88ac"
      "sequence": 4294967294
  "vout": [
      "value": 49.991,
      "n": 0,
      "scriptPubKey": {
        "asm": "1591344300 OP_CHECKLOCKTIMEVERIFY OP_DROP OP_HASH160 1a759e10e92cd4d855ba8bee9cd4f4a276033d10 OP_EQUAL",
        "hex": "04acfcd95eb175a9141a759e10e92cd4d855ba8bee9cd4f4a276033d1087",
        "type": "nonstandard"

Is it normal that If I use OP_CHECKLOCKTIMEVERIFY I get a non standard transaction? I'm able to relay it if I change acceptnonstdtxn=1 but it is not my purpose.

1 Answer 1


You should create a P2SH address containing the hash of that script, and when you want to spend, you can spend from that P2SH address. This'll make your transactions standard.

  • thanks for quickly answer. is It for security reason? I have some difficulties to understand How CLTV works. The sender (A) send 49 btc to recipient (B) and A want to lock the amount for 1 month. A asks to B, Can you create an address with this kind of Timelock?
    – monkeyUser
    Commented May 6, 2020 at 15:23
  • 1
    All vout scripts that are not P2PK, P2PKH, P2SH, some RETURN, or up to 3 CHECKMULTISIGVERIFY are nonstandard. All scripts not in this category need to be wrapped in P2SH.
    – MCCCS
    Commented May 6, 2020 at 15:30
  • 1
    As you can see from here and here and here
    – MCCCS
    Commented May 6, 2020 at 15:34
  • To create a standard transaction I have to use at least 1-3? Because right now the sender is P2SH-P2PKH and the receiver is P2SH 1-1. The scenario of A and B (previous comment) remains? A needs ask to B, can you create this kind of address to Lock my transaction until 1 Jan (for example)
    – monkeyUser
    Commented May 6, 2020 at 15:41
  • 1
    No, I meant if the output is a CHECKMULTISIGVERIFY it can't have more than 3 n. No, assuming who you were sending to in the original transaction was person B, your transaction's vout should be HASH160 XXXXX... EQUAL where XXXX is the hash of the script 1591344300 OP_CHECKLOCKTIMEVERIFY OP_DROP OP_HASH160 1a759e10e92cd4d855ba8bee9cd4f4a276033d10 OP_EQUAL and you should share this script with person B, and when time comes they should be able to spend from it to their address.
    – MCCCS
    Commented May 6, 2020 at 15:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.