Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 60. (Read 2591916 times)
March 30, 2017, 05:50:59 PM
Well it did just get cold.... No worries, I was mining a few years ago and am out of that business other than for fun. It's a Queen's race, but it is nice to help contribute to keeping the network secure.
March 30, 2017, 01:18:40 PM
Yup, the last shares had to fall off the chain. Ah well, better to have my bad luck discharged here than in other aspects of my life.....
dont worry, be happy)
come back and mining
March 30, 2017, 06:18:03 AM
Yup, the last shares had to fall off the chain. Ah well, better to have my bad luck discharged here than in other aspects of my life.....
March 29, 2017, 11:27:01 PM
March 29, 2017, 06:45:06 PM
Don't worry. It finally warmed up here so I shut down my miners. Once my shares age out I'm sure we will hit multiple blocks.
Enjoy!
CongratsEnjoy!
Half of your prophecy was fulfilled.
Only blocks are missing
March 29, 2017, 04:44:02 PM
please, test my node http://212.45.19.162:19332/static/
need extra load, for testing perfomance PC node configuration.
thank you.
need extra load, for testing perfomance PC node configuration.
thank you.
March 29, 2017, 02:07:43 PM
No waves 
No coins
No coins
March 28, 2017, 04:05:34 PM
I added to https://github.com/p2pool/p2pool/issues the solution to the problems that occurred to me:
- Elimination spaces and tabs at the end of the user name https://github.com/p2pool/p2pool/issues/338
- Using pruned blockchain on p2pool nodes https://github.com/p2pool/p2pool/issues/339
March 28, 2017, 03:26:14 PM
March 28, 2017, 02:19:10 PM
What version of p2p are you using?
March 28, 2017, 12:16:59 PM
March 27, 2017, 09:20:31 PM
Don't worry. It finally warmed up here so I shut down my miners. Once my shares age out I'm sure we will hit multiple blocks.
Enjoy!
Enjoy!
March 27, 2017, 07:31:05 PM
20 days and nothing 
I'm getting bankrupted
I'm getting bankrupted
March 26, 2017, 01:10:09 PM
sawa, you shouldn't be using the fork right now. The main branch does everything you could want right now (namely, just indicate SegWit support). A majority of P2Pool hashrate using a fork will indeed confuse other miners.
That's what I wanted to find out. I returned to the official source code.Thank you.
March 26, 2017, 12:31:55 PM
As a separate issue, I now realize that current P2Pool doesn't allow *expressing* support for SegWit, due to line 372 in work.py, which veqtrus's changes don't touch:
If anyone can confirm that fixing that is as simple as changing it to
Code:
version=max(self.current_work.value['version'], 0x20000000),
If anyone can confirm that fixing that is as simple as changing it to
Code:
version=max(self.current_work.value['version'], 0x20000002),
This is wrong. I changed p2pool to signal whatever BIP9 compatible fork a client supports in the CSV commit.
Ah, oops. I misread max as what it used to be (min). Great, so that's not a problem.
How to get out of this situation? Now for my node I use veqtrus patches from the segwit1+empty_block_fix1 branch of a https://github.com/veqtrus/p2pool.git repository.
When my node's hashrate was raised and the amount of v17 shares was increased above then 50%, the message with a link to p2pool.in appeared on another nodes. But there is no announcement about a new version. Owners of other nodes will not do anything.
What to do if the main developers can not agree?
When my node's hashrate was raised and the amount of v17 shares was increased above then 50%, the message with a link to p2pool.in appeared on another nodes. But there is no announcement about a new version. Owners of other nodes will not do anything.
What to do if the main developers can not agree?
sawa, you shouldn't be using the fork right now. The main branch does everything you could want right now (namely, just indicate SegWit support). A majority of P2Pool hashrate using a fork will indeed confuse other miners.
March 26, 2017, 10:50:24 AM
Windpath is correct. There is no rush in activating segwit in p2pool as we are far from activation on the bitcoin network. Plus more independent testing would be desirable...
Thank you. I understood. March 26, 2017, 09:38:13 AM
Windpath is correct. There is no rush in activating segwit in p2pool as we are far from activation on the bitcoin network. Plus more independent testing would be desirable...
March 26, 2017, 06:50:23 AM
...But there is no announcement about a new version...
Because there is no new version, you are running a fork.
The current version at https://github.com/p2pool/p2pool allows BIP9 signaling thanks to veqtrus's work. Please leave the politics elsewhere.
March 26, 2017, 05:27:40 AM
As a separate issue, I now realize that current P2Pool doesn't allow *expressing* support for SegWit, due to line 372 in work.py, which veqtrus's changes don't touch:
If anyone can confirm that fixing that is as simple as changing it to
, then I will publish a new P2Pool release with that change.
Code:
version=max(self.current_work.value['version'], 0x20000000),
If anyone can confirm that fixing that is as simple as changing it to
Code:
version=max(self.current_work.value['version'], 0x20000002),
, then I will publish a new P2Pool release with that change.
This is wrong. I changed p2pool to signal whatever BIP9 compatible fork a client supports in the CSV commit.
How to get out of this situation? Now for my node I use veqtrus patches from the segwit1+empty_block_fix1 branch of a https://github.com/veqtrus/p2pool.git repository.
When my node's hashrate was raised and the amount of v17 shares was increased above then 50%, the message with a link to p2pool.in appeared on another nodes. But there is no announcement about a new version. Owners of other nodes will not do anything.
What to do if the main developers can not agree?
March 26, 2017, 01:59:06 AM
As a separate issue, I now realize that current P2Pool doesn't allow *expressing* support for SegWit, due to line 372 in work.py, which veqtrus's changes don't touch:
If anyone can confirm that fixing that is as simple as changing it to
Code:
version=max(self.current_work.value['version'], 0x20000000),
If anyone can confirm that fixing that is as simple as changing it to
Code:
version=max(self.current_work.value['version'], 0x20000002),
This is wrong. I changed p2pool to signal whatever BIP9 compatible fork a client supports in the CSV commit.
Jump to: