a123 could you consider to create a new thread if the old dev won't respond ?
I would try to contact him first. This is really mostly his work, still. But if there's no response I can start a new thread.
I propose in the continued absence of the main dev, we do a hard fork once
1) PoS is removed
2) we obtain a pool operator or two
3) centralised sync checkpointing is removed (anyone has an opinion on this?)
If no one is against PoS removal, I will just code it such that all PoS blocks after the hard fork will be rejected (for instance, a Block's IsProofOfStake() will always resolve to False if height > forkheight.).
For centralised sync checkpointing, I'll just turn the hardcoded public key into maybe all zeroes or even the SLM burning address, and turn the warnings off (or make the last syncpoint's expiry never expire)
Anything else to be done? I remember reading something about P2Pool needing a few fixes to be operable with Slimcoin. Anyone has details on this?
Hard fork will reject all old clients from connecting and be pure PoW/PoB hybrid.
In the meantime, we could do a community wiki to start collating all the SLM information (such as compilation instructions, installation instructions, PoB theory, etc) so as to help, as well as to start looking for issues / improvements for SLM.
I have enabled the Wiki and Issues tracking feature on my Github page for Slimcoin:
https://github.com/kryptoslab/slimcoin, but would be open to suggestions as to where else best to host such information (:
Whoever built the 116k SLM buy wall, that's amazing
Price action tends to attract adopters so things are definitely looking up!
