If you want to be anonymous on a pool that uses usernames, just pick a name people won't recognize as you.

Same thing on a pool that uses a bitcoin address instead of a username. To be anonymous you have to use an address people don't recognize as yours.

What's the big advantage of using a BTC address as username?

Wow, awesome charts!

I had no idea there was still so much pool hopping. You can clearly see the pool hopping effect, even on Deepbit. Pool hopping on Slush's pool seems massive. I had no idea.

Why do people still mine there and lose so much income?

I guess Deepbit miners think "I only lose a couple percent to pool hopping, it's no big deal." But the loss from mining 24/7 on the other hoppable pools look like it is nothing short of massive. Pool hoppers put a serious hurting on your wallet.

Namecoins up and running again. Payouts have run already.

There was a big blockchain reorganization causing 5 orphans. Looks like there was a fork and for some reason our namecoind got stuck on the wrong fork. Very annoying. I was sure I had a recent enough namecoind. Can't see any important announcements on their website either.

Anyway, back to normal.

Namecoins up and running again. Payouts have run already.

There was a big blockchain reorganization causing 5 orphans. Looks like there was a fork and for some reason our namecoind got stuck on the wrong fork. Very annoying. I was sure I had a recent enough namecoind. Can't see any important announcements on their website either.

Anyway, back to normal.

No, I will get it running again

Merged mining will be back as soon as I have namecoind running stable again.

Yep. Unfortunately the namecoin program on the server suddenly failed. I had to turn off all namecoin operations for now, until I can get it running properly again.

Everything bitcoin related is running as normal.

I turned off namecoins until I can get namecoind working again. BTC blocks now confirming like they should and everything has been paid out.

One of those blocks actually was stale, it was Deepbit that got that one.

I even tried compiling the latest tagged release of namecoin from github and start it with no blockchain. It downloads blocks until block 141 then fails ("invalid blockchain"). That actually looks ridiculous. Not happy with namecoin right now.

Mining is running ok, but discovering blocks and their confirmations have stalled because namecoind is having issues.

Working on this right now. All blocks will show as stale until this is fixed - but they are not actually all stale.

That's right. Until a few days ago 70% of the hashpower was using the prepay perk. Now it's gone down to about 60%. It's painful when we hit an orphan. But I'm happy to see the perk is popular.


Yeah, I may have to do what one of you guys suggest, or raise the price of the prepay perk, or maybe something else.

I would prefer to just keep things as they are, as long as I won't lose hundreds of bitcoins when ASICs hit.

Does anyone know how often orphans occur with litecoins? They produce blocks at a higher rate than bitcoins. They also have much fewer pools though.

Nice graphs. Look at BitMinter go! How do you like them apples?

Why the wonky graph for Slush? I thought his pool wasn't hoppable anymore.

Wow, the growth of the pool right now is astounding. All the work I put into this pool is finally bearing fruits. It looks like something like 50 GH/s growth per day?

Thanks to all new users who are joining, and to the old ones who supported this pool for a long time already. Your support is much appreciated.

Also thanks for helping each other out while I take a few vacation days and respond more slowly to support requests. This is becoming a great community of miners.

About support for BFL ASICs ("SCs"): yes, BitMinter client will support them. I will work with BFL to make this happen at the earliest moment possible. The pool itself will of course also be able to handle these fast miners. Currently I'm pretty sure we can handle 4-5 TH/s and probably more. With SCs it looks like we will hit well over 6 TH/s. I am currently working on the server to support higher speeds, and also to set up more servers. I will do everything I can to make the transition to ASICs as smooth as possible.

I will take that under advisement.


Yeah, it's a new record! 13 blocks in 24 hours, and also over 1 TH/s hashrate.

I'm just on vacation for a few days and not spending as much time on the pool right now.


Thanks for your support. Happy to hear you like the pool. No, I'll need to require a BTC donation for instant BTC payout. I'm a bit worried that 1% donation is too cheap. A couple orphans can totally wreck the pool's meager income. But I will try to keep that going. I'm worried about the early days of SC though, the accelerated rate of block generation will cause more orphans than normal.


We seem to be stable over 900 GH/s now, will update the title. And thanks for the donations, good sir, it is much appreciated.

Windows 8 has some network behavior that Java doesn't handle well. You can try upgrading Java to the latest version. I believe it was fixed in the latest Java 6 version, hopefully also in Java 7.

Also, even with the bug you can run an old version of bitminter client which has some older (non-async) networking code, as posted earlier in this thread:


Of course 1.1.2 is lacking a lot of the goodies that are present in later versions. So it's probably worth a shot upgrading Java.

Hmm, thought I had fixed account details so BTC is always listed first. Have to look at that again.

And yeah, the hashrate is too high to display on the site. What to do!?

There's been cases where botnet operators have been mining in pools and gotten banned. Then they get angry and attack the pool with a DDoS attack. I thought that's what we were talking about. If botnet operators stop mining we'll see less of this.

No, you can see here that there are people using ufasoft: http://bitminter.com/miners

I think you'll have to ask in the ufasoft thread how to get it running. Or perhaps someone reading this who is using ufasoft can give some advice.

Try:
"C:\Program Files\Ufasoft\Coin\coin-miner.exe" -o http://mint.bitminter.com:8332 -u USER_WORKER -p PASSWORD

where USER, WORKER and PASSWORD are replaced with the ones you are using. Note the underscore (not hyphen) between user and worker names.


That's the spirit

What's the error? Never used that miner. Looks like you are missing a space before -o and I don't think you should have a space before 80. Also, please use port 8332 unless you have a firewall blocking you so that you must use port 80.

Probably the password should go in there somewhere too.

Haha  Donation sent


Thank you


I hope it will reduce the frequency of DDoS attacks, as there won't be huge CPU mining botnets anymore. But the last big DDoS attack on multiple pools was about extortion. They demanded money before they would stop the attack. This is more of a general internet problem.


It works well, except 1% donation to get paid for orphans is probably priced a bit too cheaply. Currently 1 orphan will wreck the income of 70 good blocks for the pool (70% of the hashpower use this perk and average BTC donations is 1%). Raising prices is never popular though. I'm thinking about more perks and other non-free services, so I'm very interested to see how this works out for Ozcoin.

Since CPUs are so slow it has not been a priority to improve that. You can use any miner you want on the pool, just connect to mint.bitminter.com on port 8332. As login use username_workername where username is your bitminter username and workername is the worker account you want to use. Note the underscore _ to separate them. As password use the worker password.