[KGC] The future is krugercoin and the future is now! [Official Launch] - page 17.

Nibiru

full member

Activity: 224

Merit: 100

Krugercoin [KGC]

Quote from: MinersPoolEU on March 09, 2014, 06:32:56 PM

Quote from: UniMatrixZ on March 09, 2014, 06:29:56 PM

Maybe some dev could talk to Cryptsy and tell them to update their wallet? Undecided

I created a ticket this morning. Waiting for answer.
But I don't know if Nibiru has already created his ticket

Yes have also sent ticket

Nibiru

full member

Activity: 224

Merit: 100

Krugercoin [KGC]

Quote from: UniMatrixZ on March 10, 2014, 02:29:54 AM

How to get on the right chain (winwallet):

1. Go to your appdata folder and find Krugercoin folder, go into the Krugercoin folder.
2. Start notepad
3. Write the following:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8772

Choose save as krugercoin.conf (not krugercoin.conf.txt)

Or if you already have a krugercoin.conf file, edit it to only contain the lines above.

4. Delete the following files in the Krugercoin folder

blk0001.dat
blkindex.dat
peers.dat

5. Now go to your krugercoin-qt folder and find start.bat, open it in notepad
6. Delete this line:

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and replace with the following line

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

7. Save the file
8. IMPORTANT! Start your wallet using start.bat(otherwise it will sync using the wrong nodes)and let it sync, may take awhile.
9. Done Grin

Thanks for this I have updated the wallets with above information thanks --- Yes you are all right should of planned it better -- I have been on a bit of tight schedule with various stuff -- my apologies to those affected!

You are a great bunch off guys/girls and I really appreciate it!

# cheers to eaverybody helping .....

UniMatrixZ

full member

Activity: 135

Merit: 100

miners-pool.eu down?

Edit: back up now Grin

almightyruler

legendary

Activity: 2268

Merit: 1092

If you have a cable or DSL connection that assigns a different IP each time you drop and reconnect it would be a very good idea to do this. That way you are likely to be assigned a virgin IP that old peers on the wrong fork will not know about.

UniMatrixZ

full member

Activity: 135

Merit: 100

How about if you did a clean install of the client?

I just did it on my work computer, edited start.bat before I started the client.
And I did not create a conf file.

Let's see how it goes.

I wonder where the dev is, should be in his interest to fix this.

Make sure to backup wallet.dat before you do a clean install!

almightyruler

legendary

Activity: 2268

Merit: 1092

Quote from: JohnnyCrypto on March 10, 2014, 03:53:44 AM

Had one small problem though. I did get stuck at block 1119999. With the new client.

I'm stuck at 1119999 again. It looks like -connect only restricts outbound connects, but will not disable inbound connects, so any peers on the wrong fork which you've communicated with previously will still be able to connect. Sad

I think the only reliable way to properly upgrade may be to install a copy of the blockchain database from the correct chain. A checkpoint would probably not hurt, either.

This mess would probably not have happened if the KGW fork was properly scheduled! Sad

JohnnyCrypto

newbie

Activity: 45

Merit: 0

Good hope cryptsy gets their wallet updated soon as well. Cool

I'm all synced up now on the right chain.

Had one small problem though. I did get stuck at block 1119999. With the new client.

So i ran the old client with the edited "start.bat" file. I then synced from 1119999>1121075.

I then ran the new client with the edited "start.bat" file.

Now everything is good, with correct chain nodes. Grin

Good luck everyone. Wink

paladin281978

hero member

Activity: 742

Merit: 500

cryptsy updated wallet?

UniMatrixZ

full member

Activity: 135

Merit: 100

Thank you, edited my post Wink

Just got an answer from Cryptsy, told them to ONLY use the three correct nodes when they update their wallet.
So we will see how it goes.
Let's hope the devs make a new wallet update with a new start.bat file soon.

JohnnyCrypto

newbie

Activity: 45

Merit: 0

Quote from: UniMatrixZ on March 10, 2014, 02:29:54 AM

How to get on the right chain (winwallet):

1. Go to your appdata folder and find Krugercoin folder, go into the Krugercoin folder.
2. Start notepad
3. Write the following:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8772

Choose save as krugercoin.conf (not krugercoin.conf.txt)

Or if you already have a krugercoin.conf file, edit it to only contain the lines above.

4. Delete the following files in the Krugercoin folder

blk0001.dat
blkindex.dat
peers.dat

5. Now go to your krugercoin-qt folder and find start.bat, open it in notepad
6. Delete this line:

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and replace with the following line

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

7. Save the file
8. Start your wallet and let it sync, may take awhile.
9. Done Grin

Haha, thanks.

But don't forget, you have to run "start.bat" not just the wallet directly. Or it will sync using wrong chain nodes via UPNP.

UniMatrixZ

full member

Activity: 135

Merit: 100

Thank you!

MinersPoolEU:

Maybe you could put a link on your pools frontpage to this forum, so people can get on the right chain?

paladin281978

hero member

Activity: 742

Merit: 500

UniMatrixZ

good job

UniMatrixZ

full member

Activity: 135

Merit: 100

How to get on the right chain (winwallet):

1. Go to your appdata folder and find Krugercoin folder, go into the Krugercoin folder.
2. Start notepad
3. Write the following:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcallowip=127.0.0.1
rpcport=8772

Choose save as krugercoin.conf (not krugercoin.conf.txt)

Or if you already have a krugercoin.conf file, edit it to only contain the lines above.

4. Delete the following files in the Krugercoin folder

blk0001.dat
blkindex.dat
peers.dat

5. Now go to your krugercoin-qt folder and find start.bat, open it in notepad
6. Delete this line:

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and replace with the following line

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

7. Save the file
8. IMPORTANT! Start your wallet using start.bat(otherwise it will sync using the wrong nodes)and let it sync, may take awhile.
9. Done Grin

UniMatrixZ

full member

Activity: 135

Merit: 100

Nibiru:

PLEASE add this to start.bat to all the wallets so we can make sure everybody is on the same chain.

rem *************************************
rem *** Start Krugercoin with nodes ***
rem *** This will start krugercoin ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in. ***
rem *************************************

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

Sent him a PM also, we need to sort this out so we can start to trade with krugercoins again Grin

UniMatrixZ

full member

Activity: 135

Merit: 100

Quote from: JohnnyCrypto on March 09, 2014, 09:31:19 PM

Quote from: almightyruler on March 09, 2014, 08:10:11 PM

I just restarted my Krugercoin client and noted peers with plausible heights (all connected within about a minute of each

other)

212.83.191.197 - 1121301
78.42.83.245 - 1119999
84.104.23.68 - 1127091
94.181.11.189 - 1127091
178.149.224.172 - 1121336
82.111.88.34 - 1121287

So besides the one peer stuck at 1119999 there seem to be at least 4 different chains.

Yeah, there are multiple chains going on here.

Guys stop adding all the nodes people are posting here. They are mostly no good. It's causing chain forks.

I think i may have a solution to the sync problem. Just follow these instructions.

The main chain is on krugercoin.miners-pool.eu, since 99% of the hash rate is coming from there.

So the first thing to do is delete all the addnodes in your .conf file.

Then delete blk0001.dat, blkindex.dat & peers.dat.

Then go to your "kruger-kgw" folder, where your krugercoin-qt is located, and edit the "start.bat" file to look like this.

Code:

rem *************************************
rem *** Start Krugercoin with nodes   ***
rem *** This will start krugercoin    ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in.     ***
rem *************************************

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

Then run the "start.bat" file to start your wallet. It should sync to the right chain. And will not connect to any other nodes that are on the wrong chain with the "-connect=".

These 3 nodes are on the right chain as of right now. Plus as i said, krugercoin.miners-pool.eu basically is the whole chain.

Have fun, hope this fixes peoples problems.

Thanks for the info, I have done this and it's syncing fine.

JohnnyCrypto

newbie

Activity: 45

Merit: 0

paladin281978

Just use your usual .conf file without the addnodes for now. Once everybody is on the right chain, we can go back to adding other nodes.

paladin281978

hero member

Activity: 742

Merit: 500

JohnnyCrypto

write for all the correct .conf file please

JohnnyCrypto

newbie

Activity: 45

Merit: 0

Quote from: paladin281978 on March 09, 2014, 10:17:41 PM

Quote from: JohnnyCrypto on March 09, 2014, 09:31:19 PM

Quote from: almightyruler on March 09, 2014, 08:10:11 PM

I just restarted my Krugercoin client and noted peers with plausible heights (all connected within about a minute of each

other)

212.83.191.197 - 1121301
78.42.83.245 - 1119999
84.104.23.68 - 1127091
94.181.11.189 - 1127091
178.149.224.172 - 1121336
82.111.88.34 - 1121287

So besides the one peer stuck at 1119999 there seem to be at least 4 different chains.

Yeah, there are multiple chains going on here.

Guys stop adding all the nodes people are posting here. They are mostly no good. It's causing chain forks.

I think i may have a solution to the sync problem. Just follow these instructions.

The main chain is on krugercoin.miners-pool.eu, since 99% of the hash rate is coming from there.

So the first thing to do is delete all the addnodes in your .conf file.

Then delete blk0001.dat, blkindex.dat & peers.dat.

Then go to your "kruger-kgw" folder, where your krugercoin-qt is located, and edit the "start.bat" file to look like this.

Code:

rem *************************************
rem *** Start Krugercoin with nodes   ***
rem *** This will start krugercoin    ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in.     ***
rem *************************************

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

Then run the "start.bat" file to start your wallet. It should sync to the right chain. And will not connect to any other nodes that are on the wrong chain with the "-connect=".

These 3 nodes are on the right chain as of right now. Plus as i said, krugercoin.miners-pool.eu basically is the whole chain.

Have fun, hope this fixes peoples problems.

my "start.bat" file contains that:

rem *************************************
rem *** Start Krugercoin with nodes ***
rem *** This will start krugercoin ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in. ***
rem *************************************

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and I added addnode=212.83.191.197 ( = krugercoin.miners-pool.eu)

and chain coincides with krugercoin.miners-pool.eu

Why node in file "start.bat" different?

Some nodes are on the wrong chain. So only using nodes with the correct block height, by forcing the client to only sync with nodes on the correct chain with "-connect=" instead of "-addnode=" will hopefully alleviate these problems.

paladin281978

hero member

Activity: 742

Merit: 500

Quote from: JohnnyCrypto on March 09, 2014, 09:31:19 PM

Quote from: almightyruler on March 09, 2014, 08:10:11 PM

I just restarted my Krugercoin client and noted peers with plausible heights (all connected within about a minute of each

other)

212.83.191.197 - 1121301
78.42.83.245 - 1119999
84.104.23.68 - 1127091
94.181.11.189 - 1127091
178.149.224.172 - 1121336
82.111.88.34 - 1121287

So besides the one peer stuck at 1119999 there seem to be at least 4 different chains.

Yeah, there are multiple chains going on here.

Guys stop adding all the nodes people are posting here. They are mostly no good. It's causing chain forks.

I think i may have a solution to the sync problem. Just follow these instructions.

The main chain is on krugercoin.miners-pool.eu, since 99% of the hash rate is coming from there.

So the first thing to do is delete all the addnodes in your .conf file.

Then delete blk0001.dat, blkindex.dat & peers.dat.

Then go to your "kruger-kgw" folder, where your krugercoin-qt is located, and edit the "start.bat" file to look like this.

Code:

rem *************************************
rem *** Start Krugercoin with nodes   ***
rem *** This will start krugercoin    ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in.     ***
rem *************************************

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

Then run the "start.bat" file to start your wallet. It should sync to the right chain. And will not connect to any other nodes that are on the wrong chain with the "-connect=".

These 3 nodes are on the right chain as of right now. Plus as i said, krugercoin.miners-pool.eu basically is the whole chain.

Have fun, hope this fixes peoples problems.

my "start.bat" file contains that:

rem *************************************
rem *** Start Krugercoin with nodes ***
rem *** This will start krugercoin ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in. ***
rem *************************************

krugercoin-qt.exe -addnode=192.186.133.74 -addnode=84.22.96.60 -addnode=117.27.250.149

and I added addnode=212.83.191.197 ( = krugercoin.miners-pool.eu)

and chain coincides with krugercoin.miners-pool.eu

Why node in file "start.bat" different?

JohnnyCrypto

newbie

Activity: 45

Merit: 0

Quote from: almightyruler on March 09, 2014, 08:10:11 PM

I just restarted my Krugercoin client and noted peers with plausible heights (all connected within about a minute of each

other)

212.83.191.197 - 1121301
78.42.83.245 - 1119999
84.104.23.68 - 1127091
94.181.11.189 - 1127091
178.149.224.172 - 1121336
82.111.88.34 - 1121287

So besides the one peer stuck at 1119999 there seem to be at least 4 different chains.

Yeah, there are multiple chains going on here.

Guys stop adding all the nodes people are posting here. They are mostly no good. It's causing chain forks.

I think i may have a solution to the sync problem. Just follow these instructions.

The main chain is on krugercoin.miners-pool.eu, since 99% of the hash rate is coming from there.

So the first thing to do is delete all the addnodes in your .conf file.

Then delete blk0001.dat, blkindex.dat & peers.dat.

Then go to your "kruger-kgw" folder, where your krugercoin-qt is located, and edit the "start.bat" file to look like this.

Code:

rem *************************************
rem *** Start Krugercoin with nodes   ***
rem *** This will start krugercoin    ***
rem *** with some base nodes to start ***
rem *** pulling the KGC chain in.     ***
rem *************************************

krugercoin-qt.exe -connect=84.104.23.68 -connect=94.181.11.189 -connect=krugercoin.miners-pool.eu

Then run the "start.bat" file to start your wallet. It should sync to the right chain. And will not connect to any other nodes that are on the wrong chain with the "-connect=".

These 3 nodes are on the right chain as of right now. Plus as i said, krugercoin.miners-pool.eu basically is the whole chain.

Have fun, hope this fixes peoples problems.

Topic: [KGC] The future is krugercoin and the future is now! [Official Launch] - page 17. (Read 84967 times)