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

[forrestv]

I see - very few nodes been updated:
http://poolnode.info/
http://nodes.p2pool.co/
It would be better to change the values in https://github.com/p2pool/p2pool/blob/master/p2pool/networks/bitcoin.py#L15

Code:

IDENTIFIER = 'fc70035c7a81bc6f'.decode('hex')
PREFIX = '2472ef181efcd37b'.decode('hex')

It was only released two hours ago, so it's not surprising that few nodes have updated. Changing those values would prevent a smooth transition. Everything will be fine, if it goes at all similarly to how the last hardfork did.

[1714788563]

1714788563

[1714788563]

1714788563

[1714788563]

1714788563

[jedimstr]

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2.  

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

[forrestv]

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2.  

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

[jedimstr]

Note the new P2Pool Hardfork version 15 currently does not support the BitcoinXT client (neither the 0.11C nor pre-release 0.11D version) and won't fully startup unless you're running BTCore 0.11.2. 

Forest: when BitcoinXT gets the BIP65 pull request merged in, will P2Pool be able to support the resulting BXT version #?

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

Thanks, I'll shoot a message over once Gavin and Mike have a version with BIP65 available.

[wariner]

Is some flunkie DOSing the nodes again?

I'm not aware of any p2pool node ever being dos'd. There seems to be something wrong with your setup though - over 4 seconds is rather high - try limiting your connections to 12-14 instead - that should help.

Sorry, I was thinking bitcoind. I've noticed I have been drawing more stupid-fire ever since I brought up a full node, even more than when I started running a tor relay. Simple enough to deal with, still kind of lame.

I'll try limiting the connections some. The proper solution though is to probably fire up a ubuntu system on an old laptop and run a copy of bitcoind inside network peered to the outside one and others. That should bring it back to sub-second responses while allowing the externally facing one to serve as a full bitcoin node and a p2pool node that can supply blocks to others behind nats.

The problem it's RAM.

Use this for reduce use of RAM:

-limitfreerelay=<n>    Rate-limit free transactions to <n>*1000 bytes per minute (default: 15)
 -minrelaytxfee=<amt>   Fees smaller than this (in satoshi) are considered zero fee (relaying and mining) (default: 0.00001)
 -disablewallet         Do not load the wallet and disable wallet RPC calls 

maybe fix in bitcoin core 0.12....

[Meuh6879]

v15 installed.

[yslyung]

thx forrest,

will be updating my node too.

been away for a bit. is anyone mining with s7 on p2p ? how is it doing ?

[jtoomim]

I'm not sure what version number they'll use, but when they release it (and somebody tells me), I will whitelist it and release P2Pool 15.1.

It will be 0.11D (or 0.11.0D, or something like that, depending on how it gets parsed). It should be released pretty soon.

[AndreyNag]

I see - very few nodes been updated:
http://poolnode.info/
http://nodes.p2pool.co/

Our node have been updated to.
che2pool.mine.nu:9332
Welcome.

[Meuh6879]

[windpath]

Looks like we are at about 25% upgraded, big milestone is 50% when the alert message will be triggered on all nodes to upgrade...

I'll have some time tomorrow to try and reach out to the larger nodes still producing V3 blocks, but if anyone wants to get started today it sure could not hurt

[DonBit]

Runs fine yes, but the bitmain driver throws away what could be potential block solves on p2pool...

the problem is only for s7? or even s5 - s3....?

There is a discussion that contains all modified antminer drivers for p2pool?

.. but it certainly isn't the only one .

Do you think it's just bad luck or other?

The problem is for ALL Antminers unless you have installed the proper binaries from -ck and kano.  If you are using any other binaries (Bitmain's, some other forks for extranonce, etc) then you do not have the updated code that submits stale shares.  In other words, you are potentially throwing away possible block solutions.

As to your other question regarding luck... yes, I believe it is just poor luck.  We are experiencing normal swings in variance.  As I initially mentioned, S7s are certainly a potential influencing factor since there are no (to my knowledge, -ck/kano can correct me) updated cgminer binaries for it.  However, I don't know how many people currently mining on p2pool are using S7s, so I don't have any reference for how much of an impact it might have .

I've configured the stock cgminer in my S7 batch 6 with

Code:

"submit-stale" : true,
"queue" : "1",
"expiry" : "1",
"scan-time" : "1"

and looks like it's now submitting stale shares.

 

[2015-12-09 03:27:21] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:21] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:22]  opt_bitmain_freq:600 tmp:600
 [2015-12-09 03:27:22] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:22] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:23] Pool 1 stale share detected, submitting as user requested

Don't know if it's a bogus submission or if it's really happening but I'm on full speed p2pool

[-ck]

I've configured the stock cgminer in my S7 batch 6 with

Code:

"submit-stale" : true,
"queue" : "1",
"expiry" : "1",
"scan-time" : "1"

and looks like it's now submitting stale shares.

 

[2015-12-09 03:27:21] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:21] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:22]  opt_bitmain_freq:600 tmp:600
 [2015-12-09 03:27:22] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:22] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:23] Pool 1 stale share detected, submitting as user requested

Don't know if it's a bogus submission or if it's really happening but I'm on full speed p2pool

The cgminer default is always to submit stale shares. That entry in your config does nothing on current versions of cgminer. The problem with bitmain's driver is it deletes shares in the driver before even returning them to the main cgminer code in a way you can't configure in cgminer to avoid. These shares don't even show up as being deleted in any logs.

[DonBit]

Thanks for clarifying ck! Btw I've tried to run the cgminer you compiled for the S5 in the S7. it ran but capped the clock speed on 200 

[Meuh6879]

[squidicuz]

I've configured the stock cgminer in my S7 batch 6 with

Code:

"submit-stale" : true,
"queue" : "1",
"expiry" : "1",
"scan-time" : "1"

and looks like it's now submitting stale shares.

 

[2015-12-09 03:27:21] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:21] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:22]  opt_bitmain_freq:600 tmp:600
 [2015-12-09 03:27:22] Pool 1 stale share detected, submitting as user requested
 [2015-12-09 03:27:22] Accepted 00000058 Diff 0/8192 BTM 0 pool 1
 [2015-12-09 03:27:23] Pool 1 stale share detected, submitting as user requested

Don't know if it's a bogus submission or if it's really happening but I'm on full speed p2pool

The cgminer default is always to submit stale shares. That entry in your config does nothing on current versions of cgminer. The problem with bitmain's driver is it deletes shares in the driver before even returning them to the main cgminer code in a way you can't configure in cgminer to avoid. These shares don't even show up as being deleted in any logs.

It would be nice if bitmain gave us the option to have control over that. 
Currently we have to run a modified firmware in order to actually submit stale shares?  Changing the flag in the cgminer config has no effect on submits of stale shares??

[p3yot33at3r]

It would be nice if bitmain gave us the option to have control over that.  
Currently we have to run a modified firmware in order to actually submit stale shares?  Changing the flag in the cgminer config has no effect on submits of stale shares??

Reading back through this thread, this has been a problem with bitmain throughout their entire miner range. Many people have asked them repeatedly to fix their driver/cgminer fork problems, but have been completely ignored (the same can be said for their pool support). What makes it particularly annoying is the fact that they lied, and continue to lie about their support of p2pool in their threads - & even go as far as to say that they help decentralize the network!!

We are in a precarious position. The only mining hardware currently available on the planet does not work properly/efficiently with p2pool - the only truly decentralized pool. I have a few S7's & am thinking about buying a couple more, but it pi**es me off that in order to use them effectively I am forced to point them at a centralized pool instead of my preferred choice - p2pool.

As many miners switch off their older (but p2pool compatible) miners due to inefficiency & electrical costs, I can't help but wonder what the future holds for p2pool unless a manufacturer steps up with something to rival bitmain or a dev steps in who can fix the broken bitmain firmware for use with p2pool. I can't hold my breath long enough for that to happen, & the more I think about it, the more I dislike bitmain - both their broken firmware & their empty block producing crappy SPV pool with zero support......

Spondoolies - rescue us please?   

[squidicuz]

We are in a precarious position. The only mining hardware currently available on the planet does not work properly/efficiently with p2pool - the only truly decentralized pool. I have a few S7's & am thinking about buying a couple more, but it pi**es me off that in order to use them effectively I am forced to point them at a centralized pool instead of my preferred choice - p2pool.

...

Spondoolies - rescue us please?   

I am debating to not purchase more from Bitmain due to these issues with their miners and p2pool.  Every single antminer I have had to modify in order to get expected performance on p2pool, despite Bitmain claiming native support!  This should have been resolved a year ago.

[Songminer]

We are in a precarious position. The only mining hardware currently available on the planet does not work properly/efficiently with p2pool - the only truly decentralized pool. I have a few S7's & am thinking about buying a couple more, but it pi**es me off that in order to use them effectively I am forced to point them at a centralized pool instead of my preferred choice - p2pool.

...

Spondoolies - rescue us please?   

I am debating to not purchase more from Bitmain due to these issues with their miners and p2pool.  Every single antminer I have had to modify in order to get expected performance on p2pool, despite Bitmain claiming native support!  This should have been resolved a year ago.

Just to be clear, you've been able to get your Antminers to work properly by modifying the batch file, as the above posting?

[-ck]

As many miners switch off their older (but p2pool compatible) miners due to inefficiency & electrical costs, I can't help but wonder what the future holds for p2pool unless a manufacturer steps up with something to rival bitmain or a dev steps in who can fix the broken bitmain firmware for use with p2pool. I can't hold my breath long enough for that to happen, & the more I think about it, the more I dislike bitmain - both their broken firmware & their empty block producing crappy SPV pool with zero support......

Spondoolies - rescue us please?  

Spondoolies have left the building. Their next generation is for farms only unless they come up with another product (which might happen).

The Avalon A6s will work well with p2pool but as per the last generation they're pricier than the bitmain product.