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

[user_fred]

1st POST block 
Block #835214
2015-09-25 16:40:34
dd4aa2538f3b5f367f657c6a4ce71109592f79be547cf710b5f71e5f03185e64

it's worth a look

[babbey]

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

One might be my mothers i will have to check it out today. Thanks!

Fixed.

So it turns out that one of these was one of mine... fixed; hopefully that will reduce the traffic somewhat for the network (and our data caps!!).

Steve, can you tell us if the other 2 nodes are still running? Good to be hunting them down. I only realised I was on the wrong fork when I sent coins from one wallet to the other and they hadn't arrived after almost a day...

[mazzaneo]

Great news all!
We are on coinpayments.net which open the door to a whole host of retailers.

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

[mazzaneo]

If I was to limit the bandwidth of the SolarCoin wallet would that affect the performance in any way?

[y_virtual]

Great news all!
We are on coinpayments.net which open the door to a whole host of retailers.

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

http://poll.pollcode.com/19186112_result?v

Just a reminder 

[corather]

Just wanted to say, the Solarcoin chain seems to be humming along quite nicely. My hat's off to you Steve. Well done Sir.

[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

One might be my mothers i will have to check it out today. Thanks!

Fixed.

So it turns out that one of these was one of mine... fixed; hopefully that will reduce the traffic somewhat for the network (and our data caps!!).

Steve, can you tell us if the other 2 nodes are still running? Good to be hunting them down. I only realised I was on the wrong fork when I sent coins from one wallet to the other and they hadn't arrived after almost a day...

Thanks, vipgelsl.  On the BlockChain tab you can click the Network tab, then next to the client version click the node list button.  We still have 3 nodes on 2.0.5, but that is over a 24 hour period (I believe).

-Steve

[onsightit]

Just wanted to say, the Solarcoin chain seems to be humming along quite nicely. My hat's off to you Steve. Well done Sir.

Thanks, we are pretty solid at ~1 minute blocks now.  Inflation is looking good too, 1.98050928%.

Is the network bandwidth still an issue for anyone?  I am 99% sure it's related to the "spam" blocks from 2.0.5 nodes.  I was about to put a trace on the getblock requests when mine suddenly quit receiving them.

-Steve

[vipgelsi]

Just wanted to say, the Solarcoin chain seems to be humming along quite nicely. My hat's off to you Steve. Well done Sir.

Thanks, we are pretty solid at ~1 minute blocks now.  Inflation is looking good too, 1.98050928%.

Is the network bandwidth still an issue for anyone?  I am 99% sure it's related to the "spam" blocks from 2.0.5 nodes.  I was about to put a trace on the getblock requests when mine suddenly quit receiving them.

-Steve

I am at 3.2% cpu 

[Snake Pliskin]

Is the network bandwidth still an issue for anyone?

Yes I have two wallets running and they are eating up about 20gb a day which is eating my bandwidth up so I have had to turn them off for now as with 1.2 million coins spread across the two wallets and I'm only getting about 20 coins a day.

[onsightit]

Is the network bandwidth still an issue for anyone?

Yes I have two wallets running and they are eating up about 20gb a day which is eating my bandwidth up so I have had to turn them off for now as with 1.2 million coins spread across the two wallets and I'm only getting about 20 coins a day.

We have a 2.0.7 node that is "spamming" now, and is on the wrong chain.  Whoever is 73.10.58.144, you need to reload the blockchain.

Thanks,
Steve

[Snake Pliskin]

We have a 2.0.7 node that is "spamming" now, and is on the wrong chain.  Whoever is 73.10.58.144, you need to reload the blockchain.

How does that eat up the bandwidth Steve if someone is spamming, when you say spamming what are they actually doing to our network as I can't imagine they are sending emails 

[Snake Pliskin]

What should roughly be the normal for daily bandwidth usage

[onsightit]

The average blocksize is roughly 500 bytes, so at one per minute, you get ~720k per day.  Then there's the normal network hand shaking and transaction relaying on top of that.

The nodes that are "spamming" with orphan blocks are also causing a high volume of getblock requests which appear to be creating the abnormal network traffic.  I'm currently debugging it, and may need to issue another release if the nodes do not get on the right chain soon.

EDIT: I just tested a solution that will ban a node for 24 hours if the are "spamming" with orphan block.  I'll release a 2.0.8 version soon.

-Steve

[vipgelsi]

The average blocksize is roughly 500 bytes, so at one per minute, you get ~720k per day.  Then there's the normal network hand shaking and transaction relaying on top of that.

The nodes that are "spamming" with orphan blocks are also causing a high volume of getblock requests which appear to be creating the abnormal network traffic.  I'm currently debugging it, and may need to issue another release if the nodes do not get on the right chain soon.

-Steve

Might be coming from my mom's/dad's wallets since it says NJ

I will have them reload blockchain



Update
It was my dad's wallet. i know he has his computer set to sleep after 10 minutes and doesn't run his wallet 24/7 could this be the cause?  He doesnt want to run his computer all day since his electric $ is more then he makes in coins a day.

But if it helps i will try and convince him to run 24/7

what should i do onsight?

[onsightit]

The average blocksize is roughly 500 bytes, so at one per minute, you get ~720k per day.  Then there's the normal network hand shaking and transaction relaying on top of that.

The nodes that are "spamming" with orphan blocks are also causing a high volume of getblock requests which appear to be creating the abnormal network traffic.  I'm currently debugging it, and may need to issue another release if the nodes do not get on the right chain soon.

-Steve

Might be coming from my mom's/dad's wallets since it says NJ

I will have them reload blockchain



Update
It was my dad's wallet. i know he has his computer set to sleep after 10 minutes and doesn't run his wallet 24/7 could this be the cause?  He doesnt want to run his computer all day since his electric $ is more then he makes in coins a day.

It's fine* to only stake periodically.  If he has reloaded the blockchain recently he should be fine now.

EDIT: *fine for him, but not for the network. 

-Steve

[vipgelsi]

Thanks! Should be good. He is re loading as we speak.

[onsightit]

All,

I just released 2.0.8 to help with the bandwidth issue.  You can get it using Help->Check for Update.


PS: I'm glad I can help some of you visit your parents more often.

-Steve

[Snake Pliskin]

All,

I just released 2.0.8 to help with the bandwidth issue.  You can get it using Help->Check for Update.

-Steve

Great stuff

Thanks Steve 

[mazzaneo]

All,

I just released 2.0.8 to help with the bandwidth issue.  You can get it using Help->Check for Update.


PS: I'm glad I can help some of you visit your parents more often.

-Steve

Thanks Steve