nlocktime Electrum issue/help

[jackg]

  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.

[krogoth]

At 710pm...no luck in broadcast...tried around 8 and all went well!

https://blockchair.com/bitcoin/transaction/7b2dc71b40eabcb593cc65b1578d4af23edfa765023344cfaa7ee59a044dcfec

[ranochigo]

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.

[Abdussamad]

yeah bitcoin is a very expensive clock.

[LoyceV]

If it helps: I've only tried locktime with coinb.in, not with Electrum.

[krogothmanhattan]

If it helps: I've only tried locktime with coinb.in, not with Electrum.

 Thanks Loyce...problem if there was any has been solved.