0
Previously I generated tx with CHECKLOCKTIMEVERIFY Here is the transaction https://tchain.btc.com/bb1415c166fd9f767c06d34d539f4b110ef4445f74a76c5ffad1ded33032e872
It lock funds before block 1442909. I create a new spend transaction.
When I trying to sign it:
bitcoin-cli -testnet signrawtransactionwithwallet "020000000172e83230d3ded1fa5f6ca7745f44f40e114b9f534dd3067c769ffd66c11514bb0000000000ffffffff01443dd200000000002676a92103e8546cfe53ca9014f6a352bc2e5c1f7cec1f5b344c73d4db3ed3b8f075d5c9ef88ac00000000"
{
"hex": "020000000172e83230d3ded1fa5f6ca7745f44f40e114b9f534dd3067c769ffd66c11514bb0000000000ffffffff01443dd200000000002676a92103e8546cfe53ca9014f6a352bc2e5c1f7cec1f5b344c73d4db3ed3b8f075d5c9ef88ac00000000",
"complete": false,
"errors": [
{
"txid": "bb1415c166fd9f767c06d34d539f4b110ef4445f74a76c5ffad1ded33032e872",
"vout": 0,
"witness": [
],
"scriptSig": "",
"sequence": 4294967295,
"error": "Locktime requirement not satisfied"
}
]
}
I got "Locktime requirement not satisfied" ? The height of blockchain now is 1,442,912
What I'm doing wrong?
1is there a reason for it? To prevent users losing funds or a protection measure for the end-user without detailed knowledge? I was wondering if there may be activities to allow more sophisticated use cases (following s.th. like a "--experimental" switch)? – pebwindkraft – 2018-11-11T09:06:08.800
No, it's just not implemented. Bitcoin Core has no idea what that script does, or how to construct a satisfying input for it. – Pieter Wuille – 2018-11-11T17:03:17.167
Is there any plan to implement this? – Nikos Kostoulas – 2019-04-08T16:08:42.217