[KGC] The future is krugercoin and the future is now! [Official Launch]

[gnode]

I am mining with 7.0.5  because I have not been able to sync my 9.3 client. I'm still trying to do that, if successful I'll switch to mining with the 9.3.

This node 173.48.255.21 is me. I see it on the nova list posted above so nova is seeing my node. To tell if the nova wallet is up to date try sending some coins to nova from your synced wallet and see if they show up.

If you want to mine, you need an asic scrypt miner, for example an antminer L3. To use an asic miner you have to have your own pool. I use unomp and followed this blockgen guide,

Search "blockgen mining pool" for the tutorial

If in a few days 9.3 doesn't sync I'll try your 9.4 version.


edit: my 9.3 client just crashed again with a bad allocation error and has stopped syncing.

[gnode]

I was only able to get my 9.3 client to july 2017 and then I got the bad allocation error. I'm trying to get past the bad allocation error by reindexing. Looks like it will take a while.

Any other suggestions on what to do?

[hamburger]

I was only able to get my 9.3 client to july 2017 and then I got the bad allocation error. I'm trying to get past the bad allocation error by reindexing. Looks like it will take a while.

Any other suggestions on what to do?

I had Krugercoin 9.3 running on Ubuntu 14.05 so I copied from the .krugercoin folder. the "blocks" "chainstate" and "database" folder to my Windows C:\....\AppData\Roaming\Krugercoin folder, then started the Kurgercoin client with -reindex.

I will upload a snapshot of https://www.blockexplorer.tk/ folders to github when the re indexing reach height 7400000 2017-08-16 09:42:45 - it should take you past the Krugercoin 9.3 error.

H

[gnode]

Previously I had a 9.3 client running on a different pc and I was able to get to May 2 2018 before I got bad allocation error. I could never get past that point on that pc. When I tried to copy the blocks, chainstate etc. to another laptop from a backup dated sept 2017, it would load then crash. I could always restart from the sept backup on the original machine and it would run to april or may before getting the allocation error. So maybe you should wait until the full reindex is done before putting the blocks, etc on github.

[hamburger]

Krugercoin v0.9.4.0 - sync to block height 8840714 without any errors and that is where the good news end, it is no longer down loading blocks from the /Satoshi:0.7.0.5/ client on node 173.48.255.21 (@gnode - are you running the Windows client)

It will still be some time before my v0.7.0.5-g2d35dc4-kgw client reach the block height of 173.48.255.21 - mine is at block height 4957515 now.

Until then, the waiting is killing me!

[sulfurtank]

I was only able to get my 9.3 client to july 2017 and then I got the bad allocation error. I'm trying to get past the bad allocation error by reindexing. Looks like it will take a while.

Any other suggestions on what to do?

This is because the bugerbuger coin needs to be given middle finger. The wallet would run and ramble irrespective of what u do with it, sometimes it bums and cranks when the internet session is over. I developed the fix for it and sent it to malaysian community for a quick beta test. I ordered them to improve the fix and wallet within 1 day time span otherwise the punishment will be induced.

[gnode]

Krugercoin v0.9.4.0 - sync to block height 8840714 without any errors and that is where the good news end, it is no longer down loading blocks from the /Satoshi:0.7.0.5/ client on node 173.48.255.21 (@gnode - are you running the Windows client)

It will still be some time before my v0.7.0.5-g2d35dc4-kgw client reach the block height of 173.48.255.21 - mine is at block height 4957515 now.

Until then, the waiting is killing me!

Yes it is the windows client. If I could get version 9.3 to sync I would mine it.

[hamburger]

A snapshot of the synchronized block up to height 8840714 for Krugercoin v0.9.4.0  / v0.9.3.0 is available at https://www.blockexplorer.tk/snapshot/ - the file size is 3.34 GB and is to large for github.com upload.

The file is being uploaded now and it will take some time to be available for download.

H

[almightyruler]

A snapshot of the synchronized block up to height 8840714 for Krugercoin v0.9.4.0  / v0.9.3.0 is available at https://www.blockexplorer.tk/snapshot/ - the file size is 3.34 GB and is to large for github.com upload.

That's one of the problems with KGC - being an old coin with a very short block time, it has a huge blockchain, which makes the client a real resource hog.

Here's a post I made back in 2015:

Any nodes for this coin?

I'll see if I can find some for you. The big old girl is taking a while to load the block index (over 6 minutes so far)

edit: loading block index took just over 15 minutes (!!! on a 4 core i5!) but unfortunately it's not able to connect to any nodes it currently knows about. Will have to dig out historical IPs, and restart (another 15 mins), letting it sift through mostly abandoned client IPs, so this is going to take a while.

And when I started the client recently on the same server:

10/22/18 00:03:08 Loading block index...
10/22/18 00:03:08 dbenv.open LogDir=/var/coins/krugercoin/database ErrorFile=/var/coins/krugercoin/db.log
10/22/18 00:35:36 LoadBlockIndex(): hashBestChain=c1998bf8fca210af4eec  height=8842344  date=10/20/18 19:45:35

It now takes 32 minutes to load the block index! I can't afford to run this client 24/7 because it takes resources (mostly CPU) from the other coin clients.

[hamburger]

Krugercoin v0.9.4.0 - sync to block height 8840714 without any errors and that is where the good news end, it is no longer down loading blocks from the /Satoshi:0.7.0.5/ client on node 173.48.255.21 (@gnode - are you running the Windows client)

It will still be some time before my v0.7.0.5-g2d35dc4-kgw client reach the block height of 173.48.255.21 - mine is at block height 4957515 now.

Until then, the waiting is killing me!

Yes it is the windows client. If I could get version 9.3 to sync I would mine it.

@gnode

Seems like my Satoshi:0.7.0.5 client caught up with yours and it show that the last block mined was on 24 September 2018 - is this correct?

Could you mine a few more blocks if possible and I'll confirm later if the new blocks download to my client.

Tnx,

H

[gnode]

The last block mined was October 24, 2018. Block number 8854869.


edit: I mined more blocks, last block Oct 27 8855130.

[hamburger]

Some good news

 - www.yobit.com is up again - block height 8849982
 - www.novaexchange.com - I do not have an account
 - www.freiexchange.com - will do a transaction to see if they are up

[George5]

In addition to this, I compiled a new version of the client - Krugercoin v0.9.4.0 and removed all, except for the genesis block from the check points on the main network - this should allow all clients to use the same blockchain (v0.7.0.1 / v0.7.0.5 / v0.9.3.0 / v0.9.4.0).

https://github.com/krugercoin-project/krugercoin-core/releases

So the only option to use this coin is downgrading to the old 0.7.0.5 version? I doubt that Novaexchange will support this idea...
Or maybe we should all start mining at the latest 0.9.4.0 (which is pretty stable btw) until we pass gnode's block height?  

hamburger, your source codes for v0.7.0.1  v0.7.0.5 are just the copy of v0.9.4.0 version. Please double check.

Some good news

 - www.yobit.com is up again - block height 8849982
....

Oops, that's me I'm afraid.
Well, I guess I'm gonna stay on this chain then. Cuz knowing Yobit, I'd say that there is 0.01% chance that they do a wallet resync to get on a proper chain. Been bugging them for many months with PKB fork.

[hamburger]

hamburger, your source codes for v0.7.0.1  v0.7.0.5 are just the copy of v0.9.4.0 version. Please double check.

Hi,

It is correct, github.com add the source code automatically when the release is added and I do not know how to remove it.

I never had any response from yobit on any of my requests for the version number they use and the nodes - you can at least see the highest block height when going to wallets and select deposit or withdraw.

Does anyone know the IP that yobit use?

Tnx.

H

 

[George5]

hamburger, your source codes for v0.7.0.1  v0.7.0.5 are just the copy of v0.9.4.0 version. Please double check.

Hi,

It is correct, github.com add the source code automatically when the release is added and I do not know how to remove it.

I never had any response from yobit on any of my requests for the version number they use and the nodes - you can at least see the highest block height when going to wallets and select deposit or withdraw.

Does anyone know the IP that yobit use?

Tnx.

H

Last time I had a response from Yobit was more than a year ago. Looks like they fired the support team.

And I assume they use 0.9.3 client because looks like different versions are incompatible. At least I wasn't able to sync 0.9.4 client with 0.9.3 chain.
0.9.4 version only syncs up to block 8840714

[gnode]

block height 8849982 is what client version? 0.9.3?

 Does that mean you are mining with v9.3?

[George5]

block height 8849982 is what client version? 0.9.3?

 Does that mean you are mining with v9.3?

Yeah, it's v9.3.

[gnode]

block height 8849982 is what client version? 0.9.3?

 Does that mean you are mining with v9.3?

Yeah, it's v9.3.

Are you using a linux or windows client?

[George5]

Are you using a linux or windows client?

Linux. Win client crashes with some errors.

[hamburger]

Are you using a linux or windows client?

Linux. Win client crashes with some errors.

Could you please share the nodes that your connected to?

Tnx,

H