JKC - The Scrypt Coin with Super Blocks

[JL0z]

for anyone interested, I have a small pool setup that is mining JKC (along with others) on http://pool.trademybit.com -- 0.5% / prop payout

This pool also is working away - it is multi-coin switching to the most profitable coin, or can choose to mine a particular coin.  Has a good percentage of JKC network - I like it.

[tuckertz1992]

Anyone know which pools are kicking out the most Hash?

I use Coin Base but its been donw for 4 horus today :/ - Think its time to chnage pool!

[JL0z]

Anyone know which pools are kicking out the most Hash?

I use Coin Base but its been donw for 4 horus today :/ - Think its time to chnage pool!

Hi, I was just on coin-base.info - I run a couple of small rigs during my night-time, they were fine when I checked this morning (Australia).

The only other pool I know of is a switching pool, trademybits - I did mine JKC there for a while a week ago, but then the hash rate moved so it wasn't producing, then I went with the switching port and ended up with assorted coins.

[capslock1874]

Anyone know which pools are kicking out the most Hash?

I use Coin Base but its been donw for 4 horus today :/ - Think its time to chnage pool!

You can use this JKC pool http://115.28.56.217, it's stable and never kicking out.

[nightwishx]

  good

[nightwishx]

JKC  -  The Scrypt Coin with Super Blocks

Github: https://github.com/Hartland/JKC (Full fix for "warning" 12.20.2013)


Windows Download: (UPDATED 12.29.2013)

https://drive.google.com/folderview?id=0B0wumNRRq9LNa2VOdDF2amtsa0E&usp=sharing


The new feature of this coin is that it added random coin size per block (see below), so even late in the game, you may still hit a block of 1000 coins! Like real gold mining, you may hit different block grade:-)

Features:
  
   - Total coins will be around 107 millions
   - 1 minutes block target
   - Difficulty re-targets once per day
   - Coinbase: 50 coins per block. It will also be halved about every two years (every 1036800 blocks).
   - Mining will be shut down after 12 years.
   - In regular mining (after first 4 bonus days), there will be 1% chance a block will yield triple of the
      normal coins (e.g. in the first 2 years there's 1% chance you get 150 coins per block).
   - There is also 1/10,000 (0.01%) chance that a block will yield 1000 coins. This is valid for all 12 years
      of the mining.
   - The default ports are 9771 (connect) and 9772 (json rpc).




Blockchain Explorers:

http://jkc.cryptocoinexplorer.com/

http://block.al.tcoin.info/


Pools

1% POOL FEE
Payoutsystem prop
only 90 confirms
dynamic Stratum 2-1024
Stratumport 3457
Getworkport 8457

http://coin-base.info/jkccoin/index.php

save the JKC ,save the world

[JL0z]

JKC difficulty is still at 8.67 - isn't it supposed to have retargeted by now?  i.e. daily?  Considering that each block can take a couple of hours to solve - with the network apparently around 5Mh - what's going on?

[BTCIRV]

I still can't get the wallet to synch. Think I downloaded the latest, but it's hard to say with these threads. I've included the addnodes - it connects - gets near the end, doesn't synch fully. Been waiting for two weeks to see if a transaction went though.

I've also deleted the files from roaming and redownloaded everything - still the same.

The website is crud, not even updated. The info old there. Is the most up to date wallet from December?

[JL0z]

I still can't get the wallet to synch. Think I downloaded the latest, but it's hard to say with these threads. I've included the addnodes - it connects - gets near the end, doesn't synch fully. Been waiting for two weeks to see if a transaction went though.

I've also deleted the files from roaming and redownloaded everything - still the same.

The website is crud, not even updated. The info old there. Is the most up to date wallet from December?

Hi, as I understand, the December release is the current file.

What addnodes are you using?  Try 5.249.152.30 as this one I just checked is currently up to date at latest block 161530.  If it doesn't completely synchronize, I usually close it, and wait a minute and open it again - with other wallets, this might need to be done a few times.

[BTCIRV]

I still can't get the wallet to synch. Think I downloaded the latest, but it's hard to say with these threads. I've included the addnodes - it connects - gets near the end, doesn't synch fully. Been waiting for two weeks to see if a transaction went though.

I've also deleted the files from roaming and redownloaded everything - still the same.

The website is crud, not even updated. The info old there. Is the most up to date wallet from December?

Hi, as I understand, the December release is the current file.

What addnodes are you using?  Try 5.249.152.30 as this one I just checked is currently up to date at latest block 161530.  If it doesn't completely synchronize, I usually close it, and wait a minute and open it again - with other wallets, this might need to be done a few times.

Hi, thank you. I've done that a number of times. I've just deleted all the files again except wallet and the junkcoin.conf. I JUST added the last node, so we'll see. Here's what's in my conf:

addnode=24.210.42.161
addnode=86.40.95.128
addnode=46.65.55.189
addnode=123.16.98.117
addnode=113.167.117.173
addnode=88.182.13.77
addnode=113.162.171.83
addnode=107.3.186.55
addnode=62.163.9.155
addnode=138.130.128.133
addnode=188.81.21.200
addnode=5.249.152.30:9771

[JL0z]

Hi,

I just ran the latest wallet with the junkcoin.conf file, pointing to the one node only.  I hadn't installed the wallet before on this machine so it did synchronize.  I had to stop and start the wallet probably half a dozen times, when it seemed to get stuck.

Currently had synchronized to the last block, but because of the block times being so long, you won't get a green tick unless the last block was in the past couple of hours or so.

junkcoin.conf contains:

listen=1
daemon=1
server=1
rpcuser=rpcuser
rpcpassword=rpcpassword
rpcport=9772
port=9771
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
addnode=5.249.152.30

It got stuck early at block 400, then a few hundred later, but after the first few, then seemed to go through the rest ok.

[JL0z]

addnode=24.210.42.161
addnode=86.40.95.128
addnode=46.65.55.189
addnode=123.16.98.117
addnode=113.167.117.173
addnode=88.182.13.77
addnode=113.162.171.83
addnode=107.3.186.55
addnode=62.163.9.155
addnode=138.130.128.133
addnode=188.81.21.200
addnode=5.249.152.30:9771

Hi, I checked those other nodes - none of them are up except the last one that is the one that I am connected to.

[BTCIRV]

This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this.

1) Is this wallet still pointing at LiteCoin instead of JKC?

2) Does JKC really only have 1 node after all this time?

3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts.

As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks.

(-JKC -  LTC clone. 0 starting diff with superblocks, random superblocks.)
 https://bitcointalk.org/index.php?topic=134179.0


Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc.

Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER.

[JL0z]

This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this.

1) Is this wallet still pointing at LiteCoin instead of JKC?

2) Does JKC really only have 1 node after all this time?

3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts.

As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks.

(-JKC -  LTC clone. 0 starting diff with superblocks, random superblocks.)
 https://bitcointalk.org/index.php?topic=134179.0


Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc.

Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER.

BTCIRV, Hi - I didn't run a wallet until I saw your post.  I had been looking at JKC for a while, so yesterday I ran the wallet, the first time and added that node I mentioned.  After that I restarted the wallet - I think about 5-6 times.  It synchronized in about half a day.  What I do, is to look at the debug console - which shows what block the wallet is currently at.  If it stays at the same block for a long time - you can also look at the debug.log file - I generally stop and start it, when the orphan block messages start appearing - which is usually that it is connecting to the wrong blockchain.

It looks like that node I mentioned is not accessible at the moment.  If we need to, I could probably put my copy of the blockchain somewhere for you to download.

[faraway]

This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this.

1) Is this wallet still pointing at LiteCoin instead of JKC?

2) Does JKC really only have 1 node after all this time?

3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts.

As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks.

(-JKC -  LTC clone. 0 starting diff with superblocks, random superblocks.)
 https://bitcointalk.org/index.php?topic=134179.0


Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc.

Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER.

Here is my getpeerinfo, it maybe helpful:
[    {
        "addr" : "192.241.216.151:11345",
        "services" : "00000001",
        "lastsend" : 1392933634,
        "lastrecv" : 1392933635,
        "conntime" : 1392401723,
        "version" : 60002,
        "subver" : "/DGC:1.0.1/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 687959,
        "banscore" : 0
    },
    {
        "addr" : "94.254.7.39:9336",
        "services" : "00000003",
        "lastsend" : 1392933674,
        "lastrecv" : 1392933667,
        "conntime" : 1392872708,
        "version" : 60003,
        "subver" : "/Satoshi:0.8.5/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 169878,
        "banscore" : 0
    },
    {
        "addr" : "89.178.192.93:24242",
        "services" : "00000001",
        "lastsend" : 1392933675,
        "lastrecv" : 1392933657,
        "conntime" : 1392889636,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26826,
        "banscore" : 0
    },
    {
        "addr" : "72.78.100.12:4588",
        "services" : "00000001",
        "lastsend" : 1392933635,
        "lastrecv" : 1392933602,
        "conntime" : 1392895512,
        "version" : 60080,
        "subver" : "/Satoshi:1.1.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 80260,
        "banscore" : 0
    },
    {
        "addr" : "128.199.238.183:24242",
        "services" : "00000001",
        "lastsend" : 1392933634,
        "lastrecv" : 1392933638,
        "conntime" : 1392924222,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26952,
        "banscore" : 0
    },
    {
        "addr" : "84.250.6.190:24242",
        "services" : "00000001",
        "lastsend" : 1392933660,
        "lastrecv" : 1392933606,
        "conntime" : 1392924507,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26953,
        "banscore" : 0
    },
    {
        "addr" : "78.221.228.44:9336",
        "services" : "00000003",
        "lastsend" : 1392933635,
        "lastrecv" : 1392933674,
        "conntime" : 1392931264,
        "version" : 60003,
        "subver" : "/Satoshi:0.8.5/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 89423,
        "banscore" : 0
    },
    {
        "addr" : "72.213.130.251:9336",
        "services" : "00000000",
        "lastsend" : 1392933707,
        "lastrecv" : 0,
        "conntime" : 1392933707,
        "version" : 0,
        "subver" : "",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 0
    }
]

[JL0z]

faraway,

Hi - it looks like none of those peers are JKC wallets.

:9336 is LTC

JKC clients should be :9771 unless they have specifically changed the port in their junkcoin.conf - unlikely.

Ok - this is similar to what has happened in some other clients.  I have had to set firewall restrictions to allow the wallet to only make outbound connections to specific ports.  For JKC the ports should be tcp 9771 and 9772.  For Windows, this is done in Windows Firewall or in your antivirus firewall if enabled.

[faraway]

faraway,

Hi - it looks like none of those peers are JKC wallets.

:9336 is LTC

JKC clients should be :9771 unless they have specifically changed the port in their junkcoin.conf - unlikely.

Ok - this is similar to what has happened in some other clients.  I have had to set firewall restrictions to allow the wallet to only make outbound connections to specific ports.  For JKC the ports should be tcp 9771 and 9772.  For Windows, this is done in Windows Firewall or in your antivirus firewall if enabled.

You are right the client keep the connection with wrong coins. And requires a full upgrade. The maintainer has some work to do...

Anyway if you look at http://www.coinchoose.com/, the block count =161532, and the /Satoshi:0.6.3/ nodes are fine, like the other one:


   {
        "addr" : "115.28.56.217:9771",
        "services" : "00000001",
        "lastsend" : 1392939010,
        "lastrecv" : 1392939086,
        "conntime" : 1392939006,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 161532,
        "banscore" : 0
    },


You may synchronize with these nodes.



The last client repository contains the following checkpoint:

    static MapCheckpoints mapCheckpoints =
            boost::assign::map_list_of
            (  1, uint256("0x11b82349e53d49a5b5ef6262c262564e7663d8cfd912b0040b33683f623022f2"))
            ( 11, uint256("0xc8fc42e967eebdeafcabbd9050a545617f8685d53f2ebcd8f0fa5002b7e62a86"))
            ( 59, uint256("0xcdde8a3e42fa8888df2db8bf6673b29f5e2ae29951275d452686c47acb51cb66"))
            (104, uint256("0x206fe8cc678598456a11041fac65c8e096d9e26c887e391977fdad41e7add208"))
            (10000, uint256("0x7ddbb237b18ffedfa1680a0560d135a9bca247654ab3eef1cc5a39c33074f364"))
            (30030, uint256("0x895f2c50bdf86c3446712d6ff3da448d32e3803a09cb438ad784dbac5c1baf64"))
            (50005, uint256("0xb43e13a918dd208a58fd42aae6aeb51a42e24631cdeb89b2307b62d5353513b9"))
            (100000, uint256("0xfa2e00373495d1343687146a9ef604d8b0f3ee0c21ea749cef9e4c9efaf7c00d"))
            (135000, uint256("0x6ef258d60b6bf2466ade47812d624ca401964d32d264063b2bda3129873d8c26"))



This is enough for the client to operate properly.

[BTCIRV]

This thing still doesn't work... I left it running all night, and it had reset it self twice before then and again during the night. I get up this AM and it's stuck around 8000 remaining. Close it, it reopens at 700000. Now it's stuck at 356049. This is the 5th time I've done this.

1) Is this wallet still pointing at LiteCoin instead of JKC?

2) Does JKC really only have 1 node after all this time?

3) How many DAYS does it take to synch one wallet? I'm approaching a week (2?) and many attempts.

As this coin has grown in popularity, a little better support may be in order? My JKC have gone up over 500% in value and I can't even get to them in several weeks.

(-JKC -  LTC clone. 0 starting diff with superblocks, random superblocks.)
 https://bitcointalk.org/index.php?topic=134179.0


Edit: closed and reopned a couple times, goes to 8682, then back to 300k, then back to 8682... etc.

Edit: closed and reopened a again. Stuck at 92800k or so, then at 8685, then back to 356052, then down to 8000k, then back to 356052. OVER AND OVER AND OVER AND OVER.

Here is my getpeerinfo, it maybe helpful:
[    {
        "addr" : "192.241.216.151:11345",
        "services" : "00000001",
        "lastsend" : 1392933634,
        "lastrecv" : 1392933635,
        "conntime" : 1392401723,
        "version" : 60002,
        "subver" : "/DGC:1.0.1/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 687959,
        "banscore" : 0
    },
    {
        "addr" : "94.254.7.39:9336",
        "services" : "00000003",
        "lastsend" : 1392933674,
        "lastrecv" : 1392933667,
        "conntime" : 1392872708,
        "version" : 60003,
        "subver" : "/Satoshi:0.8.5/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 169878,
        "banscore" : 0
    },
    {
        "addr" : "89.178.192.93:24242",
        "services" : "00000001",
        "lastsend" : 1392933675,
        "lastrecv" : 1392933657,
        "conntime" : 1392889636,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26826,
        "banscore" : 0
    },
    {
        "addr" : "72.78.100.12:4588",
        "services" : "00000001",
        "lastsend" : 1392933635,
        "lastrecv" : 1392933602,
        "conntime" : 1392895512,
        "version" : 60080,
        "subver" : "/Satoshi:1.1.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 80260,
        "banscore" : 0
    },
    {
        "addr" : "128.199.238.183:24242",
        "services" : "00000001",
        "lastsend" : 1392933634,
        "lastrecv" : 1392933638,
        "conntime" : 1392924222,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26952,
        "banscore" : 0
    },
    {
        "addr" : "84.250.6.190:24242",
        "services" : "00000001",
        "lastsend" : 1392933660,
        "lastrecv" : 1392933606,
        "conntime" : 1392924507,
        "version" : 60001,
        "subver" : "/42:0.6.4.6/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 26953,
        "banscore" : 0
    },
    {
        "addr" : "78.221.228.44:9336",
        "services" : "00000003",
        "lastsend" : 1392933635,
        "lastrecv" : 1392933674,
        "conntime" : 1392931264,
        "version" : 60003,
        "subver" : "/Satoshi:0.8.5/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 89423,
        "banscore" : 0
    },
    {
        "addr" : "72.213.130.251:9336",
        "services" : "00000000",
        "lastsend" : 1392933707,
        "lastrecv" : 0,
        "conntime" : 1392933707,
        "version" : 0,
        "subver" : "",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 0
    }
]

Hi, thanks. I've created this in the conf file based on your IPs. I don't know how else to do it:

listen=1
daemon=1
server=1
rpcuser=blah
rpcpassword=blah
rpcport=9772
port=9771
rpcallowip=127.0.0.1
rpcallowip=192.168.1.*
addnode=5.249.152.30:9771
addnode=192.241.216.151:11345
addnode=94.254.7.39:9336
addnode=89.178.192.93:24242
addnode=72.78.100.12:4588
addnode=128.199.238.183:24242
addnode=84.250.6.190:24242
addnode=78.221.228.44:9336
addnode=72.213.130.251:9336
addnode=115.28.56.217:9771

it connects, seems to synch up, but my coins withdrawn from Cryptsy 2 weeks ago aren't there. I just deleted the roaming files again (not the wallet) to allow it to resynch fully with these addresses.

So why is the wallet pointing to the wrong block chain? Does the dev. not know how to do the proper updates? Why let a coin die that's starting to do well?

[dreamwatcher]

The client is not and has never pointed to the Litecoin chain. There was issue a few months ago with the Litecoin alert key, but was corrected last year. This effected many coins not just JKC. The issue had nothing to do with the block chain.

The issue now is lack of miners vs. difficulty.  I could band-aid a fix in that might or might not work depending if users install it. However it would be a hard fork and could cause more problems then it solves.

The next time difficulty goes up and miners drop off, the same situation would occur again. A more permanent fix would involve completely rewriting the difficulty algo. to a different type of algo. In essence changing the coin into something else.

Network Hash rate is ~4 MH @ 8.672 difficulty. This means the network is going to crawl along until the next difficulty drop.

At block 161280 the difficulty jumped from 2.5 to 8.6. Just before the jump the network was running too fast, after the jump you can see the heavy hasher that was running up the difficulty calculation before the adjustment, dropped out of the network. This leaves the chain in the lurch it is in.
 
Difficulty re-targets every 2040 blocks, so at block 163,320 the difficulty will adjust back down again.

You claim the coin is so successful, yet the issue is lack of hash rate. The community abandoned me long ago, then became encouraging when they wanted something. As soon as they got it, crickets again.

I continue to develop in the sense of maintaining the software and keeping it running, but the issue here is not the software. It is the lack of mining outside of a heavy hitter or two who jump on the chain when the difficulty is low and jump off when it adjusts back up.

If one needs a node, I also run and maintain the block explorer jkc.cryptocoinexplorer.com.. One can use it as a node.

[dreamwatcher]

I also ran some tests:

On a machine that had JKC on it, it found a node and synced up in less then  2 minutes.

On a fresh machine that never had JKC on it, the results were similar.

One is going to have sync problems until the chain gets moving again, the client considers itself out of sync if the last block is too old. Of course if that is truly the last block on the chain, it is technically synced.