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

[onsightit]

Hi all, for me, CPU load is not fixed (osx) on 2.0.4, rescan done, "earning stake time"

You will see high CPU usage when the wallet is still syncing.  Once it is staking, you should see lower CPU usage than in previous versions.

-Steve

[1714194506]

1714194506

[1714194506]

1714194506

[fairglu]

Explorer wallet updated to 2.0.4, the RPC API bug appears too have been fixed!
New blocks showing up at https://chainz.cryptoid.info/slr/ (wallet still catching up at the moment, restarted from the bootstrap)

[onsightit]

Interesting observation....
I have about 9 wallet addresses staking and my oldest and largest is finding the majority of my blocks but each block earns an average of .25 SLR while my newest, smaller wallets are earning an average of 2 to 8 SLR as a block reward.

I thought older wallets = better rewards.

Could just be a coincidence though...

There was a request to put a cap on the maximum number of days (30) to use in calculating the coinday weight.  The largest payout I saw on testnet was 11.4 SLR with an input of 1,000,000 coins.

-Steve

[onsightit]

Explorer wallet updated to 2.0.4, the RPC API bug appears too have been fixed!
New blocks showing up at https://chainz.cryptoid.info/slr/ (wallet still catching up at the moment, restarted from the bootstrap)

Awesome!  Thanks, fairglu.  I can confirm that the gettransaction RPC call is working for both the PoW and PosT block transactions.

EDIT: getrawtransaction works too.

-Steve

[fairglu]

Explorer wallet updated to 2.0.4, the RPC API bug appears too have been fixed!
New blocks showing up at https://chainz.cryptoid.info/slr/ (wallet still catching up at the moment, restarted from the bootstrap)

Awesome!  Thanks, fairglu.  I can confirm that the gettransaction RPC call is working for both the PoW and PosT block transactions.

EDIT: getrawtransaction works too.

-Steve

Hmmm, RPC call now fails to obtain tx on block 835001 :/
(For tx 29db570a1c36db492d30c9e515cce30bcaf1084cb6647eb31feb615615dab36f)

Also no PoS block until that point, is that correct?

[onsightit]

Explorer wallet updated to 2.0.4, the RPC API bug appears too have been fixed!
New blocks showing up at https://chainz.cryptoid.info/slr/ (wallet still catching up at the moment, restarted from the bootstrap)

Awesome!  Thanks, fairglu.  I can confirm that the gettransaction RPC call is working for both the PoW and PosT block transactions.

EDIT: getrawtransaction works too.

-Steve

Hmmm, RPC call now fails to obtain tx on block 835001 :/
(For tx 29db570a1c36db492d30c9e515cce30bcaf1084cb6647eb31feb615615dab36f)

Also no PoS block until that point, is that correct?

That is what we were seeing before.  PoW txns are fine and the first PoST txn fails.

I'll take a look at it on mainnet and see what might be different from testnet.

Thanks, fairglu.

-Steve

[onsightit]

Explorer wallet updated to 2.0.4, the RPC API bug appears too have been fixed!
New blocks showing up at https://chainz.cryptoid.info/slr/ (wallet still catching up at the moment, restarted from the bootstrap)

Awesome!  Thanks, fairglu.  I can confirm that the gettransaction RPC call is working for both the PoW and PosT block transactions.

EDIT: getrawtransaction works too.

-Steve

Hmmm, RPC call now fails to obtain tx on block 835001 :/
(For tx 29db570a1c36db492d30c9e515cce30bcaf1084cb6647eb31feb615615dab36f)

Also no PoS block until that point, is that correct?

That is what we were seeing before.  PoW txns are fine and the first PoST txn fails.

I'll take a look at it on mainnet and see what might be different from testnet.

Thanks, fairglu.

-Steve

Well, it looks like transactions from block 835214 onward are the first PoST (version 3) blocks. Blocks 0 to 835213 are PoW (version 2). This occurred when we pulled the plug on 2.0.1, effectively setting end-of-pow at height 835213. Now I know how to fix it, so I'll get an update for you asap.  We may need to issue a 2.0.5 wallet update.

-Steve

[lfloorwalker]

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

Thanks for the great work Steve! I am a rockclimber also, mountains are great...
Just updating two of our wallets to 2.0.4
I didn't delete peers.dat yet. Should I still do that?

[Alao]

Mine seems to be stuck on the last 67 blocks.  Going to see if updating to 2.0.4 will do anything.

[onsightit]

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

Thanks for the great work Steve! I am a rockclimber also, mountains are great...
Just updating two of our wallets to 2.0.4
I didn't delete peers.dat yet. Should I still do that?

Nice, where do you like to climb?

It's a good idea to remove peers.dat with this release, as there has been a bit of a battle between 2.0.1/2/3 and 2.0.4.  It will let the nodes sort out who's good or bad, and restore those that were bad, but are now good.  (That's the "technical" explanation.)

-Steve

[onsightit]

Mine seems to be stuck on the last 67 blocks.  Going to see if updating to 2.0.4 will do anything.

To make it easier on you, remove blk0001.dat, peers.dat and txleveldb from your data directory, then install 2.0.4 and Reload the Blockchain.

-Steve

[Alao]

What is the exact location of the data directory.

[Alao]

Is there anyway to change the data location to another drive than C:\Users\<login>\AppData\Roaming\SolarCoin

[onsightit]

Is there anyway to change the data location to another drive than C:\Users\<login>\AppData\Roaming\SolarCoin

Add:

datadir={new location here}

To the solarcoin.conf file.

E.g.:

datadir=D:\Wallets\SolarCoin

It works, but when you do new installs, be sure to uncheck the box for installing a config file.  The config file still has to live in C:\Users\<login>\AppData\Roaming\SolarCoin  though the rest of the data can live in the new location.

-Steve

[lfloorwalker]

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.

Mine took considerably longer to load (like biodieselchris) than ver2.0.3, but I just let it go, and it loaded eventually.
Now I am re-downloading bootstrap and reloading the blockchain in Windows ver2.0.4

My Mac ver2.0.4 is running smoothly, current block 835,397. And "In sync".

[lfloorwalker]

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

Thanks for the great work Steve! I am a rockclimber also, mountains are great...
Just updating two of our wallets to 2.0.4
I didn't delete peers.dat yet. Should I still do that?

Nice, where do you like to climb?

It's a good idea to remove peers.dat with this release, as there has been a bit of a battle between 2.0.1/2/3 and 2.0.4.  It will let the nodes sort out who's good or bad, and restore those that were bad, but are now good.  (That's the "technical" explanation.)

-Steve

Thanks steve, I usually freeclimb in Hokkaido, and Nagano.
Indoor climbing (bouldering) at the gym. Climbing is like a continuous 3D jig-saw puzzle.

Deleted peers.dat on windows.

Cheers,
-lfloorwalker

[lfloorwalker]

How is Bittrex trading at the moment? Their own sidechain of wallet addresses?
Or on the ver1.5 wallet?

Or are they running ver2.0.4?

Thanks,
-lfloorwalker

[CryptoNick]

I just found a problem with my wallet. The coins will never unstake now.

My wallet says 119,000 coins with only 59,992 staked constantly. This has been since 2.0.1 and my first reward for staking was 5 coins. Then it grabbed the 5 coins and 59,992 coins to stake and they have been stuck since that day on 2.0.1.

My wallet got messed up by all the upgrades or something. The power did shut off too so I am not sure if that caused it or if I have to wait 510 blocks to get my coins out of staking since the 5 I got for reward are lumped in with them and can't come out until the 510th block confirm.

I will post some screen shots when I get more time.

[vipgelsi]

I just wish the wallet would not freeze so much 

[y_virtual]

Issue in 2.0.4 (not sure if it existed in 2.0.3, but I think I did see it in 2.0.1, there was no time to re-create, the issue is period-of-time dependent):

Description (no specific numbers, will further investigate if needed):

1. While still in 2.0.3 (re-installed ~18 hours ago) spendable amount started decreasing and staking increasing as expected, total being correct as expected (spendable+staking+interest).
2. Upgraded to 2.0.4 about 10 hours ago.
3. 10 blocks found since then, all in the first 2 hours (until non-reserved spendable got almost exhausted - see below)
4. I also did have a non-staking reserve purposely set while still in 2.0.3, increased it in 2.0.4
5. 1-2 hours ago, spendable was down close to the reserve amount, with some SLRs left to go staking before the non-staking reserve was reached - my intention was to test that specific functionality.
6. I check again several minutes ago, and see Spendable back up to almost the initial balance (but not quite there). As pointed out in 3., last block found was almost 8 hours ago, so the change in numbers is apparently  not related to finding a block
BUT
7. Staking amount has NOT decreased. Did not track the numbers precisely for this test, but it looks like Staking stays at the max number it had reached.
8. Total is now wrong - it is almost double the actual number
The wrong Total number appears in 2 places - in the Balance stats, as well as on the bar to the left of the Staking circle.
9. Transaction History does NOT update to the wrong Total number even when I update it the usual way, so I guess the History Total is apparently CORRECT
9. Number of confirmations of the first block found ~18 hours ago - 103 as of now (time of writing)
10. Number of confirmations of the first block found in 2.0.4 - 72 as of now (time of writing)
I was expecting to start seeing Spendable go back up only after interest confirmations reached the 501 as noted.

Edit: 11. Just re-scanned the wallet, it is back to the correct numbers as of point 5 above.

Issue with unexpected increase in Spendable leading to a wrong Total remains. A requirement to re-scan wallet when that happens is NOT ACCEPTABLE