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

[tubexc]

 What a tide of bad Luck 

[1714112062]

1714112062

[1714112062]

1714112062

[1714112062]

1714112062

[japz-x]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

[sawa]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

This is my node. Can you tell which address are you mining on?
I'll take a look at your charts.

You were answered right:

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain.

Here is a graph of the global p2pool hashrate increasing for a month:

It can be seen that the global hashrate has significantly increased. This confirms what frodocooper said

[japz-x]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

You might want to check whether your S9 is working properly. 12.5TH/s should average out to around 0.015BTC per P2Pool block at the current difficulty.

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain. More info at http://www.p2pool.org/learn/. This should still nevertheless average out to roughly the same amount of payouts over an extended period of time (e.g. per month), as the payout per block may decrease, but average frequency of finding blocks should increase with the rise in total P2Pool hashrate. A handy stats page to keep an eye on is http://www.p2pool.org/stats/.

Thank you for your attention and response. I will check with certainty.

[japz-x]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

This is my node. Can you tell which address are you mining on?
I'll take a look at your charts.

You were answered right:

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain.

Here is a graph of the global p2pool hashrate increasing for a month:
http://www.imageup.ru/img208/2749006/globalstat2.jpg
It can be seen that the global hashrate has significantly increased. This confirms what frodocooper said

Hi friend, how are you?
Take a look, please.
I am logged into this node as a primary crypto.office-on-the.net:9332
E this as secondary 82.200.205.30:9332
The address I use is this one 1FTjZNDMV3TxdUM776cnZLTtyxeJzicZFu

[japz-x]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

You might want to check whether your S9 is working properly. 12.5TH/s should average out to around 0.015BTC per P2Pool block at the current difficulty.

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain. More info at http://www.p2pool.org/learn/. This should still nevertheless average out to roughly the same amount of payouts over an extended period of time (e.g. per month), as the payout per block may decrease, but average frequency of finding blocks should increase with the rise in total P2Pool hashrate. A handy stats page to keep an eye on is http://www.p2pool.org/stats/.

My speed on the node shows 11.7 ~ 13.5. However
Here http://www.p2pool.org/stats/ shows 5598.03 GH / s
There is something wrong, this is fact.

[sawa]

Hi friend, how are you?
Take a look, please.

I'm fine.
Here's your graph for a month: http://crypto.office-on-the.net:9332/static/classic/graphs.html?Month

You mined unstable, and the average hashate on the node is 8.17TH/s
In addition a large percentage is DOA = 1.24TH / s
You need to select a near-by node from the list http://www.p2pool.org/stats/node_scanner.php
This will reduce the percentage of DOA and increase the efficiency of mining.

I am logged into this node as a primary crypto.office-on-the.net:9332
E this as secondary 82.200.205.30:9332
The address I use is this one 1FTjZNDMV3TxdUM776cnZLTtyxeJzicZFu

It's the same node. You need to specify different nodes:  primary and secondary

[japz-x]

Hi friend, how are you?
Take a look, please.

I'm fine.
Here's your graph for a month: http://crypto.office-on-the.net:9332/static/classic/graphs.html?Month
http://www.imageup.ru/img208/2749478/1ftjzndmv3txdum776cnzlttyxejziczfu.png
You mined unstable, and the average hashate on the node is 8.17TH/s
In addition a large percentage is DOA = 1.24TH / s
You need to select a near-by node from the list http://www.p2pool.org/stats/node_scanner.php
This will reduce the percentage of DOA and increase the efficiency of mining.

I am logged into this node as a primary crypto.office-on-the.net:9332
E this as secondary 82.200.205.30:9332
The address I use is this one 1FTjZNDMV3TxdUM776cnZLTtyxeJzicZFu

It's the same node. You need to specify different nodes:  primary and secondary

Very grateful friend to clarify. I'm still doing some testing. I'll be right back to your node.

[windpath]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

You might want to check whether your S9 is working properly. 12.5TH/s should average out to around 0.015BTC per P2Pool block at the current difficulty.

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain. More info at http://www.p2pool.org/learn/. This should still nevertheless average out to roughly the same amount of payouts over an extended period of time (e.g. per month), as the payout per block may decrease, but average frequency of finding blocks should increase with the rise in total P2Pool hashrate. A handy stats page to keep an eye on is http://www.p2pool.org/stats/.

My speed on the node shows 11.7 ~ 13.5. However
Here http://www.p2pool.org/stats/ shows 5598.03 GH / s
There is something wrong, this is fact.

Use the node speed, P2Pool.org only estimates based on how many shares you have currently.

[japz-x]

Dear mining friends, excuse me a bit of ignorance in mining in p2pool. Actually I started 1 month ago, and I have some doubts.
I am mining on 82.200.205.30:9332 and the first time I called it gave 0.034
This number has been decreasing as the month ends. It is currently mining at 0.0002. Does this number go up again? There is something wrong? My hardware is a S9 12.5

You might want to check whether your S9 is working properly. 12.5TH/s should average out to around 0.015BTC per P2Pool block at the current difficulty.

Also, note that as P2Pool's total hashrate increases, your expected payout per P2Pool block would decrease due to the increasing difficulty of the P2Pool sharechain. More info at http://www.p2pool.org/learn/. This should still nevertheless average out to roughly the same amount of payouts over an extended period of time (e.g. per month), as the payout per block may decrease, but average frequency of finding blocks should increase with the rise in total P2Pool hashrate. A handy stats page to keep an eye on is http://www.p2pool.org/stats/.

My speed on the node shows 11.7 ~ 13.5. However
Here http://www.p2pool.org/stats/ shows 5598.03 GH / s
There is something wrong, this is fact.

Use the node speed, P2Pool.org only estimates based on how many shares you have currently.

Yes, I'll take the test. ;-)

[notabeliever]

8 hrs ago Block!!! https://blockchain.info/block-height/463189

[jtoomim]

My forked sharechain has switched to v32 shares. When I did this, I forgot to upgrade one of my nodes, which resulted in that node downloading shares from my upgraded nodes, rejecting them due to an unknown share version, and then downloading them. Eventually, it disconnects from the peers due to the perceived misbehavior, but since I had the connections hardcoded with an -n command line option, it reconnected again immediately. It seems p2pool could use a temporary ban feature for misbehaving peers as well as a blacklist for share hashes that are known to be invalid according to the node's ruleset. That should be done before p2pool gets too big in order to prevent DoS attacks.

I just bumped the protocol version up to 3200 and now require peers to have that protocol version. I think we're now ready to start testing with other people's nodes. I'd like to set up a chain of nodes connected via the internet at large (each with one incoming, one outgoing peer) so that I can get an idea how long full shares will take to propagate over many hops. Any volunteers? A chain of 5 or so nodes would be sufficient. See the bottom for instructions.

After this test has been finished, I can add some new DNS seed peers to the code to make it easier for people to join the fork. (Currently, you have to use the -n command line option to manually specify someone to connect to whom you know to be using my code.)

By the way, some rough performance numbers I've observed on my LAN using pypy and fast CPUs: it appears to take around 200 ms per hop to transmit and parse a 1MB share, even when the share is being sent to localhost (i.e. infinite bandwidth). It then takes about 80-120 ms per worker (i.e. per mining address, not per mining rig) to generate and assign new work. After new work has been assigned, it seems to take Antminer S9s around 300 ms before they stop working on the old work and switch to new work (or maybe that's just additional latency on the node side from serialized processing of network input causing delays in the processing of returned work). All told, this seems to add around 600 ms of latency. Over the last week of operation, the forked pool is showing total orphan and DOA rates of 0.59% and 1.2%, respectively, or about 1.8% total, which is pretty much equal to what we'd expect based on the observed latency (0.6 s / 30 s = 2%). This indicates that the changes I made to address the "Block-stale share punished!" and "Tried to broadcast a share without all of its transactions" issues appear to be resolved in this code. The old fork probably would get a DOA+orphan rate above 10%, and certainly no less than 5%, even on a LAN. Most of that high orphan rate was purely random and shouldn't adversely affect revenue, but it could still create unnecessary orphan races which benefit larger miners like me.

It will be interesting to see how high DOA+orphan rates end up being once this fork has more mining nodes. I'm guessing we'll probably be a little under 10%, but maybe 5% is possible. We'll see.

Due to the share chain holding about 2x as many transactions per share, the memory consumption is about 2x higher. Expect about 1.5 GB with CPython and close to 4 GB with pypy. I'm sure this can be improved if it's a major problem for people, but it's not the top of my priority list. (Do we even need all the transactions for old shares? Wouldn't the merkle root + coinbase be enough for shares that are too old to have reused transactions?)


If you want to contribute to the networked chain for share propagation testing, please clone https://github.com/jtoomim/p2pool/commits/1mb_hardforked, then configure your node to point to the previous poster's node (e.g. python run_p2pool.py -n previous_node), then list your node IP, what it's connected to, what type and speed of CPU you're using, how fat your pipe is, and whether you're using pypy or CPython (the regular python). Example, and to start us off:

Node IP: ml.toom.im (default ports)
Connected to: ml.toom.im:9334 and :9336 (or :9335 and :9337 for p2p ports)
To connect to me: run_p2pool.py -n ml.toom.im:9333
CPU: Core i7 4790k 4.0 GHz
Pipe: 100m/100m fiber
Using: pypy 2.4.0

[jl2012]

Segwit dev here.

Who is maintaining the p2pool for litecoin? As segwit will activate in 2 weeks, p2pool upgrade is needed

[notabeliever]

Node IP: ml.toom.im (default ports)
Connected to: ml.toom.im:9334 and :9336 (or :9335 and :9337 for p2p ports)
CPU: Core i7 4790k 4.0 GHz
Pipe: 100m/100m fiber
Using: pypy 2.4.0

My avalon A721 seems to like it much better. Finds shares and is at a comfortable difficulty. Really nice that you did this for us Thank you

[veqtrus]

Segwit dev here.

Who is maintaining the p2pool for litecoin? As segwit will activate in 2 weeks, p2pool upgrade is needed

I'm working on the segwit PR which already supports litecoin.

[windpath]

Segwit dev here.

Who is maintaining the p2pool for litecoin? As segwit will activate in 2 weeks, p2pool upgrade is needed

I'm working on the segwit PR which already supports litecoin.

Would be awesome to get some testing for Veqtrus's PR on LiteCoin, I googled a little and found a couple LiteCoin node scanners that show no LiteCoin nodes, best I can tell there are around 10 active LiteCoin P2Pool nodes, if anyone wants to try to reach out to them heres a few I tracked down:

http://altmine.co:9327/static/
http://xpool.net:9327/static/
http://ltc.nordicp2pool.org:9327/static/
http://litecoin.treasurequarry.com:9327/static/
http://147.156.85.168:9327/static/
http://185.5.55.199:9327/static/
http://176.56.236.116:9327/static/

[veqtrus]

Would be awesome to get some testing for Veqtrus's PR on LiteCoin

It can already be tested on Vertcoin.

[windpath]

Antbleed - Potentially malicious backdoor on Antminer S9, T9, R4, L3 and any upgraded firmware since July 2016

http://www.antbleed.com/

[windpath]

The fix is easy, simply add the following to your /etc/hosts on any miner with > July 2016 firmware.

Code:

127.0.0.1 auth.minerlink.com

[jtoomim]

Or on your LAN's DNS server.