Post
Topic
Board Announcements (Altcoins)
Re: [ANN][SLR] SolarCoin | PoW to PoS v. 2.0 | Solar Proof of Generation (§1 = 1MWh)
by
corather
on 28/09/2015, 09:12:12 UTC

Question 8:
With version 2.0.1 around, having been downloaded and available for installation, if anyone wants to get on the Lottery-Winning-Train, do they just install 2.0.1 and start staking millions of SLR? Which blockchain should they stick to for better results - the main 1.5 PoW blockchain, or the forked 2.0.3? With no blockchain explorer around, I bet the 2.0.1 version is the way to go if anyone wants to get into the billions of SLR within a day or two, without being noticed.

 Cool Edit: Any further code changes to PoST implementation MUST FIRST ensure 2.0.1 will not be allowed to stake on the blockchain.


I'm having trouble synchronizing one of my wallets. It's trying to download blocks beyond the current, 835297. This may be due to people running older wallets. It may be necessary to update the next wallet (2.04) to reject any connections below 2.04. This had to be done for Feathercoin if I remember correctly when they were switching to a centralized coin structure.

"It may be necessary to update the next wallet (2.04) to reject any connections below 2.04."
If there is a way to that, that will be great, this will solve (I guess) the concern in question 8.




It's quite possible and it's really only a couple of lines of code.

Will keep an eye on that for sure!

btw, one of the reasons I am still mostly on 1.5 is that I am expecting to test the process of the transition from 1.5 to 2.0.4 and the moment I get rejected from 1.5, or have no incentive at all to stay there even if I wanted to. Now replace "I" with "Anyone"...

Also I think I just found a solution to the sync problem as of now - get the 2.0.3 node list from here:
https://chainz.cryptoid.info/slr/#!network
and replace with it the contents of the SolarCoin.conf file in the C:\Users\...\AppData\Roaming\SolarCoin folder, then restart 2.0.3. Synced it right away for me after several attempts I did with the same unsuccessful results you quoted.

I'm giving the .conf idea a try. I copy/pasted the original .conf file and then deleted the nodes from the original and pasted the list from the explorer.