Just a quick update,
I've forked slimcoin to
https://github.com/kryptoslab/slimcoin. I pushed a couple of changes here which focuses on gradually banning clients that are stuck at 15164 or keep requesting for blocks between 30k to 60k, while not keeping legitimate users away. If you have memory concerns, this would be quite useful; my clients now run consistently at a lower RAM utilisation and uses much less bandwidth - the old code really can eat up gigabytes of both RAM and bandwidth every day.
Also, hankrules suggested a checkpoint which I incorporated into the code. He is also offering to work on a dnsseed node.
Currently I'm about a quarter done into browser-based burning. I quite like the convenience of the idea here and I do intend for it to visually show how mining and burning works in an interactive fashion, so as to educate and encourage the uptake of SLM.
Also, I have noted that since the change the supply of SLM has grown much faster than before. I know, in theory it should be the same like before because of the diff adjustment for PoS. Perhaps it is related to the PoW changes, I don't know.
The rates of SLM minting for PoW and PoB are inversely linked to the difficulty, so I guess the minting rate is much higher. A month back it was like, 8 SLMs minted every PoW block but now it's 12 to 13.
I am neutral regarding PoS removal. Note that PoS in PPC is the main security mechanism, with PoW having almost no importance. So in a PPC-based PoW/PoB coin without changing this, the PoB algorithm (which is the most experimental part of the coin) would carry "most responsibility" for blockchain security. But I am not an expert on this issue, only read this in the PPC forums, as I am not a programmer.
I'm also quite ambivalent about PoS removal. PoB in this current implementation does not secure the blockchain, and the design of SLM actively discourages mining, so it might make Slimcoin vulnerable to 51% attacks if it's PoW/PoB only.
I'll explore 2 methods of fixing the PoS issue on a testnet branch and will update here once I get the code up; hopefully everyone can run a copy to test and we can be rich in test-SLMs for a bit.
I intend to check/change the hashing function (slimcoin himself did note that this is quite intensive and he tried to fix it), as well as simulate and re-weigh the values for PoS, PoB and PoW. If all these fail, then I'll disable PoS and we can see if it helps stability (compared to the main fork).
If all goes well, we can then have a hard fork implementing these PoS changes and disabling access from old clients.
In the background, we should still see if there are any skilled devs willing to port it to a newer code-base. Slimcoin did mention he was interested in this approach though he remains busy.
Could I have your SLM address for donation, please? Very appreciate for helping this coin.
I am planning to give SLMs away faucet-style, but tied to IP and the web-wallet mining itself (ala lucky draw while browser mining), so will welcome donations for spreading more SLMs around and get people excited about it. You can donate SLMs to Sg72f5icXXAjrdV7o15ZrFdj9CvNaTZwS1; this is what feeds the browser mining rewards (besides the rewards from mining, that is).