chain stopped syncing with invalid-hogex-input
#941
Comments
|
Hi, did you recently update Litecoin Core? Please resync Litecoin Core.
…On Wed, 28 Feb 2024 at 01:11, cipig ***@***.***> wrote:
2024-02-28T01:07:43Z InvalidChainFound: invalid block=8c3c3aa5769f5bb8bda8f7018fe06d76d5511e442e9764b3117c92ce2296a2cd height=2640297 log2_work=75.995930 date=2024-02-26T23:46:05Z
2024-02-28T01:07:43Z InvalidChainFound: current best=4fe1a6c2d49df6c2d6bae2e68f1bc6a1132868310fd8b9e32e4c77daa548d967 height=2640296 log2_work=75.995927 date=2024-02-26T23:43:29Z
2024-02-28T01:07:43Z ERROR: ConnectTip: ConnectBlock 8c3c3aa5769f5bb8bda8f7018fe06d76d5511e442e9764b3117c92ce2296a2cd failed, invalid-hogex-input, First input of HogEx does not point to previous HogEx
using "version": 210202"
—
Reply to this email directly, view it on GitHub
<#941>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAT43OS443XPQWWCS5LL7JDYVZ74LAVCNFSM6AAAAABD5DTREWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE2TOOBYG4ZDGMA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
yes, i moved to a new server and recompiled from master branch, so latest version |
|
No, if you upgraded from an older version, your copy of the Litecoin
blockchain doesn’t include MWEB related data, which is required in the
latest release. You must resync.
…On Wed, 28 Feb 2024 at 01:56, cipig ***@***.***> wrote:
yes, i moved to a new server and recompiled from master branch, so latest
version
resync takes way too long... isn't there another solution? can i copy the
chain from some some other server of mine?
—
Reply to this email directly, view it on GitHub
<#941 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAT43ORCWMW6LFXHAKS7KEDYV2FFTAVCNFSM6AAAAABD5DTREWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYGA2DOMZXHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
thanks for the info |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
using
"version": 210202"The text was updated successfully, but these errors were encountered: