Quote from: a123 on October 29, 2014, 04:02:34 AM

Quote from: ArchitektoR on October 28, 2014, 07:58:18 PM

Maybe PoB+PoS is much better! Why waste power for GPU-CPU mining, when even RasPi can be used to complete SlimCoin usage? SlimCoin, SlimWallet & SlimMiner (RasPi Wink

)
"Why use expensive and power-hungry hardware, when even Android smartphone can be your e-Wallet & Miner?"

Actually PoS+PoB might be a good idea. I've been thinking a lot about it too! The whole code base is built off Peercoin, and we can't migrate out to a PoW only coin cos of the PoS heritage blocks.

We will have PoB generation and PoS to secure the blockchain.

We may not even have to migrate our PoB. Just tweak PoS to make it generate blocks more frequently (aka undo what slimcoin did before he got busy elsewhere) and I remember the difficulty even reached 1 at some time back then. No one would bother to PoW then!

PoS did cause a lot of trouble for us last time though, in particular it interferes with PoW. But if PoW is meant to be an afterthought this isn't a problem then.

I would prefer keeping the PoW, whatever algorithm we end up deciding, because having PoW protects against 51%-of-burned-coins attacks (at least of some types, such as censorship attempts). However, PoW should be tweaked to make it become unprofitable quickly, because one of the main points of Slimcoin is to discourage power-hungry PoW mining. (This would probably then reduce the incentive to develop GPU / ASIC miners because of the limited profits, but no doubt they would still be built eventually. Just thinking about the risk of 'secret' GPU algorithm, if it has a big advantage, possibly leading to 51% attacks? I would support going to a different well-established CPU-based algorithm given how easily dcrypt seems to be optimised. Of course, then there's still the botnet risk... Undecided

)

Quote from: a123 on October 28, 2014, 12:23:46 AM

Quote from: Mr E on October 27, 2014, 09:41:42 PM

(PS -- I downloaded the 0.3.2.1 Windows build from the Git releases, and it was crashing again like the old wallet did. I've had to go back to 0.3.2.0 for the time being. Sad

)

Any idea why? Dya have a debug log of what led to the crashes?

Can't find them in the log any more, so I'm just firing it up again now, and we'll see what happens. It seemed to be the same or similar crash message as the older version was giving before you fixed it, though.