Quote from: old c coder on October 02, 2015, 04:55:13 AM

Quote from: senj on October 01, 2015, 09:51:54 PM

...
Changing how particular peer mines blocks does not change much - bad miners can edit code, build their own release and produce blocks as they please.

Agreed. But what if we added a rule in accept block or add block or whatever it is called that didn't allow consecutive PoW blocks? Is there code in those areas to prevent consecutive PoS blocks, or is it only in the mining code?

Yacoin is based on Novacoin and that means fast proof-of-stake algorithm - the goal was to eventually accomodate as many PoS blocks as possible kept one minute apart on average. But also to keep PoW blocks at 10 minute spacing. That would one day accomplish ultimate decentralization with proof-of-work "checkpointing" every 10 minutes.
If I am not mistaken, here is how pocopoco's source basically controls it and that didn't change from launch.

Fixes I made also strive towards that goal.

Last time I checked there were near 11x more PoW blocks than PoS blocks. Making PoW-PoS-PoW-PoS order mandatory would probably cause long delays while waiting for PoS block.
There could be other problems too, depending on addressing issues with small PoS blocks.

Quote from: old c coder on October 02, 2015, 04:55:13 AM

These changes, I presume, have to be run by all the peers(full nodes) to "reject" submitted blocks that don't "measure up"?

Yes, hard fork is needed. I am certain we can't fix all problems without it.