If you've found the block, you've already mined the correct hash to add it to the blockchain.  There is no more mining that needs to take place on that block.  Of course, finding a solo block with 10GH/s... well, at the current difficulty, you would expect it to take nearly 673 years.  That hasn't stopped me from pointing my 5 U2s at ck.'s pool, though.  I've got a 1 in 245579 chance of finding a block today .

Thanks for the continued work you're doing on the S3, kano!

Ok... That's a good thing.  The other thing though... That's not something you want to do.  If you need some capital to maintain the servers, charge a fee and be up front about it.  You're going to be in a whole heap of trouble if you try skimming.  Food for thought.

But you're skimming off the top.  You aren't paying the 25BTC when the block is found, you're paying out 24.7.  That's affecting the miners and except for your previous post that wasn't made public.  And how are you paying out that bonus coin?  Is that coming out of the 25 coins from a block find as well?  If so then the first five blocks you're paying out 23.7 of 25 coins.

No.  All it does is show you don't understand how PPLNS pools work.  Let me clarify things for you.

In a PPLNS pool, miners do not get paid unless you find a block.  Miners get paid for their shares.  Do you even know what your "N" value is in your pool?

Take for example kano's pool (http://www.kano.is).  The N value there is 500% current difficulty.

A miner has to ramp up to get a full amount of shares in that N period, but he gets paid for his contribution for every block found in that N timeframe.  The pool's luck plays into how many times a miner gets paid for a share during that N time.  If the pool finds more than the expected number of blocks during that time, the miner gets paid more times for that share than expected.  If the pool finds fewer blocks, then the miner gets paid fewer times.  If the pool finds no blocks at all, then the miner does not get paid.

Clear enough for you?  I really suggest you take some time to learn about these things if you're expecting to run a pool.

Ummm.... that's not how it works.  You don't need to build up your wallet for PPLNS.  The pool pays out when it finds a block.  What you're suggesting is that for the first X blocks nobody but the block finder and you the pool operator are going to get anything... 1BTC to the block finder and 24BTC to you so you can build up your wallet?  Who in their right mind is going to mine here???

If you're looking at the default front end, the expected payout figure comes from the payout address of the node.  When you setup p2pool, if you didn't specify one, a p2pool address was created for you in the bitcoind that it connects to.  Unless you're mining to that address, your expected payout will always show 0.

Take a look at windpath's node (http://minefast.coincadence.com/miner.php) and enter your miner's address there.  You'll see your expected payout, and what you've earned in any blocks that p2pool finds.

Somebody wasted their time directing a DDoS attack against a pool with a total hash rate of 11TH/s?  Wow... who'd you piss off?

EDIT: by the way... what does "future PPLNS" mean?

What do you mean the core is encrypted?  Do you mean the wallet is encrypted?  If so, no...

Just because IBM demonstrated it is possible to achieve a 7nm process doesn't mean it'll be here next year by any stretch of the imagination.  I'd guess 2020 before 7nm is produced in a consumer chip.  They've got to go through 10nm first.

Down at the bottom of the page you'll see a nifty little link called "move topic".  Click it and put the thread in the appropriate board

You're asking this in the wrong place.  This should be moved to alt-coin mining: https://bitcointalk.org/index.php?board=160.0

1 - yes
2 - yes, just install the new one
3 - you don't "have" to... but it's far better to be safe than sorry.  Copy your existing wallet.dat to some location before you start any upgrade process.  This way, if something blows up in the process your wallet and coins are safe
4 - typically no.  If everything went smoothly (which it usually does) then you're good to go.  If there were problems, you've copied your wallet.dat file to some other location, so your coins are safe and sound.

The use case would be to have a nicely packaged API library that you can just drop into your site without having to write it from scratch.  Why pay some developer to write the interactions with your wallet, when you can just grab an open source library that already does it?

I expected quite a large set of the initial blocks to be empty - after all, a tiny subset of people even knew what Bitcoin was.  However, the thing that really grates on me is how many empty blocks there are when there are most certainly transactions waiting to be included and confirmed.  For example, we've been having our fun little stress tests recently, yet AntPool has continued to mine empty blocks.  At one point I noticed nearly 20k transactions, but AntPool happily submitted a block with not a single one of them.  Oh well... separate debate for another thread

You have described a risk that is inherent in any rental system, and one I have written about previously.  The owner of the gear has no incentive whatsoever to actually solve blocks.  He's getting paid as long as the hash rate he's providing is consistent with expectations.  For example, on MRR, the rig owner sets a price per GH/s of hashing power, and if you decide to rent his gear, you pay the set price.  As long as that gear performs well (basically over 90% of advertised rates), the rig owner receives the payment (minus MRR fees).  Why should the gear owner care if you solve blocks?  He's been paid, so it doesn't matter.

Now, as a rig owner, and one who rents his gear out on MRR, I have every incentive to actually have my gear using proper mining software (my S3s are all updated with kano's latest cgminer 4.9.2).  Why?  Because when my gear isn't rented, it's pointed towards my own p2pool node, or to ck.'s solo pool.  I absolutely want to be able to solve a block .

Nice job windpath!  I actually started my own Java project very similar to this... I wrote some code to do some data mining on empty blocks (see my thread here: https://bitcointalk.org/index.php?topic=1085800.0).  Mostly I wrote the code for fun, but realized that I could expand it to provide a nice object-oriented view into the core APIs.  That expansion has been started, but is nowhere near completed at this point, and I haven't put anything up on github yet.  I know there are a number of available libraries already out there (like BitcoinJ), but being who I am, I wanted to figure things out on my own .

I'm looking forward to your progress with this project.

With your "average" power costs, I'd be looking into a hosting provider that could do it for me cheaper.  There are a number of options available to you in that realm.  Find out how much capacity those providers can offer you.  Just as an example, if you were to grab the S4+ from Bitmain, you could get about 250 of them (they're about $1000 each).  That's going to get you 642.5TH/s of hashing, and will have 370kWh power consumption.

The S5 is more efficient, but requires you to also purchase your own PSUs to power them.  With the same $250,000 budget, you could get 550 S5s and 275 APW3-12-1600-B2 PSUs from Bitmain (well... you'd be just slightly over your budget there).  You could probably find better PSUs... I was lazy and just used what Bitmain has for sale... ...550 S5s will get you 635.25TH/s for a power consumption figure of 324.5kWh.

Assuming $0.05 cost for electricity... (if you can negotiate that with a provider)...
The S5s would expect to make you $1739 - $389.40 = $1349.60 a day
The S4+ would expect to make you $1759 - $444 = $1315 a day

If we assume those expectations stay constant (which they don't, but for the sake of this discussion), you're looking at ~185 days to recoup your initial investment with the S5s.

Your transaction has been confirmed.  Transactions have taken considerably longer than it typical over the past few days because of an excessive number of transactions being blasted onto the network.

Oh you poor, poor soul.  Why would you torture yourself like that?