Again, you must take all factors into consideration.  If Bitcoin goes to $600, chances are very good that more people will mine it.  This will increase the network hash rate and thereby increase the difficulty.  In turn, you will earn less BTC for your hashing power.

Just for the sake of argument, let's say that today the price of Bitcoin shoots up to $600, and all else remains equal.  Your S3 will still earn you 0.004648BTC a day.  However, instead of being worth $1.08 (with BTC at $233) that same coin will be worth $2.79.

Change in network difficulty affects expected BTC earnings.  For example, right now the difficulty is 47610564513, which leads you to the expected earnings of 0.004648BTC a day for an S3.  If difficulty goes up, your expected earnings go down.  Conversely, if difficulty goes down, your expected earnings go up.

These are the main considerations that will help you gauge whether or not mining gear is profitable.

Remember the fun days of extreme overclocking?  People would drop their Pentiums into liquid nitrogen to try and get the most possible speed out of the chips.

I agree the cooling performance of the liquid would certainly degrade the more boards it had to deal with, and perhaps the optimal limit is indeed what the C1 offers.  I know there were some folks doing total immersion tests with the Spondoolies boards to get some crazy density.  It would be interesting to see how far these things can be pushed.

The problem isn't the dependence upon the fee of the previous transaction, but rather that the OP used unconfirmed inputs in his transaction.  Yes, those inputs were unconfirmed because the fee was 0, but the OP further complicated the matter by using those inputs in his own transaction.

As DannyHamilton mentioned, unless a pool is using a look-ahead method to know that by confirming the unconfirmed inputs they will be receiving fees from the child transaction, OP is forced to wait for those inputs to confirm.  Since it appears the transactions finally confirmed, everything is good to go.

Unless you've got a way to access the private key of the wallet on your Z10, you're SOL.  You'll still be able to see your coins on the blockchain by looking at the address (assuming you know the public address)... but without the private key, or getting your Z10 back up and running, those coins are effectively lost.

Mining for the small individual is getting harder and harder, even though the difficulty changes have been leveling out as of late.  Fewer and fewer hardware manufacturers produce home mining gear, concentrating instead on the larger scale industrial miners.

The official p2pool repo is forrest's: https://github.com/forrestv/p2pool/

Rav3n's got his own that has support for a boatload of alt coins: https://github.com/Rav3nPL/p2pool-rav

When you restart p2pool, the UI resets your local share count to 0.  You don't actually lose shares on the chain, it's just that the UI only tracks shares found on your node since the last restart.

The text one will be very similar.  Instead of printing out your counter variable, you just print the text over and over again.


You'll have to explain the third task a bit more clearly.  Are you supposed to prompt the user to actually tell you whether to show odds or evens?  Or are you just supposed to count to 100 by odds first, and evens second?

Think about that third task and try to put it into terms like I did for your first task.  How do you count only the odds, or only the evens in your head?  How would you do it on paper?

Assuming he's been spending 1BTC a day to rent gear, his first block was on 4/17.  11 days, 5 blocks, near 125BTC.  For a cost of 11BTC.  Now that's a win!

Holy freaking mother loving gods on a stick!!!  Another block goes to 727miner.  Whoever it was earlier (think it was mikestang) who said the Pattern weaves around him was surely not mistaken.  Unbelievable this guy has found 5 blocks with around 200TH/s.

Congrats yet again!

Each of these exercises requires you to understand looping constructs.  The first one asks you to repeat a task 10 times.  The second asks you to count to 10 and the third asks you to ... well, I think you wrote the third one down wrong because showing only even or odd numbers will show them all - unless you're supposed to prompt the user to enter whether or not he wishes to see evens or odds?  That seems a bit more complicated than the other two which are simply asking you to understand loops.

Loops in programming are very similar to how you'd think of repetitive tasks in your life.  For example, let's look at the first task.  How would you do it on paper (without using computer code)?

1) Look to see how many times your name has been written
2) If your name has been written fewer than 10 times, write your name
3) Repeat

You could also express this as a sentence:

I will repeatedly write my name until I have written it 10 times.

By doing this, you have given yourself a task that must be repeated until a condition is met.  Let's think of that sentence in another way:

While I have written my name fewer than 10 times, write my name.

So... you need a way to count how many times you've written your name, a way to write your name, a way to increment your counter, and a way to repeat those tasks.

We would start our counter at 0 because you haven't written your name yet.  Now, you start your repeating loop.  Is the counter less than 10?  If yes, write your name and increment the counter.  Do it again.  Now the counter is 1.  Is that less than 10?  Yup.  Write your name and increment the counter.

Now let's think of it in terms of code:

Initialize counter to 0.
While counter is less than 10:
 * Write my name
 * increment counter

I hope this helps, and allows you to follow along with your other 2 tasks.

I know you typically don't pay attention to anyone with a signature campaign; however, in the interest of providing clarity to the part of your statement I bolded, you are missing a few zeros.  An S4 is a 2 TH/s machine, meaning it will complete 2,000,000,000,000 hashes per second.

Using bitcoinwisdom.com reported network hash rate of 347.453128 PH/s, (as of the writing of this post) and an average expected block time of 600 seconds, one would expect a total of 2.084718768x10²⁰ hashes worldwide to find a block.

I'm pretty sure the pool starts you off with a difficulty of 1042.  Once you hit that difficulty, it adjusts according to your perceived hash rate, so you then start to see accepted shares as you typically would.  For example:

It means that the pool has accepted a share.  Unless that share is over the network difficulty, it's just informational.

I've got 5 Antminer U2 that are pointed to ck.'s solo pool.  Every week, assuming they're not rented out, I point 6 of my S3s there for a day as well.  You never know if they'll hit .

@alh, 727miner has hit 4 blocks in less than 2 weeks on ck.'s solo pool.  Yes, he rents.

Agreed.  You can come up with countless use cases and build monitoring agents accordingly.  I guess my main concern with your script is precisely because it is attempting a connection.  Some people tune their nodes to set max connections.  If your node has already reached the max connections, your script will falsely report it as being down simply because it cannot connect.

I suppose you could do a combination of things like:
1) Check to see if the process is actually running (my suggested script)
2) If 1 is true, check to see if it will accept incoming connections (your script)
3) If 1 is true, but 2 is false, see if you can retrieve data from the daemon using bitcoin-cli
...

I'm sure we could come up with a bunch of other tests to monitor things

LOL... of course it does.  Where've you been for the past couple years?

Last year on this date, that S3 (440GH/s) would have expected to make 0.03171BTC daily.  Now it expects to make 0.004648BTC a day.

That code actually attempts a connection to the bitcoin daemon, which if you're just checking to see if the process is running might be a bit of overkill.  Why not just do something simple like:

OP has been asking the same question in multiple threads.  I answered him in quite a few of them.  Apparently he's from Georgia and his English is about as good as my Georgian .  It's definitely a lost in translation thing.

OP, I hope you can get somebody to translate these answers for you.

In a nutshell, yes.  Legitimate services have a bunch of hardware that is mining.  They charge you some BTC for some portion of their hash rate.  You earn coins based on the hash rate you purchased.  There are a variety of contract types.  Some will charge you X up front for Y time.  Others charge you X up front and Y in maintenance fees for unlimited time.

Be extremely careful.  There are far too many Ponzi schemes out there posing as cloud mining services.

Everything there still applies.  @roy7, you put the address still in case some miners connect to your node without a proper BTC address.  Even if you're not collecting fees, the node will consider any improperly formatted BTC address mining as a donation.