[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[jonnybravo0311]

Ok I am wondering how does one determine what miner or if there pool found the block.

I have not figured that out yet.

2 ways...

First is to look at your logs and you'll see the message that the block was found.

Code:

2014-04-26 04:18:51.302213 GOT BLOCK FROM MINER! Passing to bitcoind!

Second is to look at your payout.  If you found the block you get a 0.125BTC reward for it.

The reward for the block finder is 0.5%? I could've sworn I had read 5%. 0.5% does make more sense, though.

Yup, you can verify it by looking at the code, too.  1/200 is given to address that finds the block, 99/200 is given to everyone else.  From data.py:

Code:

amounts = dict((script, share_data['subsidy']*(199*weight)//(200*total_weight)) for script, weight in weights.iteritems()) # 99.5% goes according to weights prior to this share
this_script = bitcoin_data.pubkey_hash_to_script2(share_data['pubkey_hash'])
amounts[this_script] = amounts.get(this_script, 0) + share_data['subsidy']//200 # 0.5% goes to block finder

[1713862358]

1713862358

[1713862358]

1713862358

[1713862358]

1713862358

[jonnybravo0311]

Just an update folks...

For those of you that had supported CoinCadence's p2pool node by placing an ad or visiting an advertiser, thanks!

While the ads were bringing in a trickle of revenue, they are just not worth it for me to keep running (and I can't stand looking at banner ads either ), soo...

Since bitcoin can bring so much to the table we thought we would try integrating with bitcoin micro-payment services (ChangeTip and CoinBase to start) and see how things go.

If you use the CoinCadence p2pool node, and like what you see consider sending a tip, if there is a feature your dying for send the suggestion with with a bigger tip  ...

Also, today we released a new Bitcoin Transaction Volume section on CoinCadence.com, it is in response to the great feedback we got on Reddit about some data mining I did on the blockchain.

You can see the post here:
TIL: Where the Bitcoins at… Mysteries of the Blockchain

The first iteration on the site only contains transaction volume data, more to come...

Cheers!

Hey windpath,

While I don't often use your node to mine (since I run my own node locally and also on a nearby VPS for when I travel), I do indeed use your services to do things like see payout history, compare my miners' actual hash rate to what p2pool thinks they have, etc.  I know you've done a lot of work and I've personally found great value in the services you've provided.  So, I thought I would be the first one to send you a tip/donation.

Thanks for all the work you've done.

[windpath]

...

Hey windpath,

While I don't often use your node to mine (since I run my own node locally and also on a nearby VPS for when I travel), I do indeed use your services to do things like see payout history, compare my miners' actual hash rate to what p2pool thinks they have, etc.  I know you've done a lot of work and I've personally found great value in the services you've provided.  So, I thought I would be the first one to send you a tip/donation.

Thanks for all the work you've done.

Thanks buddy I appreciate it!

[idonothave]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

[jonnybravo0311]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

[PatMan]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

[idonothave]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

anyway I let only BTC address as workername, it seems it is working well
node uptime 22 hours, hp 4.78THs, 8 shares 2 orphan, peers 5 in 7 out, doa 1.41 (1-3), getblc latency 0.152, I did some changes during the period so efficiency can be not accurate
after some time if see it is ok I will probably add namecoin merged mining
why global DOA is so high?

[idonothave]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

[PatMan]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

[idonothave]

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

That's a known problem with the ants.  If you set the pseudo-share difficulty to something other than a power of 2 the best share will show up properly.

Hi,
I mine for 22 hours with 2,78THs, I got 2 shares, both orphan. I am extremely unlucky or something is wrong. Any recommendation what to check?

Need more info dude - settings etc......

I did some changes by setting static difficulty with workername btcaddress/4000+512 (for S3 units) simmilar done with S4 and S1. Will see. Just now there are 6 shares (2 orphan). I do not merge mine, my getwork latency is 0.166 just now. I am behind NAT, port 9333 is redirected thru onto my p2p server. Broadband ADSL 20mbps dn, 4mbps up. Latest forestv p2pool. DOA 1-4%. In the begin I used only 4 S3, 2 S1 and 2 HEX8A later I added 1 S4. So now 4.78THs.

edit: noticed bestshare=0 with that settings so I removed it from S3 units

Did you also try changing the --queue setting to 0?

yes, I changed with ants to --queue 0 --expiry 1 --scan-time 1 (exclude S4 where I let original setting --queue 8192)

--expiry 1 & --scan-time 1 are obsolete, you don't need them. I recommend using zero queue on all Antminers, including the S4, it will lower your DOA/stale rate.

ok, thank You, I will try it

[icio]

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody 

[windpath]

HI everybody, I'm mining with S2, S3 and S4 in different nodes. Every miner has been upgraded with The last firmware but maintening the original Bitmain's configuration. The address registered is without "+ difficulty value".
The S3 work in a range between 441-453 Gh, S2 993-997 Gh, S4 1980-1990 Gh. Recently I also closed some blocks, receiving 0,5% more. The relationship sharechain/THs is very good, almost always higher than real. For about a month I read about miner change enter "--queque 0" instead of the one programmed by Bitmain. A month that pool statistics are worsening.

Are we sure that the changes proposed here on miner are correct?

Happy mining to everybody  

It has been a rough few weeks variance/luck wise.

The one thing I know about luck is that it is bound to change

I have not messed with my queue settings, but I doubt that doing so would produce this bad luck.

The reported hash rate at the pool would have to be affected and I would imagine a miner tweaking their settings would be paying attention to that.

[jcumins]

I have seen some very strange activity on my node the past 36 hours.

I have 1 s1 and 2 s2 mining on my node.  And the max rate i can get any miner to mine at is .000240 btc  and thats way low what i have seen over the past for a s2.  I would usually average .025 to .03 btc hash rate.

The s1 at that  slower hash rate makes since to me.  But not on the S2.  This is driving me crazy why it is this way.  My equipment is running 2 quad core xeon processors SSD drive and on a 100 meg fiber circuit in my office. The latency for blockchain.info site is 7ms.  So there defiantly not a bandwidth issue.


Any recommendations would surly be appreciated. 

[windpath]

I have seen some very strange activity on my node the past 36 hours.

I have 1 s1 and 2 s2 mining on my node.  And the max rate i can get any miner to mine at is .000240 btc  and thats way low what i have seen over the past for a s2.  I would usually average .025 to .03 btc hash rate.

The s1 at that  slower hash rate makes since to me.  But not on the S2.  This is driving me crazy why it is this way.  My equipment is running 2 quad core xeon processors SSD drive and on a 100 meg fiber circuit in my office. The latency for blockchain.info site is 7ms.  So there defiantly not a bandwidth issue.


Any recommendations would surly be appreciated. 

Could just be bad luck, providing a node address would be helpful to try and diagnose any problems.

Latency to blockchain.info is completely irrelevant, it's the latency to your p2pool peers that matters.

[IYFTech]

Are we sure that the changes proposed here on miner are correct?

There has been a lot of discussion on this here, I provided a graph that showed the advantages of using --queue 0 on a local node - I have not tested the settings on a remote node. If you do a thread search for "--queue", you will see the findings.

Nice to see the blocks are back at last 

[jcumins]

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.

[mdude77]

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.

If you do indeed have a 1 TH/s miner, you will experience variance.  That means sometimes you'll do better than "expected", and other times you won't.  Right it appears you're in the "won't" luck.

M

[jonnybravo0311]

Ok I have a question for all you smart people in p2pool land.

In the last 24 - 36 hours my rate per minor has dropped of 90%  IE a 1 TH minor would do about .025 btc rate and now i am getting about .0025 to .0030 rate from the same miner.  I do have each miner using there own address and not all using the same one address,

What are you other nodes doing and how does my numbers compare to you.

Thanks for all your wisdom from the past and now into the future.

It all depends on how many shares you have on the chain.  As mdude77 pointed out, sometimes you have more than expected, other times you have fewer than expected.  I've seen my own expected payout drop to a single share before, and have seen it do exactly the opposite.  It's variance and it happens to everyone due to the very nature of mining.

[jcumins]

My node ip is as follows:

207.105.189.40:9332

Please lety me know what you think is right and what i can do better

thanks

[jonnybravo0311]

My node ip is as follows:

207.105.189.40:9332

Please lety me know what you think is right and what i can do better

thanks

Well, the first problem is that the node is not accessible.  I can't even ping your IP address, or run a trace route to it.  You sure your node is running?