search

Raptor3um / raptoreum

MIT License
317 stars 134 forks source link

Trouble with raptoreum Core wallet version v1.3.17.01-c136d2b (64-bit) #260

Closed maccappuccino closed 7 months ago

maccappuccino commented 1 year ago

Describe the issue

Impossible to finish synchro

After 3 months without use, I restart the raptoreum core software on the windows PC because I have mined a little on it. The synchro is impossible, I try all the repairs without success. I decide to upgrade to version v1.3.17.01, it's ko, I start again with the bootstrap, after half a day I'm OK, but no luck I suffer a power cut and there no way to resume the sync. I decide to start from scratch with an empty wallet, same punishment always blocked between 90-95%. I change machine, I go on mac with an empty wallet and still the same problem no way to synchronize the raptoreum core with the blockchain.

Actual behaviour

After 3 weeks without being able to make the blockchain work I decide to contact you, it's the worst chrypto-currency experience I've ever had because I've always been able to fix the others, even the Ethereum wallet which are known to be quite a pain in the ass.

Screenshots.

image

What version of Raptoreum Core are you using?

v1.3.17.01-c136d2b (64-bit)

Machine specs:

Windows machine

MacOs machine

maccappuccino commented 1 year ago

I have alway this error (in big log debug.log):

2023-01-13T23:18:59Z ERROR: ConnectBlock(RAPTOREUM): ProcessSpecialTxsInBlock for block c5bc1145370ab9d6f83518ad25a1fbfb3d2f85bf039197a3b7ddccfeca96e9fa failed with bad-cbtx-mnmerkleroot (code 16) 2023-01-13T23:18:59Z InvalidChainFound: invalid block=c5bc1145370ab9d6f83518ad25a1fbfb3d2f85bf039197a3b7ddccfeca96e9fa height=453101 log2_work=51.97803805 date=2022-11-30T12:14:45Z 2023-01-13T23:18:59Z init message: Starting network threads... 2023-01-13T23:18:59Z InvalidChainFound: current best=ef41e11e66e9e2de57252276c0501dce413dd0059bc44929fa5a23a4f5c817e4 height=453100 log2_work=51.97803573 date=2022-11-30T12:12:37Z 2023-01-13T23:18:59Z ERROR: ConnectTip(): ConnectBlock c5bc1145370ab9d6f83518ad25a1fbfb3d2f85bf039197a3b7ddccfeca96e9fa failed with bad-cbtx-mnmerkleroot (code 16) 2023-01-13T23:18:59Z InvalidChainFound: invalid block=9a37d07bfec72fa34426f70044e3e0431da2f9fa2263416c5e101c6d601273f7 height=453132 log2_work=51.97810363 date=2022-11-30T13:18:06Z 2023-01-13T23:18:59Z InvalidChainFound: current best=ef41e11e66e9e2de57252276c0501dce413dd0059bc44929fa5a23a4f5c817e4 height=453100 log2_work=51.97803573 date=2022-11-30T12:12:37Z

maccappuccino commented 1 year ago

debug.log

Blueskys379 commented 1 year ago

Hi you need to bootstrap. Your screen shows it's not applied. You need to follow this process. If you need additional support, head to wallet channel on Discord.

How to bootstrap

On https://bootstrap.raptoreum.com/
Download the version of the bootstrap that matches your current wallet version. Use bootstrap version that matches your wallet version

maccappuccino commented 1 year ago

Thank you, I have already tried this procedure several times without success.

Blueskys379 commented 1 year ago

Make sure using correct bootstrap version, 1.3.17.00-01 for version 1.3.17.01 Also, use one of the non-indexed versions of the bootstrap and don't change the config file to turn indexing on.

maccappuccino commented 1 year ago

That's what I did! Now I try again the version 1.13.17.02 testnet and functional in mainnet but not recommended. ForeCross solved this problem with this new version of raptoreum. https://github.com/Raptor3um/raptoreum/issues/257

Le 14 janv. 2023 à 02:10, Blueskys379 @.***> a écrit :

Make sure using correct bootstrap version, 1.3.17.00-01 for version 1.3.17.01 Also, use one of the non-indexed versions of the bootstrap and don't change the config file to turn indexing on.

— Reply to this email directly, view it on GitHub https://github.com/Raptor3um/raptoreum/issues/260#issuecomment-1382619572, or unsubscribe https://github.com/notifications/unsubscribe-auth/APVEVAVEQLAI7M26O4ZT3EDWSH4JFANCNFSM6AAAAAAT26SOEI. You are receiving this because you authored the thread.

maccappuccino commented 1 year ago

Thank you, it's fixed, it worked fine! The correction had been made for the previous ticket (https://github.com/Raptor3um/raptoreum/issues/257) but the description of the workaround was missing.

Bigpiggy01 commented 1 year ago

Glad it got sorted out!