|
I love it when a plan comes together.
|
|
|
|
This should fix it.
Ha, that's exactly the bit of code I was looking at to see what was going on. Saved me some time, thanks! I'll hit your pool for a bit. |
|
|
|
|
gah, thread too fast, brain hurt
|
|
|
|
gethashespersec would only show your hash rate if you are mining with -gen=1.
To see the network hash rate type getmininginfo
Thanks! mpos must be broken or something. |
|
|
|
The problem is, there is no prize bigger than getting MaxCoins faster than everyone else!
Depends. I don't know what a good value would be but there is a number that would give more coins as the prize than what they could mine in the time between when someone releases a GPU implementation (and someone will, no matter what, I'll do it if no one else does that's for sure). Not every developer has a huge mining farm. |
|
|
|
Many of us have built keccak miners, but probably none of them will work. And if they did, I don't think anyone is giving them away for many hours!
Hence the "prize" aspect.  Plus many developers like myself would do it just for the notoriety of being first. The thinking is "If not me then someone else will." |
|
|
|
|
Someone should offer a prize to the first GPU implementation (that is, working with relatively good performance). Probably won't take much work, just modify one of the existing Keccak miners.
|
|
|
|
|
Anyone know why the "gethashespersec" RPC call always returns 0?
How are pools showing the correct network hash rate?
|
|
|
|
any working not empty pool? I lost about 20 etok right now with murkanovic pool
We're up and working great as usual.  etok.cutk.com |
|
|
|
We're going 0% fees for the relaunch!! Mine with us, more profit for you.  meow.cutk.comWe're running fully updated on the latest Kittehcoin wallet relaunch code. |
|
|
|
Who owes the etoken.pool.digiraha.ee ..I have a problem with locked account ..I sent an email about 2 days ago at info@digiraha.ee but nothing That would be murkanovic. Send 'em a tweet. |
|
|
|
Thanks, I just updated from git and we are now running the new version (version 60401). All systems normal. |
|
|
|
Has new code gone to all the pools? I haven't heard anything.  |
|
|
|
Can someone fix the entry for our pool in the wiki? It's meow.cutk.com but there is a URL above it that looks like it's for our pool but in fact goes to cryptovalley.  Thanks! Is there specific time that the relaunch is going to be done tomorrow? BTW, the pool will be updated with the relaunch. PPLNS, VARDIFF, DDOS protection, always up, support is available. SSL via self-signed cert if you're so inclined. We strive for perfect proper and correct server management all the time. meow.cutk.com |
|
|
|
Yeah, it's probably just coincidence. A bad spot for a bit or something. |
|
|
|
Anyone know what's going on with the rate blocks are being found? Look at all the pools, each block is taking a crazy long time. I first noticed this on our pool last night when a block ran to over 600%. We have only had one block less than 100% in quite a while. Dumb luck? Why does it seem to be affecting all pools. Coincidence maybe? |
|
|
|
You might want to disable username based login. It's what we do. Otherwise random jerks can look at the pool list and lock all the non-anonymous accounts. |
|
|
|
Come to our pool. Everything still running smoothly. etok.cutk.com |
|
|
|
|
Has there been any mention of anti-ASIC features in this version of SHA-3? I ask because SHA-3 is specifically designed to be fast when implemented in hardware (that is one of the reasons NIST chose it) and ASIC hardware for SHA-3 has existed for at least 3 or 4 years which could mean this coin will get hammered with ASIC right out of the gate.
Or maybe it's intentionally designed to be like bitcoin and this is what they want, I don't know.
|
|
|
|
|
Show Posts
