Quote from: truecry on August 21, 2018, 01:44:34 PM

Quote from: brakmic on August 21, 2018, 07:22:48 AM

But, we are not here to discuss how we have to talk to our users. Until now every user that had problems with syncing the chain could solve this problem by following the solution I gave you:

a) delete everything in .actinium folder except your wallet.dat (not even Actinium.conf should remain there).

Done

Quote from: brakmic on August 21, 2018, 07:22:48 AM

b) Start the Daemon with the flags -daemon -server -txindex -reindex -port=4334 -rpcport=2300 -rpcuser=user1 -rpcpassword=blah -rpcallowip=127.0.0.1

Done

Quote from: brakmic on August 21, 2018, 07:22:48 AM

c) Wait for the sync to complete (you can run tail -f $HOME/.actinium/debug.log to watch the sync)

Code:

2018-08-20 07:41:58 UpdateTip: new best=157ae2747c02ea67ebd21fcd16efd3f0ce1dd4a306f106e20ee7971105a6f510 height=64516 version=0x60000000 log2_work=59.373545 tx=76017 date='2018-08-03 11:03:48' progress=0.839189 cache=13.3MiB(102548txo)
2018-08-20 07:41:58 UpdateTip: new best=8997d42b7d6a098984d455bd2c7b0b2ad797c59e31f04423c96ce208e9e1d65d height=64517 version=0x60000000 log2_work=59.373546 tx=76018 date='2018-08-03 11:05:55' progress=0.839202 cache=13.3MiB(102549txo)
2018-08-20 07:41:58 UpdateTip: new best=42682530d0db8b6de2eac6da7a0ce8f606ead1f0330de2ee9ccf9f8f66fdefb9 height=64518 version=0x60000000 log2_work=59.373546 tx=76019 date='2018-08-03 11:06:58' progress=0.839210 cache=13.3MiB(102550txo)
2018-08-20 07:41:58 UpdateTip: new best=a9db26b1a2b69b5ebb7d611002ff147f541a0086482c2590a2ddcbe874e054a1 height=64519 version=0x60000000 log2_work=59.373547 tx=76020 date='2018-08-03 11:08:01' progress=0.839218 cache=13.3MiB(102551txo)
2018-08-20 07:41:58 UpdateTip: new best=b310c459e0d09caa49eafe455a4659641ac99fb6bce3993dd13e77a5e58c5c77 height=64520 version=0x60000000 log2_work=59.373547 tx=76021 date='2018-08-03 11:09:47' progress=0.839229 cache=13.3MiB(102552txo)
2018-08-20 07:41:58 UpdateTip: new best=57246d84152fe24e61b76e70256bc3ec49d9f6750536dd0ca06a5d4dfd705ff5 height=64521 version=0x60000000 log2_work=59.373548 tx=76022 date='2018-08-03 11:12:14' progress=0.839245 cache=13.3MiB(102553txo)
Actiniumd: script/interpreter.cpp:1551: size_t CountWitnessSigOps(const CScript&, const CScript&, const CScriptWitness*, unsigned int): Assertion `(flags & SCRIPT_VERIFY_P2SH) != 0' failed.

Quote from: brakmic on August 21, 2018, 07:22:48 AM

After the sync completes you can send commands to the daemon with Actinium-cli (this is the reason I wrote extra RPC flags, so you can still command the daemon as there is no Actinium.conf).

I understand what a command line argument is, and what Actinium.conf is for; regardless, following the above still results in the same outcome: Actiniumd has crashed

Quote from: brakmic on August 21, 2018, 07:22:48 AM

Have you executed all steps exactly?

Yes, I don't know how I can be any more clear. I would not be posting saying I have done it for several posts now if it worked.

What I could offer you for testing is a separate build, made from a branch that has an extra check for the problematic block (actually, it's the TX in this block that is problematic). I have done some local tests here and although my machines never crash I think it would be of advantage to test what happens when you sync with this alternative build that explicitly overcomes the ASSERTION that provokes the crash.

Please, let me know if you'd like to test it.

---EDIT ---
Here is the branch "interpreter-fix":

https://github.com/Actinium-project/Actinium/tree/interpreter-fix

If you have time, please compile it and let me know if you can sync the chain. Many thanks!

---EDIT 2--
Forgot to mention that the above branch is based on the current 0.17.5.0-BETA which contains built-in Tor. This of course has nothing to do with your problem, but just in case you were wondering why the version number changed. Tor itself is inactive by default. You have to activate it with torenabled=1 in Actinium.conf.