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

nickgogerty

sr. member

Activity: 365

Merit: 250

Making things better with better things.

Quote from: onsightit on September 28, 2015, 09:44:52 AM

All,

I will be posting 2.0.4 very soon (hopefully within an hour or two). I just need to re-compile all the wallets and upload them to the web server. i wanted to run another testnet, which was successful. I have also confirmed that the RTI changes I made to the Average Stake Weight function are working and you will be happy to have a smaller carbon footprint with 2.0.4.

Note: In 2.0.4, you will still earn 10% interest up to block 836000, then it will switch to 2% going forward.

-Steve

2.0.4 is up Can now be updated from within the wallet.

Also available for download from the directory http://solarcoin.org/downloads/ Website will be updated in 5-7 hours in all languages.

solarcoiner

sr. member

Activity: 445

Merit: 250

I backed up my wallet.dat and deleted my entire Solarcoin folder in %appdata%
Installed 2.04 and it's reloading the blockchain now!
Thank you Steve for you hard work!

y_virtual

sr. member

Activity: 377

Merit: 251

Note to self: it's not you doing it, it's us.

Quote from: biodieselchris on September 28, 2015, 01:37:24 PM

anybody's window wallet snag for along time on the "done loading" part of the load screen? Been doing this before and this version it still has opened the wallet yet.

Yes, on the one PC with the much larger wallet file (very long transaction history). Usually rescanning the wallet takes that long...don't know for sure yet.

biodieselchris

hero member

Activity: 579

Merit: 500

CoinQuacker

anybody's window wallet snag for along time on the "done loading" part of the load screen? Been doing this before and this version it still has opened the wallet yet.

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

Quote from: mazzaneo on September 28, 2015, 01:20:02 PM

Just updated the wallet and i'm getting alot of small interest payments. Is this what I previously earned and they are all coming in at once now that we have updated?

Can someone confirm we are currently on block 835317.

Thanks

Currently on 835318.

Staking is based on coinage. Not all of your coins have the same age, and as the network matures, the coins will split, and the ages will spread out even more. This will also have the effect of helping us reach the target of 1 block per minute.

It will be several days before things settle down.

-Steve

Alao

sr. member

Activity: 493

Merit: 250

How do you state all of the coins in your wallet. I noticed it only picked a portion of my coins.

terciops

member

Activity: 74

Merit: 10

The change to 2.04 went smoothly enough and all is now in synch. However I am still only 'staking' about 2% of my coins. This number has been static since the rollover from 2.01.

The total coin volume is correct.

Can I get them all on board or is it just a case of waiting patiently.

2.04 is using about half the CPU power of 2.03. Nice(r).

T

mazzaneo

sr. member

Activity: 300

Merit: 250

Just updated the wallet and i'm getting alot of small interest payments. Is this what I previously earned and they are all coming in at once now that we have updated?

Can someone confirm we are currently on block 835317.

Thanks

y_virtual

sr. member

Activity: 377

Merit: 251

Note to self: it's not you doing it, it's us.

Quote from: onsightit on September 28, 2015, 12:19:33 PM

Quote from: y_virtual on September 28, 2015, 10:02:50 AM

Quote from: onsightit on September 28, 2015, 09:48:19 AM

Quote from: Epiphany on September 28, 2015, 09:41:47 AM

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

No, it's much friendlier. When a wallet node receives "bad data" from another wallet node, it flags the node with a DoS score. When the score reaches 100 for a given node, it is removed from the list of reliable nodes and is no longer communicated with. That information is stored in peers.dat, which is why I recommend removing it when upgrading to 2.0.4.

-Steve

If anyone is still running 2.0.1 (which apparently is the case), and they got the wrong 2.0.1 interest awards, what happens to those awards? Will they be confirmed?

Everyone running 2.0.1 past block 835000 will show their interest as "conflicted" in the wallet.

-Steve

Great, thank you Steve!

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

Quote from: vipgelsi on September 28, 2015, 12:26:44 PM

Thanks for the hardwork how was your trip?

Thanks, got quite a bit of climbing in, and camped with my brother and my dog Leo. Good times...

-Steve

vipgelsi

legendary

Activity: 1736

Merit: 1001

Thanks for the hardwork how was your trip?

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

All,

2.0.4 is out. Please update asap and run File->Reload Blockchain to get your node staking.

Note: Because the wallet downloads are hosted on the shared web server, you may not have any luck using the in-wallet "Check for Update" feature. If it says the download completed but only took one second, it did not successfully download the update. Sad

Next release, they will be hosted on the dedicated server.

In the mean-time, you can download them from the official http://solarcoin.org/downloads/ site.

To see what's new, go to "Help->Check for Update" in the wallet.

-Steve

EDIT: Here are the individual links.

http://solarcoin.org/downloads/SolarCoin_2.0.4_32bit.exe (Windows)
http://solarcoin.org/downloads/SolarCoin_2.0.4_64bit.pkg (Mac)
http://solarcoin.org/downloads/SolarCoin_2.0.4_64bit.run (Linux 32-bit)
http://solarcoin.org/downloads/SolarCoin_2.0.4_32bit.run (Linux 64-bit)

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

Quote from: y_virtual on September 28, 2015, 10:02:50 AM

Quote from: onsightit on September 28, 2015, 09:48:19 AM

Quote from: Epiphany on September 28, 2015, 09:41:47 AM

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

No, it's much friendlier. When a wallet node receives "bad data" from another wallet node, it flags the node with a DoS score. When the score reaches 100 for a given node, it is removed from the list of reliable nodes and is no longer communicated with. That information is stored in peers.dat, which is why I recommend removing it when upgrading to 2.0.4.

-Steve

If anyone is still running 2.0.1 (which apparently is the case), and they got the wrong 2.0.1 interest awards, what happens to those awards? Will they be confirmed?

Everyone running 2.0.1 past block 835000 will show their interest as "conflicted" in the wallet.

-Steve

y_virtual

sr. member

Activity: 377

Merit: 251

Note to self: it's not you doing it, it's us.

Now, as it has been requested, I brought back my biggie wallet from 1.5 back to 2.0.3.
Guess what? 3 blocks in a row, last 3 blocks (no other wallets find any blocks, I mean), 2-3 hours apart from each other (apparently that depends on how much patience I have): each of them soon after a restart and/or wallet rescan.
The wallet declared "staking" only before the first block found, in between the second and the third it stays "In Sync, not staking, earning Stake-Time".
Right now it says "In Sync".
Edit: I was wrong, it does start Staking soon after the restart (missed to notice that before). Restarted few minutes ago, it is now Staking, so next block is on it's way.

Do you want me now to "move" the 2.0.3 blockchain manually. I mean, I can't do a restart every minute, obviously... What time frame?

Let's better wait for 2.0.4 and see.

Thanks!

vipgelsi

legendary

Activity: 1736

Merit: 1001

Should not count mine didnt

y_virtual

sr. member

Activity: 377

Merit: 251

Note to self: it's not you doing it, it's us.

Quote from: onsightit on September 28, 2015, 09:48:19 AM

Quote from: Epiphany on September 28, 2015, 09:41:47 AM

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

No, it's much friendlier. When a wallet node receives "bad data" from another wallet node, it flags the node with a DoS score. When the score reaches 100 for a given node, it is removed from the list of reliable nodes and is no longer communicated with. That information is stored in peers.dat, which is why I recommend removing it when upgrading to 2.0.4.

-Steve

If anyone is still running 2.0.1 (which apparently is the case), and they got the wrong 2.0.1 interest awards, what happens to those awards? Will they be confirmed?

Epiphany

sr. member

Activity: 406

Merit: 250

Quote from: onsightit on September 28, 2015, 09:48:19 AM

Quote from: Epiphany on September 28, 2015, 09:41:47 AM

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

No, it's much friendlier. When a wallet node receives "bad data" from another wallet node, it flags the node with a DoS score. When the score reaches 100 for a given node, it is removed from the list of reliable nodes and is no longer communicated with. That information is stored in peers.dat, which is why I recommend removing it when upgrading to 2.0.4.

-Steve

OK. Thanks.

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

Quote from: Epiphany on September 28, 2015, 09:41:47 AM

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

No, it's much friendlier. When a wallet node receives "bad data" from another wallet node, it flags the node with a DoS score. When the score reaches 100 for a given node, it is removed from the list of reliable nodes and is no longer communicated with. That information is stored in peers.dat, which is why I recommend removing it when upgrading to 2.0.4.

-Steve

onsightit

sr. member

Activity: 308

Merit: 250

truth=(true?true:false);

All,

I will be posting 2.0.4 very soon (hopefully within an hour or two). I just need to re-compile all the wallets and upload them to the web server. i wanted to run another testnet, which was successful. I have also confirmed that the RTI changes I made to the Average Stake Weight function are working and you will be happy to have a smaller carbon footprint with 2.0.4.

Note: In 2.0.4, you will still earn 10% interest up to block 836000, then it will switch to 2% going forward.

-Steve

Epiphany

sr. member

Activity: 406

Merit: 250

Quote from: onsightit on September 28, 2015, 09:36:28 AM

... Nodes on protocol version 70003 are likely DoSing nodes on 70004.

-Steve

Is this what you're referring to?

https://en.wikipedia.org/wiki/Denial-of-service_attack

Topic: [ANN][SLR] SolarCoin | PoW to PoS v. 2.0 | Solar Proof of Generation (§1 = 1MWh) - page 198. (Read 466799 times)