I've got a miner going on it, I had it right at the changeover too, but it's not showing up in my userstats, I have payouts set for 2.0 and 2.1 just to cover my bases as well. Only old 2.1 from the test is showing new stuff isn't showing up. Oh fuck me, my worker was fucked up. Damn it, and I was on a few hundred low diff blocks too, fuck it all. |
|
|
|
Deposite vcoin on Yobit still not available yet, status Maintenace  I have noticed this,I will contact with them for further information Thank you dev, I really hope this issue resolved as soon as possible Any luck finding out what's going on with Yobit? |
|
|
|
All peers are on the same block

[
{
"addr" : "70.169.221.184:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363407,
"bytessent" : 1486,
"bytesrecv" : 75339,
"conntime" : 1459363215,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "144.76.68.101:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363902,
"lastrecv" : 1459363246,
"bytessent" : 502,
"bytesrecv" : 75199,
"conntime" : 1459363243,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "98.115.147.74:41989",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363665,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363663,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "70.163.93.50:59678",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363716,
"lastrecv" : 1459363675,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363675,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "144.76.236.8:56683",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363717,
"lastrecv" : 1459363901,
"bytessent" : 43882,
"bytesrecv" : 282,
"conntime" : 1459363715,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
}
]
Wallet is ignoring my krugercoin.conf file though, I've tried solo mining rather than using iSpace, but the wallet is ignoring the config file. I used a custom data direction, but I've also put the config file in %appdata% too just to be sure it wasn't checking there. Wallet will not use the config so it's making solo mining to start moving the block chain not an option. iSpace seems badly forked and yobit is now in maintenance. I guess this is the end for this coin unless someone can fix it.
try copying krugercoin.conf to bitcoin.conf in both your custom data directory and %appdata% That worked, I had seen it used the right krugercoin.conf here https://cryptocointalk.com/topic/756-krugercoin-kgc-information/ but also tried coin.conf which I've seen a few coins use, neither worked. Solo mining works now, and it looks like iSpace is terribly forked. Thanks. Edit: The new peer list, only ispace is busted  [ { "addr" : "70.163.93.50:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447906, "lastrecv" : 1459448052, "bytessent" : 1431, "bytesrecv" : 75339, "conntime" : 1459447810, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : true }, { "addr" : "70.169.221.184:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448053, "lastrecv" : 1459447953, "bytessent" : 337, "bytesrecv" : 75449, "conntime" : 1459447811, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "108.61.10.90:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448056, "lastrecv" : 1459448056, "bytessent" : 31719, "bytesrecv" : 198859, "conntime" : 1459447815, "pingtime" : 0.00000000, "version" : 60001, "subver" : "/Satoshi:0.7.0.5/", "inbound" : false, "startingheight" : 5263099, "banscore" : 0, "syncnode" : false }, { "addr" : "70.168.69.115:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448053, "lastrecv" : 1459447832, "bytessent" : 447, "bytesrecv" : 35630, "conntime" : 1459447831, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "98.115.147.74:34494", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447906, "lastrecv" : 1459447956, "bytessent" : 48472, "bytesrecv" : 337, "conntime" : 1459447905, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : true, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "144.76.68.101:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447941, "lastrecv" : 1459447944, "bytessent" : 227, "bytesrecv" : 75229, "conntime" : 1459447941, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false } ] Second edit: It was working briefly, now it rejects shares. |
|
|
|
All peers are on the same block

[
{
"addr" : "70.169.221.184:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363407,
"bytessent" : 1486,
"bytesrecv" : 75339,
"conntime" : 1459363215,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "144.76.68.101:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363902,
"lastrecv" : 1459363246,
"bytessent" : 502,
"bytesrecv" : 75199,
"conntime" : 1459363243,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "98.115.147.74:41989",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363665,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363663,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "70.163.93.50:59678",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363716,
"lastrecv" : 1459363675,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363675,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "144.76.236.8:56683",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363717,
"lastrecv" : 1459363901,
"bytessent" : 43882,
"bytesrecv" : 282,
"conntime" : 1459363715,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
}
]
Wallet is ignoring my krugercoin.conf file though, I've tried solo mining rather than using iSpace, but the wallet is ignoring the config file. I used a custom data direction, but I've also put the config file in %appdata% too just to be sure it wasn't checking there. Wallet will not use the config so it's making solo mining to start moving the block chain not an option. iSpace seems badly forked and yobit is now in maintenance. I guess this is the end for this coin unless someone can fix it.
try copying krugercoin.conf to bitcoin.conf in both your custom data directory and %appdata% That worked, I had seen it used the right krugercoin.conf here https://cryptocointalk.com/topic/756-krugercoin-kgc-information/ but also tried coin.conf which I've seen a few coins use, neither worked. Solo mining works now, and it looks like iSpace is terribly forked. Thanks. Edit: The new peer list, only ispace is busted  [ { "addr" : "70.163.93.50:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447906, "lastrecv" : 1459448052, "bytessent" : 1431, "bytesrecv" : 75339, "conntime" : 1459447810, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : true }, { "addr" : "70.169.221.184:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448053, "lastrecv" : 1459447953, "bytessent" : 337, "bytesrecv" : 75449, "conntime" : 1459447811, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "108.61.10.90:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448056, "lastrecv" : 1459448056, "bytessent" : 31719, "bytesrecv" : 198859, "conntime" : 1459447815, "pingtime" : 0.00000000, "version" : 60001, "subver" : "/Satoshi:0.7.0.5/", "inbound" : false, "startingheight" : 5263099, "banscore" : 0, "syncnode" : false }, { "addr" : "70.168.69.115:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459448053, "lastrecv" : 1459447832, "bytessent" : 447, "bytesrecv" : 35630, "conntime" : 1459447831, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "98.115.147.74:34494", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447906, "lastrecv" : 1459447956, "bytessent" : 48472, "bytesrecv" : 337, "conntime" : 1459447905, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : true, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false }, { "addr" : "144.76.68.101:8771", "addrlocal" : "71.38.156.239:8771", "services" : "00000001", "lastsend" : 1459447941, "lastrecv" : 1459447944, "bytessent" : 227, "bytesrecv" : 75229, "conntime" : 1459447941, "pingtime" : 0.00000000, "version" : 70002, "subver" : "/Kruger:0.9.3/", "inbound" : false, "startingheight" : 5214372, "banscore" : 0, "syncnode" : false } ] |
|
|
|
|
All peers are on the same block

[
{
"addr" : "70.169.221.184:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363407,
"bytessent" : 1486,
"bytesrecv" : 75339,
"conntime" : 1459363215,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "144.76.68.101:8771",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363902,
"lastrecv" : 1459363246,
"bytessent" : 502,
"bytesrecv" : 75199,
"conntime" : 1459363243,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : false,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "98.115.147.74:41989",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363675,
"lastrecv" : 1459363665,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363663,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "70.163.93.50:59678",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363716,
"lastrecv" : 1459363675,
"bytessent" : 43937,
"bytesrecv" : 227,
"conntime" : 1459363675,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "144.76.236.8:56683",
"addrlocal" : "71.38.156.239:8771",
"services" : "00000001",
"lastsend" : 1459363717,
"lastrecv" : 1459363901,
"bytessent" : 43882,
"bytesrecv" : 282,
"conntime" : 1459363715,
"pingtime" : 0.00000000,
"version" : 70002,
"subver" : "/Kruger:0.9.3/",
"inbound" : true,
"startingheight" : 5214371,
"banscore" : 0,
"syncnode" : false
}
]
Wallet is ignoring my krugercoin.conf file though, I've tried solo mining rather than using iSpace, but the wallet is ignoring the config file. I used a custom data direction, but I've also put the config file in %appdata% too just to be sure it wasn't checking there. Wallet will not use the config so it's making solo mining to start moving the block chain not an option. iSpace seems badly forked and yobit is now in maintenance. I guess this is the end for this coin unless someone can fix it.
|
|
|
|
Wallet under maintenance, anyone know whats going on. Seems to have happened right after iSpace blew up for a while. I've also trying syncing a wallet myself, won't update past the day iSpace had it's meltdown, even though iSpace is mining again, I can't sync up, even with a good 6-7 nodes at times. |
|
|
|
|
What's going on with the site? It's been entirely dead for a while now.
|
|
|
|
TAKcoin seems to have been taken off coinwarz  It was only on Cryptsy and we all know what state they are in. Might be a good time to search out another exchange to get listed on. Might be able to get it on Yobit or something? |
|
|
|
where exchange ?? go go
Everything quiet now, not looking good. |
|
|
|
New Wallets are up and working. Make sure to get the new wallets with our new branding. www.lootcoin.org Working on finding an exchange at all? |
|
|
|
Submitted a Request to list Joulecoin to www.coins-e.com exchange. I hope it makes into the VOTING selection. Please, some support will be needed. Ill try to financially pitch in as much as I can but anything will help. Thank All Keep You all Posted I will gander this 2night and this weekend, I have no issues throwing some BTC at an exchange that will list this. Yobit would for the 0.1 BTC fee they have. |
|
|
|
OK, seem to be getting to the bottom of things. Diff was holding at the same diff it was when it would freeze for many blocks, this time it did finally move unlike on the old wallet. Seems the smaller shares that would normally update speed are being considered stale for some reason.  this was accepted by the blockchain and is now 3 confirmations. So it seems it might not have been the key, just coinciding chain derpyness. I guess stale small shares that would normally update speed weren't counting for some reason. I've solo mined a ton of coins and never seen such long diff freezes. I had it up on one monitor keeping an eye on it for over an hour on the old wallet, 2.895M frozen which it always froze at, no other number, which makes it so odd, there should be some damned variance. Solved it, seems if the wallet systems windows clock is even off by a few seconds it starts causing the speed in the miner not to update. Even though windows was set to autosync, one sync and now the speed is moving around normally as it mines. I bet it's a once every 24 hour fracking sync, and it got off just enough at the time I added the key to start up. Miner speed now adjusting properly, never seen a coin do this before over a normal daily clock drift. Edit: Been a while now, zero freezing issues now ever since I gave the system clocks a smack. Off by mere seconds, but it was enough. Problem completely gone now. |
|
|
|
I notice my cgminer does get stuck sometimes and work restarts. Seems to be early on that it all might be trying to adjust.
I had it freeze for a good hour twice, the speed up top 5s 1m, 5m would slowly drop, but the miner specific hash would freeze. , no change, I even gave it a good long while watching it once. This never happened before adding a key to the wallet, and immediately after it started. I'm going to set a wallet up on another system and see if it happens. |
|
|
|
I will monitor and see.
It's been an issue with cgminer, not sure if others would have it, but as it seems wallet related it likely would, but it could just be a freeze tripping cgminer up. 0 issue once going back to a pool. |
|
|
|
How many connections are you showing.
8, I've had ports mapped and been running it nicely for a while. |
|
|
|
|
Minor bug: If you add a privkey to the wallet and try and solo mine, the miner starts randomly freezing and not submitting work units anymore. Was fine for ages before the privkey, started glitching quickly right after, happens in minutes a lot, and most times right after finding a block. Moved back to pool mining for now due to it, and the miner is having no issues, soon as I go back to solo it starts freaking out.
Edit: I've done a reindex/rescan still happens within minutes of starting the miner for solo mining. speed freezes and it just doesn't do work anymore.
|
|
|
|
Airdrop anyone? Thoughts?  Could help with interest, and reward those already mining away. Any chance on getting this on an exchange soon? |
|
|
|
I'm getting no work available from pool when I try and mine.
Should be fixed now. My apologies Starting working for a bit, just broke again. I was just about to rent a rig too, couldn't verify pool, thanks for getting on it. Are you using the port that was posted in the ANN? I had tweaked them by accident and just changed them back. Please use stratum+tcp://mine.coinze.com:4012 Diff: 1024 - 1024 stratum+tcp://mine.coinze.com:4013 Diff: 128 - 51200 stratum+tcp://mine.coinze.com:4014 Diff: 24000 - 512000 I had used the getting started page on the pool as I thought I'd need an account at first. I used the port displayed there then. I was coming up with miner stats as well while it was working. I guess that's the issue, getting work now. |
|
|
|
I'm getting no work available from pool when I try and mine.
Should be fixed now. My apologies Starting working for a bit, just broke again. I was just about to rent a rig too, couldn't verify pool, thanks for getting on it. |
|
|
|
|
Show Posts
with send sys
