Topic: JKC - The Scrypt Coin with Super Blocks (Read 33142 times)

Hello,

   The archive.org copy of the official block explorer shows a last recorded Best Chain at height 219213.

    This week, some user opened their Junkcoin wallet, found the IRC server and synced with my node up through height 66755.

    So, roughly almost 25% of the historical chain still exists, through 6/21/13 16:13:56.

    Anybody think they might be able to put up a peer to catch me up to block 219213 and beyond?

Best Regards,
-Chicago

Hello Junk Captains,

    Would y'all be kind enough to help by putting your JunkCoin wallet online so I may sync with it.
    I am unable to find any nodes to peer with and do want to keep my full node online so the blockchain persists and remains historically relevant.

    It would be best to find the longest chain with the most work.
    Feel free to send me a private message if you would like to help but do not want to post your node's address in the forum at present.

Best Regards,
-Chicago

Junk is salvage-able

Ideas?

Pick 3 junky coins under$10k
Lets get'm back up, and under the flag of JUNK coins

battle tesla hellas
kore xdq bitbar bitcoinplus
seed cool top
caix spa red apex
buk grand util
tor asic bet icb
sbc nrs emd mls
craig mmc zed
taco alien vegas
xXx ghc rpc lyc

PICK 3 on that list and post below.

Someone just tried to game JUNK big-time today.

They Manipulated the price down from 130 Satoshi to 2 Satoshi.

I have no idea how someone could have done that so smoothly without any attention.

I actually bought a few hundred junk coins at 18 Satoshi so it wasn't some glitch, it really went that low.

There were no sellers at that price, just bots selling tiny blocks.

Now the price is back up at 130 Sats but I wonder what's going on - was that a fat finger trade or is someone trying to buy up a huge portion of JUNK?

Anybody have any idea?

Thanks!

Is JUNK still alive or is JUNK finally Junked?

JKC Devs and Holders,


Is this the official JunkCoin thread?

Older coins are being burried under an avalanche of new cryptos, something I said would happen last year.

That said, devs of any crypto should do anything within their power to increase stakeholder value.  Given the small budgets of most cryptos there is little that can be done.

May I suggest a "Stock-BuyBack".


A reduction in total max coins and also a reduction in the current subsidy are both great examples of a stock BuyBack and the best part is that it doesn't cost the devs or current holders anything to do.

Reducing the outstanding number of coins (and subsidy) will instantly increase the value of the coin as it makes it harder to get and more rare in the future.  It's a simple supply and demand equation and right now, most alts have way too many coins to make them equitable to new investors.

There is no reason for JKC to have 107 million total max coins.  DarkCoin made this realization and they dropped their max coins from 88 million to 22 million and it has done wonders for them.

This will automatically increase shareholder value [proportionately] rewarding the current loyal holders of JKC and if you set a date when the BuyBack will take effect anyone can buy JKC and gain that same value, thus, creating a sudden demand for JunkCoins.

There are now 11 million JKC coins now.  I suggest a max cap of 30 million and perhaps drop the lotto subsidy in half as those large blocks can dilute the coin too quickly

Just a suggestion:  Something needs to be done because [like I said last year when we had only 12 coins out here] by next year, we'll have over 3,000 alt coins.

Do something while you can still be noticed and do it in time for the next big wave of incoming new investors which will be this summer.

Good luck!

PUMP on cryptsy?

Here's my getpeerinfo from the console, only 2 of the above nodes are connected.




[
{
"addr" : "5.249.152.30:9771",
"services" : "00000001",
"lastsend" : 1393354533,
"lastrecv" : 1393354536,
"conntime" : 1393354286,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "115.28.56.217:9771",
"services" : "00000001",
"lastsend" : 1393354529,
"lastrecv" : 1393354529,
"conntime" : 1393354303,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "84.200.84.93:9771",
"services" : "00000001",
"lastsend" : 1393354529,
"lastrecv" : 1393354528,
"conntime" : 1393354331,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
},
{
"addr" : "38.64.135.55:9771",
"services" : "00000001",
"lastsend" : 1393354528,
"lastrecv" : 1393354528,
"conntime" : 1393354455,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 161564,
"banscore" : 0
}
]

I've made this junkcoin.conf file. Is this workable? The dif is the changes to the ports - none set to LTC any longer as noted on the previous page:

I appreciate your detailed reply, and your frustration over this coin. I didn't realize that there was such a lack of interest when its value is up and up. How big a rig is a "heavy hitter"? Would it be 60 mh/s +? There's no way I could help with that. But I may be able to offer some help for a little while.

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.

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.

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.

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.

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
    }
]

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.

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://bitcointalksearch.org/topic/list-of-all-cryptocoins-134179


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.

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

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.