Author

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

sr. member
Activity: 445
Merit: 250
Maybe someone can answer this...
Is there any benefit of problem to running the same wallet on 2 or 3 machines simultaneously? Will it help or hinder the network?

Not a good idea, you can corrupt your wallet
sr. member
Activity: 445
Merit: 250
If so, can someone please clarify how exactly the confirmation process works? Is the confirmation process tied to block generation ie. 500 confirmations = 500 new blocks, or is it independent ie. a seperate function of the network that doesn't relate to the coin life cycle itself?

Thanks in advance.

I can answer my own question here, I've just updated to 2.0.6 and have been watching the number of confirmations verse the block height and can confirm (no pun intended) that with every increase in block height the confirmations increase proportionally.

On a happy note, it appears as thought the block height is now increasing about one block per minute. In the time it's taken me to check my confirmations and write this post I've watched the height go from 835744 to 835751.


Blocks are really rolling in fast all of a sudden! Updating to 2.06 now.. lets see how it goes

On my first attempt to update through the wallet the download stopped at 99%, then failed. I retried and it worked fine the second time. Hope yours goes smoothly.

Just updated. It worked right away. Nice to see that I already have over 50 confirms on my new interest payment. It seems like the network is working much ''faster''now Wink
Special thx to Steve who has put a lot of effort into this!
sr. member
Activity: 300
Merit: 250
Maybe someone can answer this...
Is there any benefit of problem to running the same wallet on 2 or 3 machines simultaneously? Will it help or hinder the network?
sr. member
Activity: 337
Merit: 258
If so, can someone please clarify how exactly the confirmation process works? Is the confirmation process tied to block generation ie. 500 confirmations = 500 new blocks, or is it independent ie. a seperate function of the network that doesn't relate to the coin life cycle itself?

Thanks in advance.

I can answer my own question here, I've just updated to 2.0.6 and have been watching the number of confirmations verse the block height and can confirm (no pun intended) that with every increase in block height the confirmations increase proportionally.

On a happy note, it appears as thought the block height is now increasing about one block per minute. In the time it's taken me to check my confirmations and write this post I've watched the height go from 835744 to 835751.


Blocks are really rolling in fast all of a sudden! Updating to 2.06 now.. lets see how it goes

On my first attempt to update through the wallet the download stopped at 99%, then failed. I retried and it worked fine the second time. Hope yours goes smoothly.
sr. member
Activity: 445
Merit: 250
If so, can someone please clarify how exactly the confirmation process works? Is the confirmation process tied to block generation ie. 500 confirmations = 500 new blocks, or is it independent ie. a seperate function of the network that doesn't relate to the coin life cycle itself?

Thanks in advance.

I can answer my own question here, I've just updated to 2.0.6 and have been watching the number of confirmations verse the block height and can confirm (no pun intended) that with every increase in block height the confirmations increase proportionally.

On a happy note, it appears as thought the block height is now increasing about one block per minute. In the time it's taken me to check my confirmations and write this post I've watched the height go from 835744 to 835751.


Blocks are really rolling in fast all of a sudden! Updating to 2.06 now.. lets see how it goes
sr. member
Activity: 337
Merit: 258
If so, can someone please clarify how exactly the confirmation process works? Is the confirmation process tied to block generation ie. 500 confirmations = 500 new blocks, or is it independent ie. a seperate function of the network that doesn't relate to the coin life cycle itself?

Thanks in advance.

I can answer my own question here, I've just updated to 2.0.6 and have been watching the number of confirmations verse the block height and can confirm (no pun intended) that with every increase in block height the confirmations increase proportionally.

On a happy note, it appears as thought the block height is now increasing about one block per minute. In the time it's taken me to check my confirmations and write this post I've watched the height go from 835744 to 835751.
sr. member
Activity: 445
Merit: 250
Just a small update: my first interest payment just got confirmed and my coins started staking again. it didn't take more than 10 minutes to find the next block of almost 200 SLR....now i can see my coins back in the staking tab and it looks like they have not ''split up''.
Should they not have split up like Steve said they would? I'm confused because if they don't split up how can the network keep ''rolling''if everyone's SLR just find a block and wait for 500 confirms
sr. member
Activity: 337
Merit: 258
I've been spending the day reading up on PoST and I'd like to both confirm whether I have it right in my head now, as well as seek some clarification.

My understanding is that each coin will have a life cycle that will transition through three stages as follows:

  • Ageing - coins effectively do nothing until they earn enough age (Coin weight) to pass into the Staking phase.
  • Staking - coins of sufficient age will constantly poll the network in a bid to win the right to mine the next block.
  • Staked - coins that won the right to mine the block are held until enough confirmations allow them to be released. Upon release they lose all age and move back to the Ageing phase.

Is this correct?

If so, can someone please clarify how exactly the confirmation process works? Is the confirmation process tied to block generation ie. 500 confirmations = 500 new blocks, or is it independent ie. a seperate function of the network that doesn't relate to the coin life cycle itself?

Thanks in advance.
legendary
Activity: 1708
Merit: 1000
Solarcoin.org
member
Activity: 95
Merit: 10
Hi all, is there a way :
- to find the exact 1.5.0 nodes ?
- to deny theses 1.5.0 nodes in the next release ?
- to authorize them back after the POST staking mechanism has reached a no return point ?
Thanks for all your answers.
legendary
Activity: 1708
Merit: 1000
Solarcoin.org
Question:
What happens, when all available Spendable balances in all currently available (online) wallets go to Staking, and there are ~150-200 confirmations left before the Interest awards begin getting confirmed and coins released from Staking back to Spendable? With no Spendable left, who finds next block?

My understanding of how PoST works might not be right, but aren't the staked coins the ones doing the work? If so, it doesn't matter how many coins are in Spendable, as these are doing nothing and not contributing towards finding the next block.

That would have been my understanding, too, but it seems it's not like that - at first you have no staked coins, THEN you find a block, THEN coins go to Staking. With Spendable going down, you find a block less often. Then Spendable goes to ~0 and you find no more blocks. Didn't you notice that?

That was my understanding also TooQik, but wouldn't be the first time I was wrong... Smiley

Yes, I've noticed that too but thought it was simply how the GUI was updating the counts.

I've only earned one lot of interest (0.09...woohoo) and only after finding that block did my wallet update the Staking count but it did not reduce the Spendable count. Of my original 54,000 coins it now shows 54,000 as Spendable, 1,000 as Staked and a Total of 55,000. Obviously this is not correct as it hasn't taken the 1,000 Staked coins out of the Spendable amount.

You should have a few backups of your wallet.dat. I'd rename your current wallet to something like "wallet(test).dat" and copying over one of your backups. I'd like to see the outcome.

Sorry for the delayed reply corather.

I didn't actually have a copy of wallet.dat handy at work, so I just stopped the wallet on my work PC and restarted the wallet on my laptop at home. The laptop wallet shows the correct amounts with 53,000 as Spendable, 1,000 as Staked and a Total of 54,000. This obviously isn't the same as the test you suggested, so I'll take a copy of my wallet.dat from my laptop into work on Monday, copy over the dat file and see if the work PC wallet displays the same figures or not and post the result here.

That should work, keep copies of everything renaming the ones you aren't using also just in case. Always make multiple backups of your wallet files. If they're lost the only way to recover them is if you generated a private key while you have them.
sr. member
Activity: 377
Merit: 251
Note to self: it's not you doing it, it's us.
Quote
PoW work is different from PoS work, therefore the numbers are different. The concept is the same. The Difficulty number for PoST must be calculated (adjusted) in as similar way as the Difficulty number in PoW, so that the TARGET block rate is met under ANY conditions of the network of machines, doing the job of finding next block.

The difficulty changes yeah, but has nothing to do with the ability of finding a block in PoST. The wallets are not searching for a block they are staking their coin weight against other wallets to be considered for reward at any given time. When reward is granted the wallet hashes a difficulty to produce the hash work for the block, your not finding a block, you are given the ability to mint it and this now changes your Weight for future stakes, locked in also hence 500 Confirms. You won a block reward since your Stake met the criteria of PoST.

If the wallets online right now were just hashing at the current difficulty we would see many more blocks. If your coin weight determines your Difficulty then this still doesn't make blocks quicker since it is relative to your weight and if I had my wallet hooked up to a thousand core symmetrical processor I could just keep adding hash to my wallet and find more blocks than anyone on the network since I am Hashing and winning blocks at high Coin Weight Diff even though other wallets with normal cores can't find blocks at a low diff. See how it just can't work that way?

None of what you say is my task to understand as a system tester.
The question I asked was this:
"In PoW mining, the feedback that maintains the 1 minute target is achieved by varying the difficulty according to the hashpower currently working on that blockchain.
In the current PoST implementation we have, what is the feedback used to maintain the target block rate?"

Steve's answer was this : "Same concept in PoS.  The difficulty is adjusted."

Then what is your answer? What is the feedback used to maintain the target block rate?

It is 60 blocks an hour, the difficulty is produced by the network to match this rate as Coin Weight. Not externally by hash. If everyone has their coin locked up staking and coin age requirements are not met and I don't think anyone can generate a block. Well Vericoin is situated at 60 per hour so this will work itself out when the network reaches equilibrium.

Now I don't see your answer to my question any different from Steve's answer. What happened? And who is ever talking external hash here? Am I dumb? No, I am not.
There are still many spendable staking coins in many wallets - everyone here says that.
I have 5 wallets on 2.0.5 (11% of all, I guess?)
I have no wallets on 1.5, but know of 2 wallets on 1.5, but these two 1.5 wallets I know of have ZERO balances in them. Oh, I am sorry, hope goes down I guess...by 10% !
In my five 2.0.5 wallets running with the sole purpose to INCREASE the number of staking nodes, most of the balances have already staked, BUT there are still 40000-50000 SLR "staking". With fewer and fewer coins to stake, they should be staking at the same rate as when there were more coins to stake. But the fact is, the rate goes down. And the other fact is: the initial rate, as well as the highest rate achieved so far, were nowhere close to the target.

If there is a feedback mechanism in place, it's either not working properly, or it's not set up properly.
legendary
Activity: 987
Merit: 1003
Quote
PoW work is different from PoS work, therefore the numbers are different. The concept is the same. The Difficulty number for PoST must be calculated (adjusted) in as similar way as the Difficulty number in PoW, so that the TARGET block rate is met under ANY conditions of the network of machines, doing the job of finding next block.

The difficulty changes yeah, but has nothing to do with the ability of finding a block in PoST. The wallets are not searching for a block they are staking their coin weight against other wallets to be considered for reward at any given time. When reward is granted the wallet hashes a difficulty to produce the hash work for the block, your not finding a block, you are given the ability to mint it and this now changes your Weight for future stakes, locked in also hence 500 Confirms. You won a block reward since your Stake met the criteria of PoST.

If the wallets online right now were just hashing at the current difficulty we would see many more blocks. If your coin weight determines your Difficulty then this still doesn't make blocks quicker since it is relative to your weight and if I had my wallet hooked up to a thousand core symmetrical processor I could just keep adding hash to my wallet and find more blocks than anyone on the network since I am Hashing and winning blocks at high Coin Weight Diff even though other wallets with normal cores can't find blocks at a low diff. See how it just can't work that way?

None of what you say is my task to understand as a system tester.
The question I asked was this:
"In PoW mining, the feedback that maintains the 1 minute target is achieved by varying the difficulty according to the hashpower currently working on that blockchain.
In the current PoST implementation we have, what is the feedback used to maintain the target block rate?"

Steve's answer was this : "Same concept in PoS.  The difficulty is adjusted."

Then what is your answer? What is the feedback used to maintain the target block rate?

It is 60 blocks an hour, the difficulty is produced by the network to match this rate as Coin Weight. Not externally by hash. If everyone has their coin locked up staking and coin age requirements are not met and I don't think anyone can generate a block. Well Vericoin is situated at 60 per hour so this will work itself out when the network reaches equilibrium.
sr. member
Activity: 308
Merit: 250
truth=(true?true:false);
All,

The block explorer on CryptoID should be working soon.  I have pushed the fix for it, and will be pushing 2.0.6 later tonight.  (It's just a maintenance release. No new features like 10,000% interest or anything.)  Wink

Current block height is 835709.  We're moving along, despite the 21 1.5 nodes that are not staking.  Yay

Note:  In a non-capped-interest model of PoST, the folks that are staking would be seeing very nice interest payments with the low network stake weight.  But, ours is capped at 10% until block height 836213 when the interest rate will drop to a 2% cap.


-Steve
sr. member
Activity: 377
Merit: 251
Note to self: it's not you doing it, it's us.
Quote
PoW work is different from PoS work, therefore the numbers are different. The concept is the same. The Difficulty number for PoST must be calculated (adjusted) in as similar way as the Difficulty number in PoW, so that the TARGET block rate is met under ANY conditions of the network of machines, doing the job of finding next block.

The difficulty changes yeah, but has nothing to do with the ability of finding a block in PoST. The wallets are not searching for a block they are staking their coin weight against other wallets to be considered for reward at any given time. When reward is granted the wallet hashes a difficulty to produce the hash work for the block, your not finding a block, you are given the ability to mint it and this now changes your Weight for future stakes, locked in also hence 500 Confirms. You won a block reward since your Stake met the criteria of PoST.

If the wallets online right now were just hashing at the current difficulty we would see many more blocks. If your coin weight determines your Difficulty then this still doesn't make blocks quicker since it is relative to your weight and if I had my wallet hooked up to a thousand core symmetrical processor I could just keep adding hash to my wallet and find more blocks than anyone on the network since I am Hashing and winning blocks at high Coin Weight Diff even though other wallets with normal cores can't find blocks at a low diff. See how it just can't work that way?

None of what you say is my task to understand as a system tester.
The question I asked was this:
"In PoW mining, the feedback that maintains the 1 minute target is achieved by varying the difficulty according to the hashpower currently working on that blockchain.
In the current PoST implementation we have, what is the feedback used to maintain the target block rate?"

Steve's answer was this : "Same concept in PoS.  The difficulty is adjusted."

Then what is your answer? What is the feedback used to maintain the target block rate?
legendary
Activity: 1736
Merit: 1001
i have 493 confirmations so far on my oldest block.
sr. member
Activity: 406
Merit: 250


Can you share some peer ip?

solarcoind getpeerinfo would show some connected nodes.

Is this what you mean?

Quote
addnode=104.156.228.67
addnode=106.188.22.137
addnode=108.31.36.59
addnode=118.209.221.45
addnode=118.211.7.75
addnode=121.98.129.219
addnode=150.101.243.74
addnode=154.20.130.233
addnode=162.243.214.120
addnode=173.57.196.254
addnode=174.57.197.124
addnode=178.112.239.229
addnode=188.165.2.147
addnode=196.210.245.72
addnode=197.41.90.186
addnode=209.181.66.82
addnode=213.91.205.134
addnode=216.185.251.142
addnode=217.42.146.185
addnode=221.149.128.187
addnode=222.237.39.100
addnode=24.184.117.70
addnode=46.251.113.106
addnode=5.165.97.22
addnode=50.153.144.128
addnode=67.170.32.46
addnode=67.86.46.74
addnode=68.132.65.5
addnode=69.112.174.140
addnode=70.192.209.165
addnode=71.189.135.188
addnode=73.10.58.144
addnode=73.148.161.32
addnode=73.196.136.61
addnode=77.100.195.205
addnode=78.83.197.46
addnode=85.27.20.109
addnode=87.212.116.150
addnode=88.10.65.24
addnode=89.215.107.204
addnode=92.135.210.229
addnode=95.172.230.204
addnode=95.172.237.11
addnode=96.44.66.168
addnode=96.49.13.206
addnode=98.255.195.184
addnode=99.184.252.232

I pulled this from here: https://chainz.cryptoid.info/slr/#!network by clicking on the Version 2.0.5 "Node List" button.
legendary
Activity: 987
Merit: 1003
Quote
PoW work is different from PoS work, therefore the numbers are different. The concept is the same. The Difficulty number for PoST must be calculated (adjusted) in as similar way as the Difficulty number in PoW, so that the TARGET block rate is met under ANY conditions of the network of machines, doing the job of finding next block.

The difficulty changes yeah, but has nothing to do with the ability of finding a block in PoST. The wallets are not searching for a block they are staking their coin weight against other wallets to be considered for reward at any given time. When reward is granted the wallet hashes a difficulty to produce the hash work for the block, your not finding a block, you are given the ability to mint it and this now changes your Weight for future stakes, locked in also hence 500 Confirms. You won a block reward since your Stake met the criteria of PoST.

If the wallets online right now were just hashing at the current difficulty we would see many more blocks. If your coin weight determines your Difficulty then this still doesn't make blocks quicker since it is relative to your weight and if I had my wallet hooked up to a thousand core symmetrical processor I could just keep adding hash to my wallet and find more blocks than anyone on the network since I am Hashing and winning blocks at high Coin Weight Diff even though other wallets with normal cores can't find blocks at a low diff. See how it just can't work that way?
legendary
Activity: 1456
Merit: 1006
Mining Pool Hub
What is the official latest blockchain's current height?

I'm running v2.0.6.0 and still at 830120
v1.0.5 wallet is at 844355.
https://chainz.cryptoid.info/slr/ is showing 835000

Is there any official block explorer?

835707 is what my 2.0.5 wallets show. I guess since the official block explorer has not been fixed yet, 835707 is unofficial.

Can you share some peer ip?

solarcoind getpeerinfo would show some connected nodes.
sr. member
Activity: 377
Merit: 251
Note to self: it's not you doing it, it's us.
What is the official latest blockchain's current height?

I'm running v2.0.6.0 and still at 830120
v1.0.5 wallet is at 844355.
https://chainz.cryptoid.info/slr/ is showing 835000

Is there any official block explorer?

835707 is what my 2.0.5 wallets show. I guess since the official block explorer has not been fixed yet, 835707 is unofficial.
Jump to: