If it helps: I've only tried locktime with coinb.in, not with Electrum.
Thanks Loyce...problem if there was any has been solved.
Topic: nlocktime Electrum issue/help (Read 403 times)
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
Thanks Loyce...problem if there was any has been solved.
If it helps: I've only tried locktime with coinb.in, not with Electrum.
yeah bitcoin is a very expensive clock.
Having the transaction appear in block explorers doesn't mean that it is necessarily valid, when it comes to the timestamp. The network consensus with BIP113 is that the timestamp has to be the median of the last 11 block which means that it can deviate from the actual time by 1 hour, and that explains why your transaction couldn't broadcast at 7PM and you could at 8PM. If you're looking to do nLocktime, you should set it an hour in advance.
The fact that the blockexplorer threw a non-final error basically shows that the transaction is still behind the unix time. I'm not sure why Blockcypher accepted it but if it didn't get propagated, then their timestamps logic could be wrong.
The fact that the blockexplorer threw a non-final error basically shows that the transaction is still behind the unix time. I'm not sure why Blockcypher accepted it but if it didn't get propagated, then their timestamps logic could be wrong.
At 710pm...no luck in broadcast...tried around 8 and all went well!
https://blockchair.com/bitcoin/transaction/7b2dc71b40eabcb593cc65b1578d4af23edfa765023344cfaa7ee59a044dcfec
https://blockchair.com/bitcoin/transaction/7b2dc71b40eabcb593cc65b1578d4af23edfa765023344cfaa7ee59a044dcfec
I try to push on smartbit.com.au and I get PUSH TRANSACTION ERROR: 64: NON-FINAL
There's only 2 reasons I think this error could occur:
1. You added a space or extra character somewhere that it wasn't expecting so it couldn't parse it
2. It's just broken. I'm leaning towards the second.
3. Also was it definitely past the blockheight? The 10 minutes if you did use blockheight might be out as the 10 minutes is a targeted average.
There's also a chance the fee was too low. That seems to be a common error and a lot of nodes used to not hold.more than 20mb in their mempool (but I imagine these explorers could hold at least 128gb in their mempool without exceeding the capacity of a single ram chip.
I pushed it on blockstream now....and it really broadcast..I also see it in my wallet as well
https://blockstream.info/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007
And it shows everywhere!
But why earlier would https://live.blockcypher.com/btc/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007/
say its broadcast and it never was??
https://blockstream.info/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007
And it shows everywhere!
But why earlier would https://live.blockcypher.com/btc/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007/
say its broadcast and it never was??
So I nothing has yet arrived in my wallet from the first tx 7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007
So I looked it up on blockchain and blockchair...and it never existed as they came up with nothing!
Tried again on blockcypher and I get
Error validating transaction: Transaction with hash 7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007 already exists..
I try to push on smartbit.com.au and I get PUSH TRANSACTION ERROR: 64: NON-FINAL
So I looked it up on blockchain and blockchair...and it never existed as they came up with nothing!
Tried again on blockcypher and I get
Error validating transaction: Transaction with hash 7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007 already exists..
I try to push on smartbit.com.au and I get PUSH TRANSACTION ERROR: 64: NON-FINAL
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
Here is a 2nd one I made......my time is 4pm and I placed a 7pm timelock....so 3 hours in the future
This time it did not broadcast! So will update when I do broadcast at 7pm.
Code:
020000000156ca7e2bdb24ecc2fc1e7fc7a764edd3feeb7bb0702450fb3c471f57b8201de6000000006a47304402201fa31e2b081b05ae06273862b6b7a528565970d1b613a8420f27c05cde182d590220125ccf210c00e9f8e958d5b97649d5bc3d9ff9b960de9191771464c8144270b201210249cfee87a6f55d0bd9e2be09adc8b72e434789b87d53860d628df167eba00de1fdffffff01155d0000000000001976a914549c9f4f0f5911f080a8b6c1f3ec137afc8f823c88ac9789ff5f
Code:
Decoded Transaction
{
"addresses": [
"14kBzTFSfgbzHipBwob38RNiigLcByuRVJ",
"18iPPRURq13LgLdsNKcM2e7K5DQpsNTBvY"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 3840,
"hash": "7b2dc71b40eabcb593cc65b1578d4af23edfa765023344cfaa7ee59a044dcfec",
"inputs": [
{
"addresses": [
"14kBzTFSfgbzHipBwob38RNiigLcByuRVJ"
],
"age": 0,
"output_index": 0,
"output_value": 27669,
"prev_hash": "e61d20b8571f473cfb502470b07bebfed3ed64a7c77f1efcc2ec24db2b7eca56",
"script": "47304402201fa31e2b081b05ae06273862b6b7a528565970d1b613a8420f27c05cde182d590220125ccf210c00e9f8e958d5b97649d5bc3d9ff9b960de9191771464c8144270b201210249cfee87a6f55d0bd9e2be09adc8b72e434789b87d53860d628df167eba00de1",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 1610582423,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"18iPPRURq13LgLdsNKcM2e7K5DQpsNTBvY"
],
"script": "76a914549c9f4f0f5911f080a8b6c1f3ec137afc8f823c88ac",
"script_type": "pay-to-pubkey-hash",
"value": 23829
}
],
"preference": "low",
"received": "2021-01-13T20:57:38.181377299Z",
"relayed_by": "3.80.72.207",
"size": 191,
"total": 23829,
"ver": 2,
"vin_sz": 1,
"vout_sz": 1
}
This time it did not broadcast! So will update when I do broadcast at 7pm.
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
Ok so I made a new locktime for 240pm EST as follows...
I wanted to see if it would broadcast...and it did before the 10 minutes to broadcast arrived here
https://live.blockcypher.com/btc/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007/
Funny thing,is I do not see it in my receiving wallet yet. Perhaps after 340pm est?
I will try another one, but had to post this one..no idea what I am doing wrong..will give it a 30 min lead time this time.
Code:
020000000156ca7e2bdb24ecc2fc1e7fc7a764edd3feeb7bb0702450fb3c471f57b8201de6000000006a47304402200714987225e63727f37d8b7c38ec9e1ab4079b234ef88e49d147c5663620d32f0220158a7aa47e1e0dd93501408658f064213c740930994e06feb9431024206bb6b901210249cfee87a6f55d0bd9e2be09adc8b72e434789b87d53860d628df167eba00de1fdffffff0155680000000000001976a914549c9f4f0f5911f080a8b6c1f3ec137afc8f823c88acad5aff5f
Code:
Decode A Transaction
Decoded Transaction
{
"addresses": [
"18iPPRURq13LgLdsNKcM2e7K5DQpsNTBvY",
"14kBzTFSfgbzHipBwob38RNiigLcByuRVJ"
],
"block_height": -1,
"block_index": -1,
"confirmations": 0,
"double_spend": false,
"fees": 960,
"hash": "7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007",
"inputs": [
{
"addresses": [
"14kBzTFSfgbzHipBwob38RNiigLcByuRVJ"
],
"age": 0,
"output_index": 0,
"output_value": 27669,
"prev_hash": "e61d20b8571f473cfb502470b07bebfed3ed64a7c77f1efcc2ec24db2b7eca56",
"script": "47304402200714987225e63727f37d8b7c38ec9e1ab4079b234ef88e49d147c5663620d32f0220158a7aa47e1e0dd93501408658f064213c740930994e06feb9431024206bb6b901210249cfee87a6f55d0bd9e2be09adc8b72e434789b87d53860d628df167eba00de1",
"script_type": "pay-to-pubkey-hash",
"sequence": 4294967293
}
],
"lock_time": 1610570413,
"opt_in_rbf": true,
"outputs": [
{
"addresses": [
"18iPPRURq13LgLdsNKcM2e7K5DQpsNTBvY"
],
"script": "76a914549c9f4f0f5911f080a8b6c1f3ec137afc8f823c88ac",
"script_type": "pay-to-pubkey-hash",
"value": 26709
}
],
"preference": "low",
"received": "2021-01-13T20:30:43.6295312Z",
"relayed_by": "52.23.194.197",
"size": 191,
"total": 26709,
"ver": 2,
"vin_sz": 1,
"vout_sz": 1
}
I wanted to see if it would broadcast...and it did before the 10 minutes to broadcast arrived here
https://live.blockcypher.com/btc/tx/7fde5a833eabc42b5f90d3a5a8015372e449d6749fa090c678a2f7746b76d007/
Funny thing,is I do not see it in my receiving wallet yet. Perhaps after 340pm est?
I will try another one, but had to post this one..no idea what I am doing wrong..will give it a 30 min lead time this time.
It would appear that with the very large number of unconfirmed transactions over the last few days, that the "mempoolminfee" code got triggered... 
Note that the error you had in Electrum explicitly mentioned "mempool min fee"... and not the usual "min relay fee" etc:
Note that the error you had in Electrum explicitly mentioned "mempool min fee"... and not the usual "min relay fee" etc:
The electrum server you're sending it to wants a higher fee to be paid. Not sure why though since it says it's 2 sat per byte (maybe trying to. Help people not get transactions stuck with a custom script on that specific node).
https://statoshi.info/dashboard/db/memory-pool?panelId=3&fullscreen&from=1609918343354&to=1610523143354
So I took the raw data from electrum and went to qr.io and converted it to a qr code. Scanned and it matched the hex data perfectly. THAT problem is solved. Tomorrow will work on the time lock. Thanks again all
I also scanned qr code with qr code reader...and i get
IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
Electrum uses base43 encoding for their QR codes. It helps to save the limited space for QR codes and Electrum will decode it when you're using the desktop client to scan the QR code.IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
If you want to get it in hex format, you can just use this: https://github.com/jacoblyles/base43js. It's the only converter that I'm aware of.
Funny thing i had tried the blockheight the night before on another PC and it worked. That computer is older than this 2 month old laptop I used.
If it still doesn't work, PM me the raw TX and I'll take a look.Ok...that makes sense now..thanks for all the help. Appreciate it. Will be back home tomorrow night...hopefully will have time to create another timelock..will let you know. Thanks
I also scanned qr code with qr code reader...and i get
IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
Electrum uses base43 encoding for their QR codes. It helps to save the limited space for QR codes and Electrum will decode it when you're using the desktop client to scan the QR code.IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
If you want to get it in hex format, you can just use this: https://github.com/jacoblyles/base43js. It's the only converter that I'm aware of.
Funny thing i had tried the blockheight the night before on another PC and it worked. That computer is older than this 2 month old laptop I used.
If it still doesn't work, PM me the raw TX and I'll take a look.
I also scanned qr code with qr code reader...and i get
IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
IR50$Z8DV9UHO1YOOKBX*9NI033H28X3S-Q-5ESIZ2V5HQ-JPW18UDS691CJ+.CIE7XGACT412SAI96-*P44ZI12UYT3A28YI61ZY5722529932R0+Y4V.JPZ952*17A/X8$:-N1J:I300AA5XZ5K0N3Q*C1B3-L8F+KN2MD6:J30.PTTPU*7V0/+FDLJECPDUR1MLCMPY2Z-5G$XCF*6USTR6G$PE14$GK..V7H.6.X/X$:JMXEWJH2HP33QMX:EH6NRWAM1/1O04
Why? Is there a specific reader that will convert qr code to the original raw data?
I deleted it and tried with blockheight afterwards..same issue.
Funny thing i had tried the blockheight the night before on another PC and it worked. That computer is older than this 2 month old laptop I used.
Will try again when home. Thanks for the input all
Funny thing i had tried the blockheight the night before on another PC and it worked. That computer is older than this 2 month old laptop I used.
Will try again when home. Thanks for the input all
I tried again an hour later and still same results.
Could you try it today too? I'm wondering if there were any issued with your PC clock or with the conversion of your local time to GMT by Electrum. 1610392963 (the locktime in the picture in OP) is January 11, 2021 7:22:43 PM GMT, your picture is showing 2:22:43 PM since there is 5 hour difference and if there were any issues there (such as your clock, timezone or bug in Electrum), only 1 hour waiting wouldn't be enough.
I just tried with a block number...and I am getting same issues. Why? The deposit I placed in Electrum wallet is unconfirmed....thats the only thing I can see that might be an issue..but I doubt it 
It can't be the unconfirmed UTXO, unless it's from a local transaction but it should produce a different error for a different issue.I've tried it in v4.0.9 testnet and it got rejected when it was broadcast before the set block height (as expected).
And then waited for the next block to come (same height as nLocktime) and it was successfully sent.
Maybe it's the server's node that you're connected to?
I tried again an hour later and still same results. I am using blockheight now as an experiment and see how that goes. But I want the time lock exact not guessing what the time might be.
You'll have some inaccuracy when using unix time as nlocktime, that is by design. nLocktime uses the median time past of the 11 blocks prior to the block that includes your transaction. As such, you might have to wait up to an hour before it can be relayed. Exact timing will not be possible.Your transaction appears to be rejected with non-final. Is the nlocktime specified smaller than the current block height? The nlocktime specifies that the current block height must be strictly greater than the nlocktime. As for the decoding on transaction, I'm aware that Blockchain.com appears to be bugged and can't process the raw transaction.
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
I just tried with a block number...and I am getting same issues. Why? The deposit I placed in Electrum wallet is unconfirmed....thats the only thing I can see that might be an issue..but I doubt it
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
Could it be it's too close to the end time?
LoyceV read this.
LoyceV read this.
I tried again an hour later and still same results. I am using blockheight now as an experiment and see how that goes. But I want the time lock exact not guessing what the time might be.
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
The electrum server you're sending it to wants a higher fee to be paid. Not sure why though since it says it's 2 sat per byte (maybe trying to. Help people not get transactions stuck with a custom script on that specific node).
Ok..but why am I getting errors on the websites? I am trying to broadcast it on btc.com and also on blockchain.com
Edit..whoever gets this in the future should be able to transmit anywhere thats why I am trying outside sources
Could it be it's too close to the end time?
LoyceV read this.
LoyceV read this.
The electrum server you're sending it to wants a higher fee to be paid. Not sure why though since it says it's 2 sat per byte (maybe trying to. Help people not get transactions stuck with a custom script on that specific node).
legendary
Activity: 2520
Merit: 3238
The Stone the masons rejected was the cornerstone.
Ok. I made an Electrum nLocktime transaction for a certain date in the future instead of block heoight.....yet when the time came and past I was not able to broadcast on Electrum or on a blockchain website. Can someone please let me know what exactly is the issue? Thanks
I made a transaction timelock for the 11th January 2011 222pm
I used the following website to decode...it was the only one able to
https://btc.com/tools/tx/decode
I tried the same on https://www.blockchain.com/btc/decode-tx
And I got this error
SO when the time came and went past the broadcast..I tried and these are the results.
On btc.com
On blockchain.com Code: -26, Error: non-final
and this on electrum itself
Jump to: