Quote from: truecry on August 20, 2018, 10:43:43 PM

I have started Actinium with no flags, with any flags, with no other config - though this should not matter, ultimately it does not matter, it will always crash / quit at the same point. Upon scan of the chain, once this height is reached, the software crashes. This happens from the bootstrap, from the network, or from my old previously working chain. The software does not remain running. Upon relaunching Actiniumd the same issue will occur. The daemon cannot be used with the active chain.

Debug entries before crash:

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.

The issue with the release notes is the language of "weird error" which does not really reflect an actual error. The error is not weird. It is understandable and that is why I am writing about it here, because I have not developed this coin or worked with any Segwit code.

The term "weird error" was used because most of our users came with this questions to us, in the Discord. It would be very easy for me to write "Assertion Error in C++ Code - Script Parsing Error - while chain sync".

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).
b) Start the Daemon with the flags -daemon -server -txindex -reindex -port=4334 -rpcport=2300 -rpcuser=user1 -rpcpassword=blah -rpcallowip=127.0.0.1
c) Wait for the sync to complete (you can run tail -f $HOME/.actinium/debug.log to watch the sync)

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).

Have you executed all steps exactly?