[ANN][ScryptAdaptive] KMC KimoCoin - KimotoCoin [5 EXCHANGES!]

[forgetme]

Excuse me I'm using vert 5.03 and this is bullshit I haven't changed anything and suddenly this issue shows up? That means it's not me it's something server side. What don't want to let anyone solo this coin now fucking bullshit.

Please stay calm and relax. You're not in a life or death situation, i think. We're trying to give you support at our best.

[forgetme]

I have found one block the past 3 hours when I should of been finding 3 an hour I have been wasiting my hash and i"m not happy.

Please stop spamming all this short messages. Edit your message before and please use some calm terms.
There is no "server side" of a wallet..everyone has solo mined at least for the first 300 blocks and no problem...
And nobody can't stop you from solo mining. Don't understand what you would you say

[forgetme]

I have found one block the past 3 hours when I should of been finding 3 an hour I have been wasiting my hash and i"m not happy.

Which is your hashrate? We're running total net hashrate quite high now, so at least 10/12 MH/s is needed for a profitable solo mining

[Zulandio]

I was finding 3 blocks an hour on average earlier today with the same net hash rate. That's not the point the point is that I am magically having issues mining this coin. WTF Pool zero not providing work fast enough. PC crash suddenly not my end has to be something on the wallet end.

[CHMinePeeR]

I have found one block the past 3 hours when I should of been finding 3 an hour I have been wasiting my hash and i"m not happy.

solomine is a lucky thing you cant say you should find 1 block every hour...you can find 10 in a row and then 0 for 24hrs, there is no fixed timeframe...

Please be calm and patient in here, a great dev and supporters are here to help, and your word considering there work are absolutely not nice! (or is WTF your signature?? lol)

Check your miner settings properly especially you configured correctly your directions.

Pool url or credentials are invalid  this means you entered wrong username or password or wrong rpc port!
btw you seems to be the only one having this issue, i cant see any other bother...

[Zulandio]

Would you read my post FFS I WAS NOT HAVING ANY ISSUES EARLIER TODAY AND SUDDENLY I AM!!.

[forgetme]

I was finding 3 blocks an hour on average earlier today with the same net hash rate. That's not the point the point is that I am magically having issues mining this coin. WTF

In c++ programming doesn't exist any magic. Sorry. Please can you post any screenshot about this malfunction? If you continue just to accuse, seems more like you're trying to scam and put bad view on the coin just for interes

Post some screenshot so we can help you more.
You're the only one talking about this "magic" issue, so i want to investigate more. Sounds strange to me. So strange.

[forgetme]

Would you read my post FFS I WAS NOT HAVING ANY ISSUES EARLIER TODAY AND SUDDENLY I AM!!.

If you can see, i'm reading and trying to support you at my best. Please follow my indication to have a proper support about your issue.
However why your rpc port is set up on that number? is it configured custom to your stuff or what?

[CHMinePeeR]

i just made a test, i have no issue to connect on solomine.

my kimocoin.conf

listen=1
server=1
daemon=1
rpcuser=xxx
rpcpassword=yyy
rpcport=1988
rpcallowip=192.168.1.*

my miner

vertminer version 0.5.4pre2 - Started: [2014-04-02 06:55:24]
--------------------------------------------------------------------------------
 (5s):1.095M (avg):1.081Mh/s | A:2378368  R:22272  HW:0  WU:973.8/m
 ST: 12  SS: 12 (inf%)  NB: 0  PA: 0  PR: 2411  LW: 65928  GF: 8  RF: 0
 Connected to 192.168.1.100 diff 56.3K with LP as user xxx
 Block: df5fe4ac...  Diff:0  Started: [00:07:33]  Best share: 4.04M
--------------------------------------------------------------------------------

from my point of view, you cant provide proves of your issue, you are just a troll......

just give a look on this troll messages history...seems the most unlucky Miner on the world..... 
https://bitcointalk.org/index.php?action=profile;u=272252;sa=showPosts

[Zulandio]

Would you read my post FFS I WAS NOT HAVING ANY ISSUES EARLIER TODAY AND SUDDENLY I AM!!.

If you can see, i'm reading and trying to support you at my best. Please follow my indication to have a proper support about your issue.
However why your rpc port is set up on that number? is it configured custom to your stuff or what?

That wasn't directed at you it was to the guy that said it's lucky finding blocks.

[CHMinePeeR]

That wasn't directed at you it was to the guy that said it's lucky finding blocks.

shit man how can you have that temperatures on your GPUS on scrypt-n?
btw strange your issue...

[forgetme]

you can increase your ST (Staged Work) by increasing your queue by going to settings and then queue and increase it from the default of 1 to 90 or so.  That will help.  Also setup some backup pools so that when Bitcoin-QT doesn't supply work fast enough you miner can leak some shares to standard pools.  That way it's not a complete loss.

Also the only share you will see submitted to the solo will be block solves.  So not seeing any accepted shares is normal operation for solo mining.

For any info check this thread, i think you could solve this with one of the try here

https://bitcointalk.org/index.php?topic=332082.0

Let us know it it worked and share to the community, thanks.

[Zulandio]

you can increase your ST (Staged Work) by increasing your queue by going to settings and then queue and increase it from the default of 1 to 90 or so.  That will help.  Also setup some backup pools so that when Bitcoin-QT doesn't supply work fast enough you miner can leak some shares to standard pools.  That way it's not a complete loss.

Also the only share you will see submitted to the solo will be block solves.  So not seeing any accepted shares is normal operation for solo mining.

For any info check this thread, i think you could solve this with one of the try here

https://bitcointalk.org/index.php?topic=332082.0

I have no idea why they are running that hot I didn't even know they were supposed to run cooler on N.

And now suddenly I find 3 blocks in 10 minutes so I guess it decided to start working again. I don't know if this is something to do with KGW?

[forgetme]

you can increase your ST (Staged Work) by increasing your queue by going to settings and then queue and increase it from the default of 1 to 90 or so.  That will help.  Also setup some backup pools so that when Bitcoin-QT doesn't supply work fast enough you miner can leak some shares to standard pools.  That way it's not a complete loss.

Also the only share you will see submitted to the solo will be block solves.  So not seeing any accepted shares is normal operation for solo mining.

For any info check this thread, i think you could solve this with one of the try here

https://bitcointalk.org/index.php?topic=332082.0

I have no idea why they are running that hot I didn't even know they were supposed to run cooler on N.

Have you tried to read also the other post in the thread i've linked?

[Zulandio]

And now suddenly the local miner on the same machine as the wallet is DC and won't connect. Is showing when I put the IP as alive but local as dead. I don't get it I have all firewalls disabled my router has them in DMZ yet still this occurs.

[CHMinePeeR]

...

you should try to do something for your gpu running on 99C, this is very dangerous for your gpu and shorts his life a lot!

If i mine Scrypt i have a power vent that gives fresh air and i can stay at 75C, with Scrypt-N i dont need the 320m3/h fan...

BTW can you please post your .conf? maybe there is an issue...

[forgetme]

I'm using SGminer on the local rig I have 127.0.0.1 on the others I have the wallet rig addy. It will kick off my miners or it will say pool is not providing work fast enough and cause them to crash.

daemon=1
listen=1
server=1
gen=0
rpcuser=kim
rpcpassword=1
rpcallowip=192.168.1.*
rpcallowip=192.168.1.101
rpcallowip=192.168.1.102
rpcallowip=192.168.1.103
rpcport=1113
maxconnection=100

I have tried disabling windows firwall putting the rigs in DMZ nothing stops this from happening.

SGMiner work with Vert and Kimo ? Maybe you want to use this : https://github.com/Bufius/cgminer-vertcoin-cpu

and remember to add this on the cgminer options : --no-stratum --no-longpoll



FaSan

Try:

-Hardware reboot or
-Change with cgminer and give a try with that or
-Try CPU mining, and tell us how does it goes with that or
-why your rpc port is set up at 1113?

[forgetme]

Total KMC Blocks Minted: 4208 !

We're doubling the expected blocks number. Such an hashrate on Scrypt-Adpative-N!

Good work miners

[forgetme]

@Zulandio

Any news over there?
 

[Astroxjr]

Use static IP's for all - sounds like your DHCP times out on one of your rigs.