Why not join the p2pool network? No fees, no outside person in control of pool operation, and very de-centralized. And hey p2pool could use the extra hash power right now!

Ok cool. I think on VTC you might be solo as well, if you want to double check it.

I merge mine Namecoin on UNO and BTC. That's it so far. Haven't tried United Scrypt, Huntercoin, etc.

I have various patches applied but I didn't realize that would increment the version number. I'm running forrestv's repo for BTC, p2pool-n repo for VTC, and rav3n's repo for Uno. Here's a graph of my p2pool fork for BTC:

https://github.com/roy7/p2pool/network

Looks like I'm only running mmouse's minerstats and my own vardiffbyaddress. However I thought I also had iongchun's auto-worker-diff applied, but maybe I never pushed that up to my fork. If I have time tonight I'll clean it up some.

You must be unlucky? The interface tells me the time to share for 186 GH/s is currently 4h 3m 37 s. I don't see how/why bitcoind would mess you up. I'm also running 0.9.1.

Oh I've had some. I just restarted it a day or two ago. I was trying to find some ways to reduce the orphans further. I guess I could plot orphaned shares too. Next step for the interface is to add a list of all shares at the bottom like recent blocks.


The main thing I'm trying at the moment is using -n to connect to the largest public nodes I can find. This way my shares might get spread more quickly, and/or I'll get updated on someone else's shares more quickly. I added the couple nodes with the highest hash rate I could locate, as well as one that had the highest incoming/outgoing connections.


I don't actually know on that one. I assume share orphans are more a factor of the speed your found shares make it out to the network vs other people's found shares. If all users have the same orphan rate then the orphans don't matter, because we all get a proportional amount of a found block.

My pleasure. Here's my one S1 that I own:

http://us-east.royalminingco.com:9332/static/miner.html?id=1Gtt49xTxD3udiKcMfuzK37oJu1pGbnr8A

Click on Week or Month and you can see more of my share value history over time.

Also remember for BTC the 3 day thing is just the max capacity of the window. It's really supposed to be 3 blocks worth of work on average. So once the pool start finding blocks faster than 1/day, shares will last less than 3 days.

Hi jonnybravo0311. I will try to help.


Yes. BTC has a SPREAD of 3 and a maximum share chain of 3 days worth of shares. If block times get over 1 day on average, the share window will be smaller than SPREAD since we hit the 3 day cap, but your example fits perfectly.

Since shares are good for 3 days in your example, after mining 3 days if we're nailing the average like clockwork, you'd have 18 shares in the share chain (6 per day * 3 days). So the value of a share would be .01 BTC / 18 so that your one block per day pays out .01 to you.


So we're assuming the pool is supposed to find a block every 24 hours on average, but it is a really long round. Nothing really changes. You have 18 shares in the chain that total .01 of value, when this block is found you are paid .01. So you've made less income over these 4 days because of bad pool luck. I don't know what CDF a 4x longer than expect block is (it could be calculated but I'm doing my taxes and I'm tired), but keep in mind the 5% chance you hit a bad luck 95% CDF round is the same as the 5% chance you hit a 5% CDF round. Over a long enough period of time the average CDF of all blocks found should be 50%.


You have zero shares and so get paid nothing. Orphan rates should be somewhat similar across the p2pool networks, but a node that is super fast and efficient might have a lower orphan rate than some other poorly connected slow node. This gives an advantage to the better/faster nodes. The efficiency % in most interfaces is a way to try and measure that.


At the time the block is found you have 2 days of shares in the share chain (since day 3 was all orphans). That means 12 shares instead of 18 shares, giving you 2/3 of your normal payment. .00666666 instead of .01.

The max share chain length was increased to 3 days instead of 1 day at some point in the past, when the share chain was slowed down from 10 seconds to 30 seconds.


If you are supposed to find 6 shares/day at your hash rate but get lucky and find 8 instead, then you're making about 1/3 more than normal. Or .01333333 per block instead of .01. If the pool is supposed to be finding 1 block a day but is constantly lucky and finding 2 instead, then you are getting two .01333333 payments per day. In total making .02666666 vs .01 per day. Of course, you are equally likely to have bad luck in the opposite direction and given enough time it will average out to .01/day.

I hope 1- this helps, and 2- I didn't actually get any of this wrong.

What I did on one of my sites running nginx and php was to use xcache to store the results of database calls for a period of time. I had wrapper functions for any database info I needed, and would cache the result for 30 seconds up to 15 minutes depending on what it was. This way even if someone did an endless spam of page reloads, it'd only affect the web server and the database server wouldn't even notice. Maybe something like that would help.

Personally I'd just like to see them change the view on mining activity, that the cost basis for all mined coins is $0 and you realize a capital gain when selling them. Thus you have far less record keeping issues. For example, what if you mine an alt coin on p2pool and receive dozens of payments per day? The paperwork to report each one of those on your tax return is madness. Better to just gather it all up, and report a gain when you eventually sell the coins or exchange them for property of some value.

What's the purpose/advantage of removing the block punishing code? That's an area I've never looked at and am clueless about.

My apologies for contributing to that. I hate it when it happens on other threads.

I never realized that. Thank you. I guess I assumed it was the block with the highest value (transactions) or some other tiebreak. So a miner may collect 2-3 blocks found at the same time, but will keep working on the one they heard about first. As soon as someone finds a 2nd block, the one they were working on becomes the "real" block since they have a longer chain and the other blocks are now orphaned.

If two miners working on different blocks also find 2nd blocks at the same time, they keep mining separate chains until someone first finds a 3rd block for one of those two chains?

Thanks for the education.

I notice your UNO node is running solo and not connected to the rest of the p2pool network. Is that intentional?

Were the ATMs somehow tied to MtGox?

p2pool won't work until bitcoind has finished downloading the block chain

I've been running my 180GH/s on p2pool lately and it's not that bad. Yes the average block time is 1-1.5 days, but I'm okay with that myself.

Whatever your payout is supposed to be based on the shares you have submitted, you'll get it in the coinbase generation section of the block itself. The pool doesn't pay you anything directly, your payment will be built into the block itself.

With CORS wouldn't the miner need to run a mini web server and return a Access-Control-Allow-Origin: header?

Edit: JSONP would be the same I guess. Doh.

Right except not all coins exist to make a profit by selling the coins.