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

[LevinSwe]

I found my first block!BTC It was my laundry miner who found it, a BitmainS9 as I only had a week. My girlfriend hates it, but it dries the laundry really fast.
http://scadainfo.com/pic/0699.jpg

[1714051686]

1714051686

[1714051686]

1714051686

[1714051686]

1714051686

[windpath]

I found my first block!BTC It was my laundry miner who found it, a BitmainS9 as I only had a week. My girlfriend hates it, but it dries the laundry really fast.

Congrats!

[flameruk]

Hi folks. Is there any issue running classic as the backend for P2Pool or does it need to be core?
Just I am upgrading a rack server this week at work during the holiday and the old box will be reprovisioned as a uk node.
Something I've wanted to do for a while to lower my latency and we have a direct Ethernet comnection at work so probably makes sense.

[windpath]

Hi folks. Is there any issue running classic as the backend for P2Pool or does it need to be core?
Just I am upgrading a rack server this week at work during the holiday and the old box will be reprovisioned as a uk node.
Something I've wanted to do for a while to lower my latency and we have a direct Ethernet comnection at work so probably makes sense.

You need to change the block version in the P2Pool source code, it's line 372 in work.py, to:

Code:

Code:

version=min(self.current_work.value['version'], 0x30000000),

or

Code:

Code:

version=min(self.current_work.value['version'], 805306368),

Both work.

[veqtrus]

... classic as the backend for P2Pool ...

You need to change the block version in the P2Pool source code, it's line 372 in work.py, to:

...

This is no longer needed.

[windpath]

... classic as the backend for P2Pool ...

You need to change the block version in the P2Pool source code, it's line 372 in work.py, to:

...

This is no longer needed.

Thanks for the heads up, but can you clarify what the new version from you commit signals for?

Code:

version=max(self.current_work.value['version'], 0x20000000),

[veqtrus]

Thanks for the heads up, but can you clarify what the new version from you commit signals for?

Code:

version=max(self.current_work.value['version'], 0x20000000),

0x20000000 is BIP9 with no deployment bits set. If some are set the version will be larger; therefore the version should always be at least 0x20000000 (what my code does).

Edit: This means that whatever BIP9 compatible version bitcoind is suggesting will be used as is.

[windpath]

Thanks for the heads up, but can you clarify what the new version from you commit signals for?

Code:

version=max(self.current_work.value['version'], 0x20000000),

0x20000000 is BIP9 with no deployment bits set. If some are set the version will be larger; therefore the version should always be at least 0x20000000 (what my code does).

Edit: This means that whatever BIP9 compatible version bitcoind is suggesting will be used as is.

Thanks for taking the time to clarify, and appreciate your contribution. So basically P2Pool will signal for whatever flavor of Bitcoin client you are running signals for...

[KorbinDallas]

Whoa! 10 PH/s 

[flameruk]

Hi folks. Is there any issue running classic as the backend for P2Pool or does it need to be core?
Just I am upgrading a rack server this week at work during the holiday and the old box will be reprovisioned as a uk node.
Something I've wanted to do for a while to lower my latency and we have a direct Ethernet comnection at work so probably makes sense.

Thanks for the info.

I will go with classic as in my mind it's a better solution to Segwit and cores principles.
Please don't thrash me over this one. I'm still reading about Segwit but it seems to begin to steer ownership towards core of the network.

The new hardware never arrived this week so I'll have to wait a couple more days into the new year.
I hashed up Ubuntu on an old office PC and started to get things working but nah the processors having none of it.
Until then I'll keep mining to another node.

[in2tactics]

Hi folks. Is there any issue running classic as the backend for P2Pool or does it need to be core?
Just I am upgrading a rack server this week at work during the holiday and the old box will be reprovisioned as a uk node.
Something I've wanted to do for a while to lower my latency and we have a direct Ethernet comnection at work so probably makes sense.

Thanks for the info.

I will go with classic as in my mind it's a better solution to Segwit and cores principles.
Please don't thrash me over this one. I'm still reading about Segwit but it seems to begin to steer ownership towards core of the network.

The new hardware never arrived this week so I'll have to wait a couple more days into the new year.
I hashed up Ubuntu on an old office PC and started to get things working but nah the processors having none of it.
Until then I'll keep mining to another node.

I do not think anyone cares which software you use. It is more important that you properly configure your node for quick block submission and for optimal transaction payout versus worrying over SegWit support yes or no.

[veqtrus]

I will go with classic as in my mind it's a better solution to Segwit and cores principles.

I'm not going to argue about whether or not SegWit is good but once it is certain that it will activate P2Pool will have to fork to produce SegWit blocks and if your node doesn't support it by then you will be forked off the P2Pool network.

[tubexc]

Renting hashrate and listening :
Jennifer Lopez - Jenny from the Block - YouTube
https://www.youtube.com/watch?v=dly6p4Fu5TE   

[in2tactics]

Renting hashrate and listening :
Jennifer Lopez - Jenny from the Block - YouTube
https://www.youtube.com/watch?v=dly6p4Fu5TE   

I thought that for sure we were going to find a block during that huge spike.

[flameruk]

I will go with classic as in my mind it's a better solution to Segwit and cores principles.

I'm not going to argue about whether or not SegWit is good but once it is certain that it will activate P2Pool will have to fork to produce SegWit blocks and if your node doesn't support it by then you will be forked off the P2Pool network.

Yep I'm aware of that. Figure p2Pool might even activate before the rest of the network as well.
Guess that's something I'm going to have to go with to stick with P2Pool.

I got a test node running at

http://81.131.94.77:9332/static/

It's not been tweaked for efficiency as it's running on my Centos box at home.
Slow processor, lack of memory slow hard drives.
At least I can get it up and running, I've got a half broken S7 mining to it now.
Gives me a few days to play around with it until the new rack server arrives on Tuesday.
Once that's in I'll use a spare IP at the office and it can sit on our leased line and on the same subnet as my Miners.
Then I can get down to some serious tweaking.

Cool, enjoying the ride.

[tubexc]

Block found.!!!
Fireworks
Happy 2017 

[in2tactics]

Block found.!!!
Fireworks
Happy 2017  

Yup, it is nice to bring in the new year with a block.

[mahrens917]

The node scanner at p2pool.co is back up and working at http://p2pool.co. It was down for a little while.  Please try it out.  Feedback is always welcome.

[sawa]

The node scanner at p2pool.co is back up and working at http://p2pool.co. It was down for a little while.  Please try it out.  Feedback is always welcome.

On this node scanner always limited node list. You must manually add them?
Why not add all nodes with http://poolnode.info/?

[in2tactics]

The node scanner at p2pool.co is back up and working at http://p2pool.co. It was down for a little while.  Please try it out.  Feedback is always welcome.

On this node scanner always limited node list. You must manually add them?
Why not add all nodes with http://poolnode.info/?

I always see way more nodes with poolnode.info while I usually only see a few on p2pool.co, but I am not really sure why.