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

[kano]

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

Power cycle will lose the change.

... and yes I've posted about the issue long ago :p

[1714196361]

1714196361

[1714196361]

1714196361

[1714196361]

1714196361

[1714196361]

1714196361

[1714196361]

1714196361

[1714196361]

1714196361

[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

Power cycle will lose the change.

... and yes I've posted about the issue long ago :p

Well that's a huge PITA, sounds like jtoomim's solution to update your LAN DNS to point auth.minerlink.com to localhost is the way to go!

[in2tactics]

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

http://www.antbleed.com/

Thanks for sharing this, windpath. We need to spread more awareness on this issue to protect as many miners as possible using those Antminers.

Also, to anyone who would like to chip in with their opinions about Antbleed here, please keep it civil and as apolitical as possible. The main point here is to be aware that there is a backdoor, that this backdoor could be exploited in ways we do not know yet, and that we need to take as many precautions as possible to mitigate this risk. We do not need more name-calling and mudslinging.

You do know that this horribly named vulnerability has been known about for awhile, right? We do not need a lecture on civility by someone with a 4 day old account.

[in2tactics]

...

We do not need a lecture on civility by someone with a 4 day old account.

Not everyone joined the bitcointalk forum the very moment they joined the Bitcoin ecosystem.

Yes, I can certainly understand that as it describes my own situation rather well. However, your post is completely OT and you are pretty much violating your own request for civility. I would like to point out that just because the folks you quoted did not know of the vulnerability does not mean that other parts of the community were not tracking it. I know that I read about it at least some months ago now.

[windpath]

I find this interesting (from the node scanner):

Currently 125 P2Pool nodes online, 120 of them are open to the public. I've seen 206 P2Pool nodes since I began scanning in April 2017.

First to have 120 of 125 active nodes open to the public is simply amazing.

In November 2016: 103 nodes discovered (p2pool version 16+) 58 public nodes (blue), 45 private nodes (yellow)

Thats a huge boost in the percentage of public nodes.

The second thing I find interesting is that since April 21st (just 6 days) 81 nodes have been started and then subsequently gone offline, wonder what those folks are up to...

[jl2012]

Miner upgrade checklist: https://litecoincore.org/ltc-segwit-pool.pdf

Let me know if you need help

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/

[sawa]

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/

+ http://crypto.office-on-the.net:9327

[Meuh6879]

The second thing I find interesting is that since April 21st (just 6 days) 81 nodes have been started and then subsequently gone offline, wonder what those folks are up to...

Honestly, i have rented a S7 and a S9 (in russia) to see my P2Pool node on this scanner ... but only for 1 week. 

[windpath]

Whoops....

Bug in my code. I was counting all reachable nodes (ever, not just the active ones), so my number of public nodes was way off....

It's accurate now.

Currently 121 P2Pool nodes online, 79 of them are open to the public. I've seen 215 P2Pool nodes since I began scanning in April 2017.

[in2tactics]

Whoops....

Bug in my code. I was counting all reachable nodes (ever, not just the active ones), so my number of public nodes was way off....

It's accurate now.

Currently 121 P2Pool nodes online, 79 of them are open to the public. I've seen 215 P2Pool nodes since I began scanning in April 2017.

I still think it is pretty awesome that 65% of current nodes are open to the public.

[Meuh6879]

Question about P2Pool (on Bitcoin network) : how many time must wait for the P2Pool node to adjust the difficulty ?

I have rented a 4,7 TH/s and, when it has finished, my regular 10 GH/s follow the path.
But, the difficulty stuck at 1200 (instead of 2).

When i restart the P2Pool node, the difficulty is reset to 1 and the P2Pool rise to 2 for the 10 GH/s like usual.





Edit : OK, 40 minutes to adjust automaticly the P2Pool difficulty (readed on the P2Pool log) from 1200 to 2.  

[windpath]

Question about P2Pool (on Bitcoin network) : how many time must wait for the P2Pool node to adjust the difficulty ?

I have rented a 4,7 TH/s and, when it has finished, my regular 10 GH/s follow the path.
But, the difficulty stuck at 1200 (instead of 2).
I have waited 1h and no change on difficulty ...

When i restart the P2Pool node, the difficulty is reset to 1 and the P2Pool rise to 2 for the 10 GH/s like usual.

The P2Pool difficulty itself is dynamic and adjusts with each share found.

There are 2 other difficulty settings configurable by the miner:

Share difficulty: sets the actual difficulty for a miners shares. This was implemented for large miners who wanted to set share difficulty HIGHER than P2Pools actual difficulty. If set to lower than share difficulty it is ignored. It is set by adding a "/" to the end of your address followed by the difficulty number.

Sudo share difficulty: sets a sudo difficulty so your miners will submit work more often than they would at the actual difficulty. This is useful to smooth out your hash rate graph on the node. It is set by adding a "+" at the end of the miner address followed by the desired sudo difficulty.

You can set both or either one.

Regardless of your settings shares will only be accepted if they meet the minimum P2Pool difficulty.

Edit: as pointed out below I mixed up the + and /, this post is edited to be correct.

[Meuh6879]

  Roger, 5/5 !

[frodocooper]

...

There are 2 other difficulty settings configurable by the miner:

Share difficulty: sets the actual difficulty for a miners shares. This was implemented for large miners who wanted to set share difficulty HIGHER than P2Pools actual difficulty. If set to lower than share difficulty it is ignored. It is set by adding a "+" to the end of your address followed by the difficulty number.

Sudo share difficulty: sets a sudo difficulty so your miners will submit work more often than they would at the actual difficulty. This is useful to smooth out your hash rate graph on the node. It is set by adding a "/" at the end of the miner address followed by the desired sudo difficulty.

You can set both or either one.

Regardless of your settings shares will only be accepted if they meet the minimum P2Pool difficulty.

Hmm, I was under the impression that it was the other way around, i.e.:
- adding a "/" followed by the desired difficulty level to the end of the Bitcoin address would tell the miner to submit only shares above the stated "/" difficulty level, and
- adding a "+" to the end of the Bitcoin address tells the P2Pool node to always give the miner work with the stated "+" difficulty level.

[in2tactics]

Personally speaking, I have always found the "+" option to be the most useful as it forces p2pool to give a miner the specified work difficulty.

[windpath]

Your both absolutely right! Will edit now so it's correct, was on my cell phone and could not search the source so went from memory (or lack there of...)

[whortonda]

Greetings p2poolers,

I'm the owner of the "1Hinen" address. I began renting hashpower to mine on p2pool about a month ago and noticed the smaller block sizes, and came across the discussion here after some Googling on the subject.

@jtoomim, I have switched my node to your fork. I just finished downloading the sharechain and it looks like everything is working well. You can expect anywhere from 0-10Ph of rented hashpower from me depending on rental prices.

Please let me know if I can do anything else to help you test your fork (or if I'm doing anything that's not helpful). Thank you for your work on this. Looking forward to finding a fat 1MB block with you.

--Darren

----------------------------------------------------------------------------------

Node: whortonda.noip.me
Worker port: 3000
P2P port: 9333
Connected to: ml.toom.im:9333
To connect to me: run_p2pool.py -n whortonda.noip.me:9333
CPU: Core i7-6800K @ 3.4GHz
RAM: 32GB
Pipe: 100m/20m cable
Using: Python 2.7 / Ubuntu 16.04 LTS

I am using a non-standard miner port to avoid conflict with litecoind.
Anyone is welcome to mine to my node, but I can't guarantee 100% stability.

[leri4]

Node IP: whortonda.noip.me (default ports)
Connected to: ml.toom.im:9333
To connect to me: run_p2pool.py -n whortonda.noip.me:9333
CPU: Core i7-6800K @ 3.4GHz
RAM: 32GB
Pipe: 100m/20m cable
Using: Python 2.7 / Ubuntu

Node IP: 109.87.83.144 (default ports)
Connected to: 208.84.223.121:9335
To connect to me: run_p2pool.py -n 109.87.83.144:9333
CPU: i5 4690 3.5 GHz
RAM: 16GB
Pipe: 100m/100m cable
Using: Python 2.7 /PyPy 5.1.2/ Ubuntu

After syncing sharechain:

Code:

 raise jsonrpc.Error_for_code(-12345)(u'p2pool is not connected to any peers')

Code:

2017-05-02 09:14:23.415915 P2Pool: 16885 shares in chain (8245 verified/16886 total) Peers: 3 (0 incoming)
2017-05-02 09:14:23.416102  Local: 10064GH/s in last 4.1 minutes Local dead on arrival: ~27.8% (12-51%) Expected time to share: 20.2 minutes
2017-05-02 09:14:23.416245  Shares: 1 (0 orphan, 1 dead) Stale rate: ~100.0% (20-100%) Efficiency: ~0.0% (0-81%) Current payout: (0.0000)=0.0000 BTC
2017-05-02 09:14:23.416403  Pool: 9005TH/s Stale rate: 0.8% Expected time to block: 2.9 days
2017-05-02 09:14:23.419608 Peer sent entire transaction b703f925cfeccb47fa4cd4957ebb8d8efb7fcac6d2a59ca58b69741dd7635b0d that was already received
2017-05-02 09:14:23.425375 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.425646 Transaction 3062050f02b1ec30d1a0f14e4fe539ae40917ed8f84f995184dda9e098c3d03d rescued from peer latency cache!
2017-05-02 09:14:23.427743 Peer sent entire transaction fcafe2636e858ae28bffd87102a54544ad4f2195fda2f75f95f0565a0d622ae5 that was already received
2017-05-02 09:14:23.436750 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.437028 Peer sent entire transaction a2bdb9f1f914e7ce2cc4c354f1ebb804832a269e9b4170d214b3dd9557a62a67 that was already received
2017-05-02 09:14:23.442954 Peer sent entire transaction 080667f400e06ddc8b24c1be9cc18c50e9ed07ff97f08a0edbe18aae809a30c8 that was already received
2017-05-02 09:14:23.450137 Transaction 76dcccb813174919e6b38d1c9449abd4f28777effae44147b0a98dcd6775d0f3 rescued from peer latency cache!
2017-05-02 09:14:23.450335 Peer sent entire transaction ac171faed3f3d58b10ee64c87db758c393b65c877f783ac9eb6973fd6d446eea that was already received
2017-05-02 09:14:24.211989 Processing 32 shares from 74.66.86.127:9333...
2017-05-02 09:14:24.592938 ... done processing 32 shares. New: 32 Have: 16918/~17280
2017-05-02 09:14:24.593267 Requesting parent share 3c2dc9ea from 208.84.223.121:9335
2017-05-02 09:14:24.600174 GOT SHARE! 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT 5ae39c4e prev e9a5a8b5 age 50.06s
2017-05-02 09:14:24.612468 Warning: Previous share's timestamp is 3603 seconds old.
2017-05-02 09:14:24.612675 Make sure your system clock is accurate, and ensure that you're connected to decent peers.
2017-05-02 09:14:24.612826 If your clock is more than 300 seconds behind, it can result in orphaned shares.
2017-05-02 09:14:24.612970 (It's also possible that this share is just taking a long time to mine.)
2017-05-02 09:14:24.629463 Generating a share with 96944 bytes (3005 new) and 104 transactions (9 new)
2017-05-02 09:14:24.631907 New work for 18gMRtpHR9iCQBHtJWyCktTYqrrTQ48RMT! Diff: 32000.00 Share diff: 1744307.93 Block value: 12.81 BTC (104 tx, 97 kB)
2017-05-02 09:14:24.784342 Lost peer 74.66.86.127:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.848019 Lost peer 208.84.223.121:9333 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:24.912460 Lost peer 208.84.223.121:9335 - Connection to the other side was lost in a non-clean fashion.
2017-05-02 09:14:53.425500 P2Pool: 16918 shares in chain (8278 verified/16919 total) Peers: 0 (0 incoming)

[windpath]

When advertising nodes I think it's very important to differentiate between what share chain you are running on very clearly.

The two I am currently aware of are

- MainNet
- Jtoomim fork

The two share chains are not compatible with each other, so if you explicitly set a -n to an incompatible node you will not submit valid work...

If both share chains survive for a while I will update p2pool.org to track stats for both, currently it's only for MainNet (the long standing main implemtation by Forrest).

[whortonda]

jtoomim fork found a block: https://blockchain.info/block/00000000000000000218556606adced3948eccd7703411117304211f7ed83fe3
998kB / 13.93885715 BTC

Yay!