Good work!!! Did you compile latest release?
Not yet. I've been waiting to see whether the code was basically functioning across the range, not just mint-by-burn but also mint-by-stake.
Your post prompted me to check.
Serendipitously, I received the first mint-by-stake tx just as this morning broke.
It was followed by an orphaned mint-by-stake, then two others which were confirmed, totalling very close to the amount of the orphaned tx.
Pix ...
Slimcoin has faultlessly recovered from around a dozen hard crashes of my laptop. The other evening I nudged the machine as I got out of the armchair to retire to bed, inadvertently disconnecting the power cable. The battery drained in less than an hour, shutting the machine down. Slimcoin is configured to start on bootup so in the morning, after I'd re-connected the power cable and the machine had booted, I checked how Slimcoin had got on, synching up to the chain tip. There was just one block to go, apparently .... after a few moments had passed, I realised that it had stuck, as it had done on a previous occasion and, like last time, I should just tough it out and get on with other things. When I re-checked later, it had caught up just fine.
During my Slimcoin-related pereginations, I managed to make the connection between the code that gmaxwell was referencing:
Peercoin uses POW to select which stake can actually mine, it also uses broadcast block signing from the developer to get all the miners selecting from the same stake holders and prevent anyone but the developer from replacing the chain history. ... but thats pretty big centeralization risk.
And the to-be-triggered v04 code in the Slimcoin port (of peercoin) which I postponed because I wasn't in a position to evaluate the effects of such a profound change on the Slimcoin blockchain.
It's currently set to trigger on the 31st Dec this year:
https://github.com/slimcoin-project/Slimcoin/blob/209d10771ed1f3851525d081a2727b04dacf0607/src/kernel.cpp#L19// Protocol switch time of v0.4 kernel protocol
unsigned int nProtocolV04SwitchTime = 1483056000; // Dec 31 2016
unsigned int nProtocolV04TestSwitchTime = 1483056000; // Dec 31 2016
Except that the implementing code is actually disabled (commented out), so nothing will actually happen. That code can now just be excised.
So ...so far, so good. I'll tidy up the codebase and commit it to the public repos.
I'll look into the possibility of cross-compiling a Windows binary, can't promise anything.
The OS X 10.6.8 app is quietly ticking away on the old MacBook (Slimcoin was originally advertised as suitable for running on a Raspberry Pi iirc), hasn't seen any minting tx as yet.
The implementations running on the remote server, my laptop and the MacBook are all in synch with the advertised blockchain explorer:
https://bchain.info/SLM/ but I'm really not sure whether I believe the results of `getpeerinfo`.
I think I have a Vagrant+ansible deployment setup around somewhere, I'll add it as a separate repos in the github project pages - if/when I find it.
Cheers
Graham