Nothing magical happens.  It's just that you'll get a more accurate representation of your average payouts if you wait a week to compare.  Just like if you wait 2 weeks you'll get an even better picture - of course, if there's a difficulty change that happens, that will have an effect on your expected earnings.

It really doesn't matter.  It's your total hash that matters, not in how it's accomplished.

If the luck is good (around 100%) then you should expect to get approximately 0.004648BTC per day from your S3.


Turn on your S3
Point it to AntPool
Let it run
After 1 week look at your payouts.  If the pool has had good luck, you will see that your payments should be close to expectations.

It means that you aren't guaranteed to get that amount.  Some days you'll get less.  Some days you might get more.  There are a lot of things that determine what you get in actuality vs what the mining calculators say you should expect.

Stays until it's deleted.

No... I don't think you're understanding this.  I posted a reply to you in another thread that I will post here as well:

You need to understand how this whole thing works.  When you look at mining calculators, they are providing you an expected value.  They simply say, "Given the probability of finding X shares in Y time, you would expect to earn Z coins".  The simplified version of the formula they all use is:
Using an S3 as an example, and with current network difficulty of 47610564513:
There are a whole host of factors that influence that value in reality.  Pool luck, rejected shares, orphaned blocks, pool fees, etc all represent factors that affect your actual earnings vs your expected earnings.

LOL... that must have been an interesting conversation.

Phil - Honey, I think we've been in NJ long enough.  Let's sell our house.
Wife - Where did you have in mind?
Phil - Well, I was thinking about Washington.
Wife - Oh, Seattle is a beautiful city...
Phil - Ummm... no, I was thinking more like eastern Washington.
Wife - Huh?  There's nothing there!
Phil - Sure there is!  Spokane is the second largest city.  There's the Columbia river, the Grand Coulee Dam... we'll save a ton on power costs!
Wife - Alright, but the weather is nasty.  Hot summers, freezing winters...
Phil - Yeah!  Those freezing cold winters will be GREAT!
Wife - You hate the cold... what are you getting at?
Phil - Well, I found a nice place on 15 acres with a barn...
Wife - A barn??!!??  Why would we ever need a barn?  We don't own horses...
Phil - The barn used to house a welding shop...
Wife - So?
Phil - So, it's got a nice 200 amp service with 240V power...
Wife - And?  You're going to start welding stuff?
Phil - Well, no... not exactly.  I was thinking it would be a great place to put more of those Bitcoin miners.
Wife - Bitcoin miners.
Phil - Yeah, you know...
Wife - You want to move us across the country... and your reason is so you can have even MORE of those damn noisy miners?
Phil - Ummm.... yes?

Please note, the above is a completely fictional account of the conversation between Phil and his wife.  I was bored and thought maybe it might elicit a few chuckles.

In all seriousness, congrats, Phil!  I hope you and the wife enjoy your new adventures .

PS - can you host a couple miners for me?

No.  You can turn your miner off for 2 minutes.  The only effect will be that you have 2 minutes of not mining.  Will there be any effect on your payout?  Sure... but it's pretty minimal since 2 minutes is a pretty small percentage of a day.

While I don't truly understand what you're asking, my guess is that you're wondering if turning your miner off and on will have any effect.  The answer is that the only effect it will have is that you aren't hashing for 2 minutes.  Each and every single hash produced by your miner has an equal chance at being the one that solves a block.  There is no such thing as historical influence playing any role in future actions.  Each and every hash is independent.

Point your gear to a pool and let it ride.  Look at the stats.  If something is wrong, like extremely high reject rates, then you have to evaluate if it's your gear, or the pool that has the problem.

You need to understand how this whole thing works.  When you look at mining calculators, they are providing you an expected value.  They simply say, "Given the probability of finding X shares in Y time, you would expect to earn Z coins".  The simplified version of the formula they all use is:
Using an S3 as an example, and with current network difficulty of 47610564513:
There are a whole host of factors that influence that value in reality.  Pool luck, rejected shares, orphaned blocks, pool fees, etc all represent factors that affect your actual earnings vs your expected earnings.

The suggestion of waiting for a week is to allow everything to normalize.  You'll get a better idea of how a pool performs with your gear over a week's time than you will if you just throw hash at it for 24 hours.  For example, using the PPLNS method, you have to wait for that "N" timeframe before you're getting your full value payouts.

All things being equal you will earn the same amount of coin no matter which pool you choose.  Things are not equal though.  Some pools have fees.  Some are not ideally suited to the miner - example they are on the other side of the planet.  Some are poorly written.  Some are poorly connected.

I suggest you look through this forum and read the pool threads.  Figure out what works best for you and make your decision.

You can set difficultly on p2pool... just add +XXX after your BTC address.  For example, if you want to set your difficulty to 1000 you just put your worker as BTCADDRESS+1000 and password as x.  If you are on a node that has a high hash rate in comparison to your own gear (in other words, the node has like 100TH and you've only got 1TH, you'll also want to use the "/" parameter.  You do it like this: BTCADDRESS+1000/1000 for your user.  That will ensure your miner gets only diff 1000 shares and also tells the node that you will be submitting minimum difficulty share-chain shares.

Alright... seriously, you revived two posts over 2 years old each and posted exactly the same reply to each.  What's the deal?  Just felt the need to find old posts that mentioned pools that might hit that magical 51% mark?

And that's the truth.  Half the new pool announcements are "Come mine with us we use PROP!!!"  Arghhh.  Pool operators can't even figure out how to run their own pools or won't even bother to do a single bit of research on it, yet they expect miners to trust them with BTC?

Aren't the C1 and the S3 based on the same BM1382 chips?  The power consumption is going to be the same from a watts per GH perspective.  As far as how much space things take, with each C1 you've got a PSU, miner and water cooling equipment.  With the S3, you can drive 3 of them from a single EVGA 1300 G2, compared to the single C1 the same PSU could drive.

Honestly, it's a tough choice.  My opinion is to go with the S3s just because you don't have the added headache of the water cooling.

Very likely.  Unfortunately the original communicated request was pretty incoherent.  I'm assuming English is not his native tongue.  My reply was intended to get him to provide some further details on what exactly he's trying to do, or to hire somebody who can .

No, that should be correct.  In your S5 config you should have the pool URL as IP_OF_MACHINE_WITH_BTCD:8332 the user as your rpcuser in bitcoin.conf and password as rpcpassword set in bitcoin.conf.  Your bitcoin.conf file should look something like this:

Ensure you have proper port forwarding rules on your router (to allow the traffic over 8332 to go to your S5 from where bitcoind is running) and that you have port 8332 open and port forwarding rules to the machine on which bitcoind is running.

Please note, that you really shouldn't be doing this (accepting RPC connections from an external network) because your RPC password is transmitted in clear text.

I'd suggest putting together a business plan to figure out what you want to achieve, or go to the services forum to hire some folks to do it for you.  Once you've got that down, post in the services forum and hire some developers to code things for you.

Any operator who wants to run a PPS pool.  Honestly, I don't understand why any operator would even consider a PPS pool - the risks involved are all taken on by him.  I know I would not start such a pool, even if I did have an extra couple thousand BTC lying around the house.