Quote from: ax66 on May 02, 2016, 07:52:04 AM

Quote from: Nightz on May 02, 2016, 07:45:46 AM

Quote from: ax66 on May 02, 2016, 07:39:32 AM

Quote from: Nightz on May 02, 2016, 07:08:29 AM

Quote from: Amph on May 02, 2016, 07:05:45 AM

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Nightz, check debug.log, you'll see that bloody orphans disaster beginning.
if you don't beat it in near future, it'll bury the coin as it did with other clones.
maybe more strict rules to mark nodes as misbehaving cd help idk

That is a good point mate and I can certainly look into the Banning of bad nodes through misbehaviour Wink

.

I also lowered the amount of orphans to be kept in the memory too from 750 to 200.

lowering to 200 just made it less resource hungry but doesn't beat anything, look here:

https://gist.github.com/ax66/5856bf5a875167b254a46bdb1b3022d3

and it's rolling and rolling more of'em

it may sound strange but there wasn't such flood in v1.2, it's only now in v1.3
maybe some good code change turned bad in practice

maybe the change to weight has caused it. possibly it will calm down when the age /difficulty relationship settles ??

before the change weight did not seem to be playing a major part of staking, i checked a variety of sizes vs age and there seemed really no consistency.
but since then i got a string of similar sized stakes all together in one clump

also what about ye olde centralised checkpointing that ppc heritage comes with

https://github.com/LGLoco/Loco/blob/master/src/checkpoints.cpp#L321

ofc that would mean another update Cheesy