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

[Grandpa Jones]

also--do the log files i am posting have info that i need to delete?

You could stop your client, delete the onion folder in your app directory and restart. Your onion address from your log is cqqiid4l4z3cscl4.onion.

[1713918715]

1713918715

[MakeBelieve]

ok-- i deleted it and restarted -- do i need to add the address you posted back in?

[Grandpa Jones]

np--- is it everyone or me?

It's everyone. A lucky few got a first stake and that's all they needed to not be effected by this bug. It's an integer division issue. It comes down to the following equation being 0 by integer division:

1 * 288 * 5 / (anything bigger than 1440)

So if there were more than 1440 blocks in the previous day, your reward is 0. If so, your wallet rejects the mint and tries again.

1 in the above equation refers to the number of mints in the last 24 hours, which includes the one your wallet is attempting.

[MakeBelieve]

or-- would it be better to transfer the wallet.dat file to a windows machine and delete the mac wallet completely?

[MakeBelieve]

I guess the big question I have is this--- I put a lot of time and money into getting a lot of coins, how do I keep from getting screwed on this deal since I cannot stake while everyone else stakes away?

[Grandpa Jones]

I guess the big question I have is this--- I put a lot of time and money into getting a lot of coins, how do I keep from getting screwed on this deal since I cannot stake while everyone else stakes away?

Everyone else isn't staking away. Only a few addresses. It's only going to be 36 more hours.

If I would have gotten some debug.logs earlier, I could have nailed this. You are the first one who got one to me. I asked 36 hours ago.

But you aren't going to get screwed. The fact that a dev is on problems like this helps your value more than staking would.

And trust me I'm on it.

[MakeBelieve]

I guess the big question I have is this--- I put a lot of time and money into getting a lot of coins, how do I keep from getting screwed on this deal since I cannot stake while everyone else stakes away?

Everyone else isn't staking away. Only a few addresses. It's only going to be 36 more hours.

If I would have gotten some debug.logs earlier, I could have nailed this. You are the first one who got one to me. I asked 36 hours ago.

But you aren't going to get screwed. The fact that a dev is on problems like this helps your value more than staking would.

And trust me I'm on it.

I applaud your work, but isn't the Turbo Stake only going to last 30 days - so these days and hours do add up...

[Grandpa Jones]

I guess the big question I have is this--- I put a lot of time and money into getting a lot of coins, how do I keep from getting screwed on this deal since I cannot stake while everyone else stakes away?

Everyone else isn't staking away. Only a few addresses. It's only going to be 36 more hours.

If I would have gotten some debug.logs earlier, I could have nailed this. You are the first one who got one to me. I asked 36 hours ago.

But you aren't going to get screwed. The fact that a dev is on problems like this helps your value more than staking would.

And trust me I'm on it.

I applaud your work, but isn't the Turbo Stake only going to last 30 days - so these days and hours do add up...

They do add up. But the base rate is 10%, so the per-day interest is not very high, even with the max Turbo Stake.

I hate to say it, but these are some of the problems with new code. This isn't a straight clone.

[SockPuppetAccount]

Well, only a few addresses staking away for another 36 hours, especially when POW is over does kinda screw over a lot of people.  Those few addresses will get to start out staking with multipliers in the triple digit range since they will be staking all the blocks.  Still got about 14 hours til POW ends.  Any hope of pushing the update sooner so we all at least start out POS period on semi-equal footing rather than having to sit back and watch those few address rape us for a day and a half?

EDIT:  Theoretical example, one of those lucky addresses could easily stake 250 blocks in the upcoming 36 hours + last 12 hours.  He now has a multiplier of 250x.  Which translates into 2500% annually or 6.84% daily.  Not an insignificant headstart, especially for an already large holder.

[Grandpa Jones]

Well, only a few addresses staking away for another 36 hours, especially when POW is over does kinda screw over a lot of people.  Those few addresses will get to start out staking with multipliers in the triple digit range since they will be staking all the blocks.  Still got about 14 hours til POW ends.  Any hope of pushing the update sooner so we all at least start out POS period on semi-equal footing rather than having to sit back and watch those few address rape us for a day and a half?

The quicker the fork, the more risky. I can put it out for 14 hours from now.

That's probably the fastest I'd want to do.

I'll push the new time to github. If the network blows up, we'll know who to blame.

Edit: The time to go live is 7 PM Eastern.

Builds coming soon.

[SockPuppetAccount]

Well, only a few addresses staking away for another 36 hours, especially when POW is over does kinda screw over a lot of people.  Those few addresses will get to start out staking with multipliers in the triple digit range since they will be staking all the blocks.  Still got about 14 hours til POW ends.  Any hope of pushing the update sooner so we all at least start out POS period on semi-equal footing rather than having to sit back and watch those few address rape us for a day and a half?

The quicker the fork, the more risky. I can put it out for 14 hours from now.

That's probably the fastest I'd want to do.

I'll push the new time to github. If the network blows up, we'll know who to blame.

I will take the blame!  I'd like to believe you are an honest guy who just ran into a few bugs that you didn't catch in testing.  Mainly because the 2 bugs you did find make perfect sense for bugs that would evade detection during testing when ya think about them.

Just hate to see the coin start off with a nasty stain on it's history.  You know how the FUD brigade never let's a coin live anything down.

[Grandpa Jones]

I will take the blame!  I'd like to believe you are an honest guy who just ran into a few bugs that you didn't catch in testing.  Mainly because the 2 bugs you did find make perfect sense for bugs that would evade detection during testing when ya think about them.

Just hate to see the coin start off with a nasty stain on it's history.  You know how the FUD brigade never let's a coin live anything down.

That's going to happen to many coins.

Here's where I first asked for debug.logs:

https://bitcointalk.org/index.php?topic=1070124.msg11482503#msg11482503

No one sent one to me. I could have nailed this if they had, seriously.

[MakeBelieve]

I will take the blame!  I'd like to believe you are an honest guy who just ran into a few bugs that you didn't catch in testing.  Mainly because the 2 bugs you did find make perfect sense for bugs that would evade detection during testing when ya think about them.

Just hate to see the coin start off with a nasty stain on it's history.  You know how the FUD brigade never let's a coin live anything down.

That's going to happen to many coins.

Here's where I first asked for debug.logs:

https://bitcointalk.org/index.php?topic=1070124.msg11482503#msg11482503

No one sent one to me. I could have nailed this if they had, seriously.

I do remember you asking, but i also recall it being "fixed" - therefore logs would no longer be required-- that is why you did not get them---

As mentioned in the example by SockPuppets - 7% daily on those staking is significant - i think I read that someone with 25,000 coins is staking currently-- that person will stake more in a day than most people have ---

[Grandpa Jones]

That's going to happen to many coins.

Here's where I first asked for debug.logs:

https://bitcointalk.org/index.php?topic=1070124.msg11482503#msg11482503

No one sent one to me. I could have nailed this if they had, seriously.

I do remember you asking, but i also recall it being "fixed" - therefore logs would no longer be required-- that is why you did not get them---

As mentioned in the example by SockPuppets - 7% daily on those staking is significant - i think I read that someone with 25,000 coins is staking currently-- that person will stake more in a day than most people have ---

Here's where I said I found the problem: https://bitcointalk.org/index.php?topic=1070124.msg11483383#msg11483383

That was 2 hours for someone to get me a log file. No one did.

I'm not blaming anyone here, just saying that this is a two way street. The more involved a community is, the better the coin.

The guys who got a stake in early do have an advantage, but really, even 10% of 1% of the cap is about 0.02 BTC right now. That's really not much.

I'm here to fix this coin and make it work. All big coins have problems early on. The coins that never get big are the ones where the devs run away from problems.

[iqlimasyadiqa]

hi guys , this is right ?

{
"enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 0.00000001,
"search-interval" : 1,
"weight" : 236,
"netstakeweight" : 13,
"expectedtime" : 6
}


expected time 6 second to earn reward , and i see already some hour still 6 second , ad i not received reward

[SockPuppetAccount]

That's going to happen to many coins.

Here's where I first asked for debug.logs:

https://bitcointalk.org/index.php?topic=1070124.msg11482503#msg11482503

No one sent one to me. I could have nailed this if they had, seriously.

I do remember you asking, but i also recall it being "fixed" - therefore logs would no longer be required-- that is why you did not get them---

As mentioned in the example by SockPuppets - 7% daily on those staking is significant - i think I read that someone with 25,000 coins is staking currently-- that person will stake more in a day than most people have ---

Here's where I said I found the problem: https://bitcointalk.org/index.php?topic=1070124.msg11483383#msg11483383

That was 2 hours for someone to get me a log file. No one did.

I'm not blaming anyone here, just saying that this is a two way street. The more involved a community is, the better the coin.

The guys who got a stake in early do have an advantage, but really, even 10% of 1% of the cap is about 0.02 BTC right now. That's really not much.

I'm here to fix this coin and make it work. All big coins have problems early on. The coins that never get big are the ones where the devs run away from problems.

By the time I saw the call for debug logs for the first bug, was when you said you already found the problem.  By the time I saw you working on the second bug, MakeBelieve was already posting his debug file.  I would have tried to help if I had saw it in time.

Can't win with this line of thinking, on either side though.  Investors buy coins, withdrawal them to stake, and go AFK because they are just investors, not devs.  Devs are treated like slave labor and called scammers for daring to profit off their work, and when they ask for help monetarily or with technical stuff, no one wants to pitch in.

EDIT:  Anyway, don't worry about all that.  Just prioritize pushing the fork to align with the end of POW as closely as possible to avoid FUD!  Get to work slave!  

[Grandpa Jones]

By the time I saw the call for debug logs for the first bug, was when you said you already found the problem.  By the time I saw you working on the second bug, MakeBelieve was already posting his debug file.  I would have tried to help if I had saw it in time.

Can't win with this line of thinking, on either side though.  Investors buy coins, withdrawal them to stake, and go AFK because they are just investors, not devs.  Devs are treated like slave labor and called scammers for daring to profit off their work, and when they ask for help monetarily or with technical stuff, no one wants to pitch in.

EDIT:  Anyway, don't worry about all that.  Just prioritize pushing the fork to align with the end of POW as closely as possible to avoid FUD!  Get to work slave!  

You got it. I'm resisting the urge to expand on your analysis. In lieu of that:


HARD FORK 1.0.4.0

Github has been updated.

Downloads on OP.

You have less than 14 hours to get updated!

DO NOT TRANSFER COINS TO OR FROM EXCHANGES UNTIL WE CONFIRM THEY HAVE UPDATED!

[Grandpa Jones]

ok-- i deleted it and restarted -- do i need to add the address you posted back in?

No. You have a new onion address now. Enjoy your new identity.

[Grandpa Jones]

hi guys , this is right ?

{
"enabled" : true,
"staking" : true,
"errors" : "",
"currentblocksize" : 1000,
"currentblocktx" : 0,
"pooledtx" : 0,
"difficulty" : 0.00000001,
"search-interval" : 1,
"weight" : 236,
"netstakeweight" : 13,
"expectedtime" : 6
}


expected time 6 second to earn reward , and i see already some hour still 6 second , ad i not received reward

Update to the new client. It should fix your problem when the fork kicks in less than 14 hours from now.

[ocminer]

Updated to 1.0.4.0