I’m making an attempt to create a timelock transaction, however I’m unable to make use of a UNIX timestamp on testnet. Nevertheless, if I take advantage of a block peak the transaction works.

After I use a block peak that’s sooner or later and broadcast the transaction, I get:

sendrawtransaction RPC error: {"code":-26,"message":"non-final"}

When the block peak is reached, the transaction goes by way of as anticipated.

After I make the locktime above 500,000,000 I get a special message:

"non-mandatory-script-verify-flag (Locktime requirement not glad)"

I’ve tried a number of completely different random timestamps from varied years (2013, 2020) and I get the identical error message. If I make the transaction with a big locktime like 400,000,000 I get the anticipated "non-final" message. It solely occurs after I go over the five hundred,000,000 minimal.

I’ve decoded each transactions, and the one noticable distinction is the locktime.

Right here is the uncooked transaction with the UNIX timestamp from 2013:

0200000001ab306f83a06f006f76695f0911fbe095d2443798f232e91e7a78e8bbf2050ec40000000088483045022100c381bfb9de6930ecb45cf2cc13581aca8c42e9f570615cabf1a631fbf137270b022026636856bbf250d169f7608abe1ab4fcba13c495ffa27ee4e821d38d626365ab012103803a5bbbe00dad7dbb29dd5f4d7883ac049bad52d78b456cda12591e26ae70241c00b17576a91450840658811828e04f5501bf3fe87f012d297bdd88acfeffffff01e4250000000000001976a914f005b469eb92525da0294247b5d0ae169efd78f588ac2e377452

Right here is the uncooked transaction with block peak:

0200000001ab306f83a06f006f76695f0911fbe095d2443798f232e91e7a78e8bbf2050ec40000000087473044022011704ab11cf526e656aaf681c9ab2c3002fd8a3982383afcad8ec46af68f099d022061c06671dcc7cf6e192c541b4692a809ea97711ed2866c004780054028cc5237012103803a5bbbe00dad7dbb29dd5f4d7883ac049bad52d78b456cda12591e26ae70241c00b17576a91450840658811828e04f5501bf3fe87f012d297bdd88acfeffffff01e4250000000000001976a914f005b469eb92525da0294247b5d0ae169efd78f588acfbb22400