[ANN][SLR] SolarCoin | PoW to PoS v. 2.0 | Solar Proof of Generation (§1 = 1MWh)

[vipgelsi]

now I'm on block 837589, which matches the explorer but missing ~30k coins (over half). I haven't transacted any coins since 2014.

try re scan wallet?

[1714028315]

1714028315

[1714028315]

1714028315

[1714028315]

1714028315

[1714028315]

1714028315

[biodieselchris]

now I'm on block 837589, which matches the explorer but missing ~30k coins (over half). I haven't transacted any coins since 2014.

try re scan wallet?

yep. finally got it. thx

[user_fred]

Hi, i am on the right chain (2.0.7) , but still have some conflicted interest sometimes. staking , and same block on wallet & explorer block 837819.
http://www.hapshack.com/?v=TX3m8.jpg
I don't know why it happens again

[corather]

Hi, i am on the right chain (2.0.7) , but still have some conflicted interest sometimes. staking , and same block on wallet & explorer block 837819.
http://www.hapshack.com/?v=TX3m8.jpg
I don't know why it happens again

It's just like mining, sometimes you generate an orphan. It's normal.

[corather]

I noticed on windows 7 in the block explorer the Back, Home, and Forward buttons are not functional, however in windows XP they function perfectly.

[solarcoiner]

Hi, i am on the right chain (2.0.7) , but still have some conflicted interest sometimes. staking , and same block on wallet & explorer block 837819.
http://www.hapshack.com/?v=TX3m8.jpg
I don't know why it happens again

It's just like mining, sometimes you generate an orphan. It's normal.

funny, I haven't gotten a single conflicted interest payment yet!

[y_virtual]

FYI:

https://www.dropbox.com/s/szkcjfzvtkxbrgl/SLRvotedInCoinPaymnents.PNG?dl=0

https://www.coinpayments.net/supported-coins

[corather]

FYI:

https://www.dropbox.com/s/szkcjfzvtkxbrgl/SLRvotedInCoinPaymnents.PNG?dl=0

https://www.coinpayments.net/supported-coins

I have 2. Lag has something to do with it. The faster you can send your result of a solved block to the network, the more likely your solve will voted in by consensus.

edit: correction I have several.

[Snake Pliskin]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

[solarcoiner]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

I think steve is going to have to release another update... This also happened to me when i deleted peers.dat.
I have since recovered the new peers.dat file and replaced it with the old one and it works again. So I guess it's still trying to connect you to ''bad peers''

[corather]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

https://chainz.cryptoid.info/slr/

It'll keep you up to date.

[corather]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

I think steve is going to have to release another update... This also happened to me when i deleted peers.dat.
I have since recovered the new peers.dat file and replaced it with the old one and it works again. So I guess it's still trying to connect you to ''bad peers''

It seems to happen when there's the slightest disruption in your local network also.

[solarcoiner]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

I think steve is going to have to release another update... This also happened to me when i deleted peers.dat.
I have since recovered the new peers.dat file and replaced it with the old one and it works again. So I guess it's still trying to connect you to ''bad peers''

It seems to happen when there's the slightest disruption in your local network also.

Alright I hadn't noticed! it hasn't tried to load the other chain since several days now I had this issue back on 2.02 I think, but I guess I just got lucky that i stayed on the main chain and my peers.dat didn't get any bad peers.
Does staking still work for you guys or is it constantly trying to sync?

[corather]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

I think steve is going to have to release another update... This also happened to me when i deleted peers.dat.
I have since recovered the new peers.dat file and replaced it with the old one and it works again. So I guess it's still trying to connect you to ''bad peers''

It seems to happen when there's the slightest disruption in your local network also.

Alright I hadn't noticed! it hasn't tried to load the other chain since several days now I had this issue back on 2.02 I think, but I guess I just got lucky that i stayed on the main chain and my peers.dat didn't get any bad peers.
Does staking still work for you guys or is it constantly trying to sync?

It's still having a bit of trouble. If I can keep a stable connection it works well, otherwise it can get stuck in an endless syncing cycle. Reloading the wallet seems to fix the trouble until my connection gets the hiccups. My network isn't 100% stable, cheap cables, heh.

[babbey]

Just FYI: both my wallets seem to be rolling along nicely on 2.0.7, with interest payments coming in every 20-30 minutes. The payments are tiny, with most in the 0.01 to 0.1 range, but I'll take whatever comes! 

Have only had one or two conflicted payments which seems about right.

[Alao]

Speaking of peers. the wallets still on 2.0.5 and 2.0.6 are on a mini fork.  They need to do the following:

1. Update to 2.0.7
2. Reload the Blockchain
3. Rescan the Wallet
4. Shut the wallet down
5. Remove C:\Users\{your name}\AppData\Roaming\SolarCoin\peers.dat
6. Restart the Wallet

Thanks,
Steve

After I followed these steps it seem that my interest that was generated on 10/3/2015 is now rejected with question marks next to them.  I was upgrading from 2.0.5.  Guess i was on a mini fork..

[onsightit]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

There is still a node on the wrong fork.  Whoever is 150.101.243.74 is sending orphan blocks to you, and reporting a different block height.

-Steve

[onsightit]

Speaking of peers. the wallets still on 2.0.5 and 2.0.6 are on a mini fork.  They need to do the following:

1. Update to 2.0.7
2. Reload the Blockchain
3. Rescan the Wallet
4. Shut the wallet down
5. Remove C:\Users\{your name}\AppData\Roaming\SolarCoin\peers.dat
6. Restart the Wallet

Thanks,
Steve

After I followed these steps it seem that my interest that was generated on 10/3/2015 is now rejected with question marks next to them.  I was upgrading from 2.0.5.  Guess i was on a mini fork..

Yes, you should regenerate those interest payments again. However, you just lost a little time before the next interest payments.

-Steve

[onsightit]

whats the correct block number is it 837950

Mine synced ok this morning and then now showing 857 blocks remaining

I think steve is going to have to release another update... This also happened to me when i deleted peers.dat.
I have since recovered the new peers.dat file and replaced it with the old one and it works again. So I guess it's still trying to connect you to ''bad peers''

It seems to happen when there's the slightest disruption in your local network also.

Alright I hadn't noticed! it hasn't tried to load the other chain since several days now I had this issue back on 2.02 I think, but I guess I just got lucky that i stayed on the main chain and my peers.dat didn't get any bad peers.
Does staking still work for you guys or is it constantly trying to sync?

It's still having a bit of trouble. If I can keep a stable connection it works well, otherwise it can get stuck in an endless syncing cycle. Reloading the wallet seems to fix the trouble until my connection gets the hiccups. My network isn't 100% stable, cheap cables, heh.

It's more likely related to this: https://bitcointalk.org/index.php?topic=785257.msg12598176#msg12598176

-Steve

[onsightit]

Here's a list of nodes that are on the wrong fork:  (based on my debug.log file)

150.101.243.74
174.57.197.124
222.237.39.100
173.57.196.254

These are also causing the "out of sync" issue for some.

-Steve