[SNRG] 🔥 Synergy 🔥 Cloud.Synergycoin.com Cloud Bot Now Live!! 🔥

[MakeBelieve]

This is the problem with not testing adequately.  Now there is a situation where there are 30 days of Turbo Stake and not everyone is staking because of improper testing before release--

Now there will be some that are staking correctly while others are not, which then defeats the purpose of the coin in preventing some people from having an advantage over others--

Dev, is your wallet staking correctly?

[1713281372]

1713281372

[1713281372]

1713281372

[Cryptophile]

I staked a block of around 1500 less than 12 hours ago.  No issues here.

[NoobKidOnTheBlock]

I staked a block of around 1500 less than 12 hours ago.  No issues here.

Hmmm that's weird that it is working for some but not working for a lot of other people which is hurting my turbo staking chances as it stands right now I hope that we can figure this problem out soon so I can start receiving rewards

[Grandpa Jones]

This is the problem with not testing adequately.  Now there is a situation where there are 30 days of Turbo Stake and not everyone is staking because of improper testing before release--

Now there will be some that are staking correctly while others are not, which then defeats the purpose of the coin in preventing some people from having an advantage over others--

Dev, is your wallet staking correctly?

We did indeed test extensively on two different platforms, three different staking nodes, and about 5 nodes total. We restarted the test net about 5 or 6 times and let it run completely through an abbreviated PoW period at least twice. Only a few parameters change between the test net and main net: 1. Maturation times, 2. The stake modifier interval, 3. Minimum PoS difficulty.

...

As I write this response I have found the issue. The minimum difficulty is too high for the coin count. We wouldn't have seen this in the test net because the coins were divided among only 3 staking nodes, so each had a large number of coins given the total supply.

We'll get out a fix ASAP. It will cause a fork, so we'll get the exchanges updated first and then put out a release. Those who do not update will get left on the fork. Thanks for reporting your problems. This is why having an active community is good for a coin.

On the upside, everyone has been operating under the same difficulty so these problems have been fair to all. You can get an advantage in the forthcoming update by upgrading earlier than your competitors.

Rest assured that we are on this and will push the change to github very soon and get the exchanges updated as fast as we can.

Please also accept our apologies for your frustrations. As crypto users ourselves, we know how maddening these type of wallet issues can be.

[NoobKidOnTheBlock]

This is the problem with not testing adequately.  Now there is a situation where there are 30 days of Turbo Stake and not everyone is staking because of improper testing before release--

Now there will be some that are staking correctly while others are not, which then defeats the purpose of the coin in preventing some people from having an advantage over others--

Dev, is your wallet staking correctly?

We did indeed test extensively on two different platforms, three different staking nodes, and about 5 nodes total. We restarted the test net about 5 or 6 times and let it run completely through an abbreviated PoW period at least twice. Only a few parameters change between the test net and main net: 1. Maturation times, 2. The stake modifier interval, 3. Minimum PoS difficulty.

...

As I write this response I have found the issue. The minimum difficulty is too high for the coin count. We wouldn't have seen this in the test net because the coins were divided among only 3 staking nodes, so each had a large number of coins given the total supply.

We'll get out a fix ASAP. It will cause a fork, so we'll get the exchanges updated first and then put out a release. Those who do not update will get left on the fork. Thanks for reporting your problems. This is why having an active community is good for a coin.

On the upside, everyone has been operating under the same difficulty so these problems have been fair to all. You can get an advantage in the forthcoming update by upgrading earlier than your competitors.

Rest assured that we are on this and will push the change to github very soon and get the exchanges updated as fast as we can.

Please also accept our apologies for your frustrations. As crypto users ourselves, we know how maddening these type of wallet issues can be.

Hey no worries as long as the updated wallet gets loaded to the OP and everything is fixed then I'm okay with that shiat! At least you guys are working hard to make sure that everything is working alright which is very nice to see

[OVRGRO]

we talked late last night on yobit dev... obviously waiting on that linux compile, but thanks for being on top of this as i'm stakeless in seattle as well lol. buy up some cheap snrg before the fix hits 

[Grandpa Jones]

Github has been updated. Please do not update your builds yet if you plan to stake because the network will reject stake with the new lower limits.

We have asked the exchanges and block explorer host to reply when they have upgraded. Once upgraded, we will push out new builds for users.

[Grandpa Jones]

Bleutrade has upgraded. One down, 2 to go.

[NoobKidOnTheBlock]

Github has been updated. Please do not update your builds yet if you plan to stake because the network will reject stake with the new lower limits.

We have asked the exchanges and block explorer host to reply when they have upgraded. Once upgraded, we will push out new builds for users.

You will post the link to the updated wallet for windows on the OP as well right? I just don't know how to compile my own wallets just yet lol

[buddynuno]

Github has been updated. Please do not update your builds yet if you plan to stake because the network will reject stake with the new lower limits.

We have asked the exchanges and block explorer host to reply when they have upgraded. Once upgraded, we will push out new builds for users.

Ok so my guess is once we update the wallet we need to wait another 48 hours to start staking again?

[OVRGRO]

Ok so my guess is once we update the wallet we need to wait another 48 hours to start staking again?

not unless you moved your coins...

[daveolake]

Having same issue. saw the twitter post im in. SNj6YATSJ2v3qkg8jHFPf3Dz4J9oxZBbnB tweeting now. good to see you are on the fix. good work

[Grandpa Jones]

Github has been updated. Please do not update your builds yet if you plan to stake because the network will reject stake with the new lower limits.

We have asked the exchanges and block explorer host to reply when they have upgraded. Once upgraded, we will push out new builds for users.

Ok so my guess is once we update the wallet we need to wait another 48 hours to start staking again?

No. Absolutely not. You do not lose any coin age with this update. Upgrade and start staking. If you have mature coins, they will stake pretty soon, after the diff drops.

We changed only the limit, the actual diff has to fall after retargeting, which happens every block.

But your weight will not start over. You can calculate how much time you lost by looking at the age of your stake and subtracting 48 hours from the time it mints. I don't think it's going to be too bad for most people, maybe 1 day. There has been a slight advantage for those with more coins, but it will probably be balanced out by the movement of coins to the exchanges to dump in light of these issues.

[buddynuno]

Dev, have you updated the wallet to the newest version in the OP?

[Grandpa Jones]

Dev, have you updated the wallet to the newest version in the OP?

No. We will make an announcement. It may take 1-4 hours. We want to get it out ASAP, but, for example, I don't have console access to my usual build machines right now. I either have to make a special trip to them or see if I can build on a different machine that I can access where I am.

[Grandpa Jones]

Dev, have you updated the wallet to the newest version in the OP?

No. We will make an announcement. It may take 1-4 hours. We want to get it out ASAP, but, for example, I don't have console access to my usual build machines right now. I either have to make a special trip to them or see if I can build on a different machine that I can access where I am.

Qt downloads have been paused until a new build is put together.

If you upgraded by git after the last announcement, please upgrade again (which reverted the changes).

We will have a full update in about 9 hours. Keep staking, you may hit a block.

[NoobKidOnTheBlock]

Dev, have you updated the wallet to the newest version in the OP?

No. We will make an announcement. It may take 1-4 hours. We want to get it out ASAP, but, for example, I don't have console access to my usual build machines right now. I either have to make a special trip to them or see if I can build on a different machine that I can access where I am.

Qt downloads have been paused until a new build is put together.

If you upgraded by git after the last announcement, please upgrade again (which reverted the changes).

We will have a full update in about 9 hours. Keep staking, you may hit a block.

Ok as long as you have an updated windows qt wallet when you update this all that would be nice Thanks

[megadestruct61]

Well now I see why my 2 seconds estimate to find a block isn't coming true.  Hope they get this fixed soon right now its more like turtle staking then turbo 

[Grandpa Jones]

Ok as long as you have an updated windows qt wallet when you update this all that would be nice Thanks

We will. We were going to rush out an update, but decided it would be a mistake. It's better if it were done right, which will take some time.

Well now I see why my 2 seconds estimate to find a block isn't coming true.  Hope they get this fixed soon right now its more like turtle staking then turbo  

Turbo refers to the rewards, but yes, we see your point. We'll try to be as expedient as possible getting out the update. But we'd rather not rush it.

[jerowacik]

whats next ?

i see many dump argg