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

[MakeBelieve]

Now I understand why staking hasn't kicked in yet, wallet is just waiting for the hardfork.

You can start staking now with this small branch-update (that will not make it to github).

Windows
https://drive.google.com/file/d/0B8rWObF4xz1YcExqWWZkYVZsLU0/view?usp=sharing

OS X
https://drive.google.com/file/d/0B8rWObF4xz1YdFRUQUtCZTJWSDg/view?usp=sharing


This is version 1.0.4.0x (not going into the github source tree) corresponds to the following 1-line change:

Code:

diff --git a/src/wallet.cpp b/src/wallet.cpp
index df01923..6b2501d 100644
--- a/src/wallet.cpp
+++ b/src/wallet.cpp
@@ -2633,7 +2633,7 @@ bool CWallet::CreateCoinStake(const CKeyStore& keystore, u
 
         if (nReward <= 0) {
               printf("CreateCoinStake: Reward is 0.\n");
-              return false;
+              // return false;
         }
 
         nCredit += nReward;

PLEASE READ:

This allows your wallet to accept 0 reward PoS blocks that you mint yourself.

It's untested. The rest of the network should accept the block, but I haven't checked the code for that yet.

If you mint blocks and they don't get accepted, it means this patch doesn't work the way I hope and you will need to rescan and resync.

This is just a hack for those who want to get going with turbo early. Do not use if you don't know what you are doing.

Please don't use this patch if you have not split your stake into many many transactions. If you only have one or two, it is better to wait 7 hours and use the main branch update (1.0.4.0).

After the true 1.0.4.0 fork goes live, you will want to change back to the main-branch client.

Please post your results here to help me monitor the network.

nevermind

[1714111451]

1714111451

[1714111451]

1714111451

[1714111451]

1714111451

[1714111451]

1714111451

[findyou1337]

i have a problem , when i open the wallet all works fine , and he stakes , but after 10 minutes the conecction to synergy network lost .

[daveolake]

Now I understand why staking hasn't kicked in yet, wallet is just waiting for the hardfork.

You can start staking now with this small branch-update (that will not make it to github).

Windows
https://drive.google.com/file/d/0B8rWObF4xz1YcExqWWZkYVZsLU0/view?usp=sharing

OS X
https://drive.google.com/file/d/0B8rWObF4xz1YdFRUQUtCZTJWSDg/view?usp=sharing


This is version 1.0.4.0x (not going into the github source tree) corresponds to the following 1-line change:

Code:

diff --git a/src/wallet.cpp b/src/wallet.cpp
index df01923..6b2501d 100644
--- a/src/wallet.cpp
+++ b/src/wallet.cpp
@@ -2633,7 +2633,7 @@ bool CWallet::CreateCoinStake(const CKeyStore& keystore, u
 
         if (nReward <= 0) {
               printf("CreateCoinStake: Reward is 0.\n");
-              return false;
+              // return false;
         }
 
         nCredit += nReward;

PLEASE READ:

This allows your wallet to accept 0 reward PoS blocks that you mint yourself.

It's untested. The rest of the network should accept the block, but I haven't checked the code for that yet.

If you mint blocks and they don't get accepted, it means this patch doesn't work the way I hope and you will need to rescan and resync.

This is just a hack for those who want to get going with turbo early. Do not use if you don't know what you are doing.

Please don't use this patch if you have not split your stake into many many transactions. If you only have one or two, it is better to wait 7 hours and use the main branch update (1.0.4.0).

After the true 1.0.4.0 fork goes live, you will want to change back to the main-branch client.

Please post your results here to help me monitor the network.

worked for me. turbostaked for an hour up to 26x then stoped .. last 20 min 0x 0 amount.

[Grandpa Jones]

I keep losing all my connections.  What is the .conf name, Synergycoin synergyCoin?

I think a lot of people are trying to stake with the 1.0.4.0x update I put up.

I didn't test it. The "x" is for experimental. I think the experimental update is putting out incorrect blocks.

Everyone should just revert to the official build with the links at the OP, delete peers.dat, the tor directory, and resync their chains.

It will be best to wait for the official fork to kick in.

I did mention this was untested and to only use it if you knew what you were doing. I did not get any feedback so I could monitor the network.

[MakeBelieve]

I am using the experimental and it is staking- can i continue or should i use the wallet in the OP

[Grandpa Jones]

I am using the experimental and it is staking- can i continue or should i use the wallet in the OP

Don't use it. That experiment failed.

It was not tested as I mentioned in the post.

You didn't do anything but waste time. Sorry about that. You haven't lost any coin age, but you will have to wait for the "official" fork.

The good news is that the chain didn't advance much, so you actually did better with this experiment blowing up the network than otherwise.

Please stop your client, delete blk0001.dat, db.log, database, txleveldb, peers.dat, and tor and then restart with the client from the OP.

Also, it would be a good idea to add rescan=1 to your conf.

[Grandpa Jones]

If you see an alert and have updated to the "experimental" build described here: https://bitcointalk.org/index.php?topic=1070124.msg11498383#msg11498383

Please stop your client, delete blk0001.dat, db.log, database, txleveldb, peers.dat, and tor and then restart with the client from the OP.

If you are already on build 1.0.4.0 and didn't upgrade to the "experimental" build, then don't do anything if your block count is close to 4326 as of the time of this post.

4326 correct hash is: 66fb1e13a9b7584b8ff04282df675c137ea5c31dbe7f85b9939c76267243c422

[Digital_Currency_LTD]

Just bought some on yobit and waiting for staking...

[animalroam]

CryptoBE has updated their version two hours ago.

[Dexter12]

Just bought some on yobit and waiting for staking...

If you just bought them you have to wait 2 days for them to mature.

[NoobKidOnTheBlock]

If you see an alert and have updated to the "experimental" build described here: https://bitcointalk.org/index.php?topic=1070124.msg11498383#msg11498383

Please stop your client, delete blk0001.dat, db.log, database, txleveldb, peers.dat, and tor and then restart with the client from the OP.

If you are already on build 1.0.4.0 and didn't upgrade to the "experimental" build, then don't do anything if your block count is close to 4326 as of the time of this post.

4326 correct hash is: 66fb1e13a9b7584b8ff04282df675c137ea5c31dbe7f85b9939c76267243c422

I just used the version 1.0.4.0 from the OP and didn't bother with the experimental build so I don't need to do anything then right? My chain is currently on block 4406 is that roughly where everyone else is right now?

[MakeBelieve]

i did those steps--is there a way to identify if it is correct

[Grandpa Jones]

I just used the version 1.0.4.0 from the OP and didn't bother with the experimental build so I don't need to do anything then right? My chain is currently on block 4406 is that roughly where everyone else is right now?

You look to be on a bad chain. You will want to resync.

Please stop your client, delete blk0001.dat, db.log, database, txleveldb, peers.dat, and tor and then restart with the client from the OP.

i did those steps--is there a way to identify if it is correct

Yes. The best chain (the one most clients will accept) at the moment I write this is at 4343.

Go to your console and do 'getblockbynumber 4343' and look for the hash at the top. It should start with "852014c".

Code:

{
    "hash" : "852014c103e2cc579c07e4468e67066c2f7b6ef51d51962187554eecfb6ff147",
    "confirmations" : 1,
    "size" : 442,
    "height" : 4343,
    "version" : 6,
    "merkleroot" : "6c0b87d7fd4ceb99237a9b268e53164a8c7c293663bef09d005fb3421fac9bc7",
    "mint" : 24.27374200,
    "time" : 1433107254,
    "nonce" : 0,
    "bits" : "203fffff",
    "difficulty" : 0.00000000,
    "blocktrust" : "4",
    "chaintrust" : "83100c07f1304",
    "previousblockhash" : "628cd71a7de7e2c7e6771875f4e9893c423e6141f7ae3272d907976ed0b0c6b8",
    "flags" : "proof-of-stake",
    "proofhash" : "41c1f03fbfa61808ad0cabba35e5965ceee4823aaf0cfeaea3326f5367b5f72d",
    "entropybit" : 1,
    "modifier" : "55b489d5d0359c89",
    "modifierchecksum" : "421162ee",
    "tx" : [
        "a7d2520004a2552f6036be05ba8f4ec5b1d3e16b77c014b3f057a10886bf169a",
        "dffd9ba8616d45aceba5917db7d54dac8c628111797a14b240d85f753b775bc1"
    ],
    "signature" : "304302203b324ffad7c8ffa5733a508a374a8d25297dc958dbacdbbf5003995cbf49e437021f474e0d6bb7458d79e56d3f38664f2a3d629322193e794a2ab144ac4ce70d31"
}

[Grandpa Jones]

CryptoBE has updated their version two hours ago.

The web front end seems to be stuck at 4168.

They probably will need to resync as I have described.

[OVRGRO]

i've reset and deleted several times... keeps taking me up to block 440x

[NoobKidOnTheBlock]

CryptoBE has updated their version two hours ago.

The web front end seems to be stuck at 4168.

They probably will need to resync as I have described.

Well my version 1.0.4.0 is on block 4406 from what I can tell so I hope that means I'm on the right chain and good to go

[Dexter12]

CryptoBE has updated their version two hours ago.

The web front end seems to be stuck at 4168.

They probably will need to resync as I have described.

Well my version 1.0.4.0 is on block 4406 from what I can tell so I hope that means I'm on the right chain and good to go

No, you seem to be on the wrong chain, we are at block 4353 right now.

[Grandpa Jones]

i've reset and deleted several times... keeps taking me up to block 440x

Well my version 1.0.4.0 is on block 4406 from what I can tell so I hope that means I'm on the right chain and good to go

I'm not confident that all peers will take that chain, I know it's floating around out there.

Let me see if I can sync an experimental client to it and see what's happening with it.


Edit:

I had an experimental client synced to it already. It's a dead chain. See if you can get on ours. If not. Just wait it out. We'll pass that chain in about 1.5 hours.

[Dexter12]

i've reset and deleted several times... keeps taking me up to block 440x

Delete the whole order except your wallet.dat and resync... i ve done it once and it worked out for me.

[MakeBelieve]

I am on 4354 and i did "getblockbynumber 4343" and it was correct -- spectacular