The first KnC Jupiter that has been earned through the reseller link at Bitminter will be the prize for the november mint race! Note that we don't know when these reseller units will be shipping. More information on that when the information is available from KnC. You can read more about the Jupiter device at https://www.kncminer.com/?resellerid=299 (also use that link to buy!)

Got 5% of the pool hashrate? That's a 5% chance to win 1st place. Even for smaller miners the chances should be better than most lotteries.

The race is open for everyone. All you have to do is mine at the Bitminter mining pool.

Start: friday 2013.11.01 at 00:00 UTC
Finish: saturday 2013.11.30 at 23:59 UTC

The prizes are:

1st place: KnCMiner Jupiter 550 GH/s ASIC device (currently selling for $4995)
2nd place: BTC Trinkets bitcoin miner lapel pin
3rd place: BTC Trinkets bitcoin miner lapel pin





Update: added bitcoin miner pins. Thanks, BTC Trinkets! More details on the pins at http://btctrinkets.com/presta2/index.php?id_product=26&controller=product

Rules:

• Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) hashes during the race will win.
• As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list.
• Each person can only compete with one (their best) hash.
• If a winner cannot be reached within 1 week, the prize will go to the next on the list. You may want to make sure that the "account details" page at bitminter.com has an email address listed for you so that you are easy to reach.
• Any block by DrHaribo will not count in the race.

Verifiability:
Hopefully your mining software will show if you have created a block (BitMinter client does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (leftmost column) to see details. There is a link there to blockchain.info where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple.

CURRENT STANDINGS: see https://bitminter.com/mintrace

The timestamps on the live stats page are for when each statistic was last fetched from the server. Normally that would be the same as UTC, which is what the website uses. But if there was a problem fetching stats it could have fallen behind a bit.


Yes, the income from the block is of course paid out.

And yeah, blocks created from zero work is due to pure awesomeness.

Try this calculator to predict earnings: http://mining.thegenesisblock.com/

The problem is predicting the future difficulty.

Some info on Bitminter payouts: https://bitcointalk.org/index.php?topic=27062.msg2769824#msg2769824

There's no way to tell from the address. If you have accounts on btc-e and/or vircurex then check those.

You can't currently see the pay per shift. You can see the amount of work per shift at https://bitminter.com/shifts and you can see your pay per block if you go to "my account" -> "transaction history" in the website menu.

I could probably add how much the user has been paid for each shift in the shifts page, though.

If you are struggling with getting your ASICMiner blade going, have a look at this: https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129

Specifically to the person having problems right now, don't forget the colon in the credentials. Just put a colon and an X as password. Even though we don't use passwords anymore, the server still expects name:password for basic authentication as per the HTTP standard. Unfortunately the blade interface makes you type in the colon yourself, as if it expects all miners to be programmers.

Congrats Thanks for describing what fixed it for you.


Most likely the erupters don't get enough power. Did you try plugging one or two of them directly in the computer, with the rest on the hub?

Useful advice: https://bitcointalk.org/index.php?topic=27062.msg2998466#msg2998466

Ladies and gentlemen, we are breaking the 200 TH/s barrier.

Update: Cloudflare, our content delivery network provider, is having issues in London, Frankfurt and Paris. They are working on it.

Sounds like a Cloudflare outage in the UK. I'll see if I can get a hold of them.

But this is also not good:

https://www.cloudflare.com/support

Not Found

The requested URL /support was not found on this server.

Namecoin value really took a nosedive lately after it was discovered that the current implementation is completely broken. It hasn't helped that a fix has been created to deal with the problem. The NMC difficulty also went up a lot after BTCGuild added merged mining. Put those two together and NMC is now down to being 0.58% extra income. IXC and DVC are much worse though, at 0.05% and 0.01% respectively.

What would happen with I0C if some big pools start merged mining it? This is a coin that is worth much less than IXC. Maybe we could make a tiny bit more for a couple weeks before the difficulty goes up and the extra income you get from I0C would be 0.02% or less. That's not worth the effort of getting it up and running, and keeping it running, an old unmaintained codebase that is full of bugs just like namecoin. I0C is only worth mining if very few people are mining it plus the pump and dump scammers are in the pump part of their cycle, driving the price up.


The pool time isn't actually shown anywhere. Where did you get the 11:20 timestamp? What time was your own clock at the time?

Port 80 getblocktemplate is also HTTP, should also play nice with your firewall, and won't run out of work.

Make sure you are allowed to run the device at your workplace.

There is a stratum header causing cgminer to switch automatically to Stratum (port 3333) if you connect by getwork or getblocktemplate (port 8332 and 80). So he'd have to force cgminer to not switch to Stratum. Using the --fix-protocol option I believe? Not sure if cgminer then uses gbt when connecting by HTTP with --fix-protocol or if you need to do anything else?

If you have to use HTTP then try getblocktemplate (gbt). It uses more bandwidth than stratum but you won't have problems getting enough work. getblocktemplate, like stratum, is based on the mining server giving your client a template, and your client using the template to generate its own work.

getblocktemplate is available on the same ports as getwork (8332 and 80) on mint.bitminter.com

Maybe someone remembers how you can tell cgminer to use getblocktemplate?

Waiting for work should never happen with Stratum or GBT. Sounds like you are mining with the getwork protocol.

There's no DDOS. Mining service running as normal.

Is this with the web interface on the Jupiter? Port 3333 on mint.bitminter.com?

The namecoin daemon stopped propagating our namecoin blocks, that's why we have a string of "stale" blocks. Should be OK again now (for future blocks).

Apologies for this. Namecoin was abandoned by its developers in a state where it was full of bugs and nearly unusable. You don't notice it but it is actually crashing frequently and being automatically restarted on the server.

I'll have a look at whether the new "namecoinq" is more stable.

If you hold your mouse pointer over the column headings you will get a tooltip explaining them. The hashrate is just an estimate. Accepted infinity means all accepted proofs of work for all time. Accepted round means how many accepted proofs of work you got this round.

The namecoins are created using bitcoin hashes. This is allowed by the Namecoin system as it supports merged mining.

If you don't want those free coins that don't slow down your Bitcoin mining at all, then you can set Namecoin donation to 100%

I don't know of any problems. If you leave me your Bitminter user name I can have a look in the logs. You are connecting to mint.bitminter.com on port 3333 ?


Difficulty when using Stratum is per connection not per worker. Bitminter will choose a difficulty for the connection that is suitable for the fastest worker using the connection. That can be a little heavy for workers that are considerably slower.

Setting up two Stratum connections, for instance with Stratum proxy, should work. I'm not sure why you are experiencing problems with that. If you want the difficulty on the old proxy that you had already to drop then you may have to restart it.

By the way, if you have problems with nonce2 size 6 bytes, you can choose 4 bytes (more common) in the worker options.

That was an old cgminer version that had a bug. It was fixed very quickly and a new version released.

There's no such problem with new versions of cgminer.