the wallet doesnt sync,anybody knows how to fix it?  its the second time i try. Hi - you need to add the following in your conf file addnode=198.0.43.100 addnode=mentat.cable.nu The second one is mine - I am keeping it running for as long as I can, pending power outages, windows updates etc. A few days ago, I lost power for about 4 hours but generally it is running, so you can use it to get synchronized. thanks  i can start mining this coin. If you would like to help us - you can mine at the nbl.pnwminer.com pool - currently three of us there. [Edit] Ok, I see you were there already. You actually don't need a wallet to mine, unless you want to solo-mine - I run a wallet so that others can keep synchronized and payout my coins to Cryptsy. |
|
|
|
the wallet doesnt sync,anybody knows how to fix it? its the second time i try. Hi - you need to add the following in your conf file addnode=198.0.43.100 addnode=mentat.cable.nu The second one is mine - I am keeping it running for as long as I can, pending power outages, windows updates etc. A few days ago, I lost power for about 4 hours but generally it is running, so you can use it to get synchronized. |
|
|
|
Do you think it's possible to change amount of blocks needed for difficulty change?
Yes, but we would have to change the source code, decide when to make the change - usually when the difficulty change is supposed to happen, which means a hard fork I suppose. But then the updated wallet would have to distributed somehow so that everyone is using this one before it can happen. Block 40320 is when this could happen - ideally to implement KGW, but there is no shortcuts so we still need to get through the next 804 blocks. Currently at 39516. If we can pool our hashing power, we could get there, but most of the time pnwminer is only running about 1.6Mh which means only about 4-8 blocks a day. NBL is still keeping reasonable value - at 0.00002433 BTC right now, but this is a bit low due to the BTC meltdowns that have been happening and should recover some in the near future - hopefully back to around 0.00002800 BTC or so, once people's confidence in BTC goes back up. It could go even higher - sold a few at 0.00004500 BTC only 10 days ago. |
|
|
|
Hey guys. Does this coin need KGW or what?! Where's the Dev, i'd feel mean making an unofficial fork.
Definitely, that would be a great idea. The fork would have to happen at the end of this round of blocks, so the wait is still there, but it would be a great idea if the dev can make the changes like other coins are doing. [Edit: The dev is digitalindustry but have no idea what time he can commit to this - let's ask him] |
|
|
|
|
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.
|
|
|
|
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.0Edit: 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. |
|
|
|
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. |
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
anyone else having problems with solo mining? Or is this coin now dead?
We are all having the same nBits error - when trying to mine. |
|
|
|
BtcLtc is the only exchange I know of that lists PPL. Current value is 0.210010 CNY - not much, but it is possible to solo mine, and you get 1.25 PPL for each block. Average network hashrate goes from about 1Mh to about 10Mh.
Question: If I sell at btcltc do I need a bank account to put the CNY in or I can buy bitcoin directly from their site? Current price is 0.133 CNY. You can buy BTC, however I believe there is a minimum amount that you can withdraw - otherwise, buy other coins and withdraw those. |
|
|
|
New node: 46.229.151.234
current block 39393
You are a little behind - current block is 39432, check if you are syncing. My client is connecting to 198.0.43.100:8550 Thanks mate, now I'm at 39433  No problems - we are getting through the blocks slowly - 39434 just 27 minutes ago. Averaging at present 8 blocks a day, only 886 to go before the difficulty retarget. |
|
|
|
New node: 46.229.151.234
current block 39393
You are a little behind - current block is 39432, check if you are syncing. My client is connecting to 198.0.43.100:8550 |
|
|
|
|
Oh - another thing. It seems that the whole thing might have happened due to the miner generating the time-travel block (the one from the future) that is the real cause. They need to correct the code not to allow submissions from clients whose clocks are not in agreement with the rest of the network. This is something I referred to in a couple of posts earlier.
P.S. The solution might still be a couple of weeks away - end of the month, if you read all the posts - but who knows?
|
|
|
|
|
I don't know if ORB is still broken, but I did try mining it a couple of weeks ago, when it should have been possible to mine - but was still getting nBits errors. Has anyone had any luck?
|
|
|
|
|
When will you have your next order? I am in Sydney and am interested in a couple.
|
|
|
|
|
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?
|
|
|
|
|
Could be power supply. Swap it with any other power supply, leave one gpu installed, it should be able to boot and stay up. If you want to mine, the psu must have sufficient capacity.
I got up this morning to find one miner powered off. Would not power on. Turned off the power board, then waited a while and turned on. The machine would start up, then before it finished booting - powered off again. I started taking out gpu's and even with one gpu - it would power off in the middle of boot, so it must be a bad power supply. Rang up the shop and they said bring it in (3 weeks old unit). Tested with my psu tester which showed -12V was high (meaning not there perhaps). Took it back and waiting on a replacement.
|
|
|
|
|
I suggest you try running three cards - since two is ok, and four is not ok, how about three? This should all run ok from the one 1000W power supply. My 3x7950 takes about 850W from one 1200W psu. If this is ok, try the third card in the other slot - you may have a slot problem, not unknown.
Also as mentioned, power supplies often have multiple 12V rails - try to spread the load across the rails. If you have some of the newer psu's - they are quite often single rail, so easy to work with. In any case, using two psu's should be good.
|
|
|
|
|
Show Posts
