Another update to the pool for you... Now your average hash rate graph will show in TH/s instead of the KH/s it did previously.  For example, here's a snapshot of mine:



Enjoy!

It most certainly isn't number 2.  The bandwidth requirements for a miner connected to a pool are pretty tiny.  Even if you were sending an entire block (which you aren't) and every block was max size (which they aren't) you'd still only be sending 1MB across the wire every time you submitted a share to the pool (which is usually about 12 to 18 times a minute).

You might want to check out your miner to see if there are a high number of rejects or hardware errors.  Those could certainly be a factor in what the pool reports vs what your miner reports.

The S3 at standard clock speeds should hash at 441GH/s.  The S3+ at standard speed hashes at 453GH/s.

So far it does, and it will certainly be welcomed .

So I read that article and the entire premise is socially engineered attacks against targets to discredit them.  I'm not sure the title is appropriate.  Maybe it should be, "Destroying the Value of a Crypto Currency".  How many times have we seen pump and dumps of alt coins?  Campaigns to promote the coin's value.  Lots of trade activity.  Promises of some new revolutionary feature.  Upcoming acceptance by respected and known entities.  You get people excited enough, the value of the coin goes up and you make a killing.

That's actually the biggest pitfall to renting with NH/WH - the fact that you can be outbid.  As you saw, it can cost you a ton of coin to maintain your expected hash rate.  Sure, it may cost the small renter an extra few bucks, but if you've got a significantly sized rental, any increase corresponds to a pretty big expenditure.

If you try to wait it out you'll end up going for long stretches of not hashing at all.  Of course statistically you'll still end up with the same number of hashes whether it takes you 24 hours or 168 hours to get there; however, if there happens to be a difficulty increase during that timeframe, your hash has that much less of a chance of hitting the block.

I try not to get caught up in the bidding wars.  Most of the time it means my hash rentals are sporadically connected.  I also never try to take over the entire hash rate, either.  That leads to exactly what you posted about - everyone wanting their own rentals to be hashing and the bidding wars start .

Nice tax return .  Good luck with your solo mining adventure!

Depends on whether you're overclocking them.  Stock S3 speed of 441GH/s pulled 340W from the wall.  The S3+ (running at 453GH/s) pulls about 355-360 at the wall.  You're pushing the limits of your 750W PSU with those - the CX750 I mentioned earlier can push 744W total to the +12V at 62A max load.

Yeah, you can run 2 S3s off a 750W PSU.  They pull 340W from the wall each, so you're pretty much right in the sweet spot.  Best bet is to have a single rail PSU and the CX750 will fit the bill nicely.  2 PCIe cables per S3.

That's the S3.  441GH/s.  The S3+ was 453GH/s.  If you were lucky you could overclock them to 504GH/s.

You assume correctly.  Those numbers represent how many times a second the device executes the hashing looking for a valid block solution.  You can easily calculate the daily (or hourly, weekly, whatever timeframe) expected earnings for a device given its speed and the current network difficulty.  The equation (simplified) is as follows:

So, if you wanted to know how much an Antminer S5 (1.155TH/s) would expect to make in a day if it were mining right now:


Those are the proper terms.  A USB stick relies upon a host computer to execute the mining software and a powered USB port.  Therefore if the computer providing the power to the port, or running the mining software is stopped, so too is your mining.

There are other miners out there (I mentioned the S5 above) that are self contained.  You plug in a PSU and a network cable, then use a web browser to configure it.  You can then turn off your computer.


Minimal bandwidth required.  You're sending and receiving small bits of data from a mining pool.  Unless you're running your own pool or a full bitcoin node whatever you have currently should be more than sufficient.


If the mining software can't connect to the pool, then your mining hardware would be sitting idle.  You don't need to reconfigure.  One thing I want to point out here (and it's bold because it's important): there is no such thing as progress.  You aren't executing a progressive series of calculations the cumulative effect of which produce a block solution.  A share either solves a block, or it does not.


Well, what's your definition of cheap?  $50?  $500?  $5000?

USB devices are exceedingly unlikely to ever turn a profit.  If it's just a "for fun" thing, or perhaps a lottery ticket you point at a "solo pool" then have at it.

Wow rental prices are crazy.  Over double expected payout... what pump and dump alt is being mined to death now?

You could always run your own p2pool node... you'd know exactly what kind of payout to expect because you'd be the one setting the values

The upgrade to 0.12 shouldn't cause a re-index.  I built 0.12 in the background while 0.11.2 was running.  When it completed, I simply stopped 0.11.2 and started 0.12.  That, plus doing some server updates and rebooting everything had a total down time of about 10 minutes.

Don't forget the promo is still running... we just crossed the 50% mark (now about 50.8%) of expected shares to find the block.  Find a block before we hit 110% and get 1BTC bonus from me.

If you are using the default trust list, then typically for other people to see Laviathon's trust number be other than 0, someone on that default trust list would need to leave him a positive feedback.  Kristgt30, you should see a positive number there because you have left him positive feedback.  However, unless the rest of us have you in our trust list, then we all see his trust number as 0.

In other news... I notice you are suffering from the same problem I was in your round stats page.  While the following won't address your current rounds, it will fix your future round stats.

Log into your database and execute the following statements:


The problem was that the standard MPOS structure had those columns defined as INT(11), meaning the max value is 2³¹-1 i.e. 2147483647 - look familiar?

Anyway, I also had that PR merged into MPOS on github so future installs won't suffer the same stats issue.

Unfortunately combining our pools would be exceedingly difficult to properly pull off. 

When I started this pool, I did so to give miners a choice where to point their hash where they wouldn't get screwed by a jackass like nexious.  It also gives miners a choice to not point their hash to bad-for-bitcoin pools who SPV mine, spit out empty blocks, etc.  I'd love to get a few percent of those pools pointed here.  I'd also love to see a few percent pointed to BCMonster (as I'm sure he'd love to see, too).

If you've checked out his thread, you'll see I share my pool changes with him as well.  You can also see that I've contributed to the git repository to address the capped share stats error pointed out earlier in this thread.  I will be sharing that with BCMonster as soon as I finish writing this post.

So, if you want to see this pool grow, please feel free to spread the word.  Post on your social media accounts, websites, blogs, forums.  Talk to your friends and family.  Let them all know your experiences here and invite them to join us in this grand adventure in bitcoin.

Your miners wouldn't have shut down, they would potentially have just failed over to backup pools.

LOL... I also changed the Worker Information on your dashboard page.  Now it displays your workers in GH/s (instead of the KH/s it was defaulted to).

Fixed that one as well on my pool... I ended up putting my worker stats page in GH/s, though.  Pretty easy fix.  First, I edited templates/bootstrap/dashboard/worker_information/default.tpl.  Changed the "Hashrate" label to read "Hashrate (GH/s)":


Next, I edited the "refreshNetowrkData" function in templates/bootstrap/dashboard/js/api.tpl to change the displayed hash rate from KH/s to GH/s:


Enjoy.