Will p2pool support 8mb block size? (re: bitcoincash) when its forked on Aug 1st?
Is segwit and merge mining alt-coins working on any of the forks? (jtoomin or other?)
Trying to be prepared for the fun in less than a week. Thanks in advance for any help and advice.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 36. (Read 2591916 times)
July 26, 2017, 11:03:28 AM
July 26, 2017, 10:57:31 AM
Leaving the ship. 
http://imgur.com/a/PeCMj
Ridiculous hashrate
http://imgur.com/a/PeCMj
Ridiculous hashrate
To which pool are you headed, wise sir?
July 25, 2017, 08:28:33 PM
How can I run p2pool in background? (linux version)
Have user interface?
screen Have user interface?
July 25, 2017, 08:14:38 PM
How can I run p2pool in background? (linux version)
Have user interface?
Have user interface?
July 25, 2017, 07:03:48 PM
Just a pass ... 
July 25, 2017, 05:07:24 PM
July 23, 2017, 05:23:01 PM
Anyone knows about pruning does it affect node, can I run pruned node with p2pool and mining on it? Thanks.
You can run with a pruned blockchain https://github.com/p2pool/p2pool/issues/339Do not pruned the blockchain less than 2 gigabytes.
Thanks! I am already downloading blockchain, will see how it goes:)
July 23, 2017, 04:20:00 PM
Anyone knows about pruning does it affect node, can I run pruned node with p2pool and mining on it? Thanks.
You can run with a pruned blockchain https://github.com/p2pool/p2pool/issues/339Do not pruned the blockchain less than 2 gigabytes.
July 23, 2017, 03:57:17 PM
Hello,
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
look it up
https://bitcointalksearch.org/topic/running-bitcoin-core-on-external-hard-drive-1763613
Thanks, I know about -datadir option already, I am always using it manually when running mode. And running node from external HDD is not an option.
Anyone knows about pruning does it affect node, can I run pruned node with p2pool and mining on it? Thanks.
July 23, 2017, 02:33:33 PM
Hello,
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
look it up
https://bitcointalksearch.org/topic/running-bitcoin-core-on-external-hard-drive-1763613
July 23, 2017, 02:06:26 PM
Hello,
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
I got a question regarding Bitcoin Core client. I would like to run full node, but I don't have disk space to hold whole blockchain. Right now my Bitcoin Core client is synchronizing, I enabled prune to 5120 MB. Will I be able to be full p2pool node with pruned client? Will I have incoming connections from other clients (I've opened port)? Will my node serve other nodes by providing them data of last 5GB of blocks data?
Thanks.
July 22, 2017, 07:09:35 AM
BIP9 signaling (more than 95%) : http://bitcoin.sipa.be/versions.html
https://www.xbt.eu/ (144 Blocks)
https://www.xbt.eu/ (144 Blocks)
July 22, 2017, 05:26:18 AM
why p2pool Miner dont set the segwit2x bit ?
July 22, 2017, 04:10:10 AM
When you next find a block, if it's rejected because p2pool 'will' mine on invalid blocks, you know it's because no one fixed it.
Damn shame.
Damn shame.
Now that I think about it more, there are actually 3 percentages that matter.
1) Total miners who are signalling segwit (that is around 99.3%)
2) P2pool miners who are not signaling segwit
3) P2pool miners who are using non-BIP-91 compatible code
The cost of 3) depends on the 1). If almost all blocks signal segwit then the fact that sometimes p2pool miners build on the wrong block doesn't have much effect.
2) is a direct cost. If 80% of p2pool miners are flagging segwit, then 20% of the blocks that p2pool finds will be invalid. In that case, mining on p2pool is like mining on a pool that has 20% fees (except that nobody actually gets the fees).
A rule that that marks shares that don't flag segwit as invalid would be justified.
July 21, 2017, 06:37:27 PM
The thing is there is virtually no one left mining non-BIP91
Xbt is showing SW + BIP91 = 99.3% so agreed the point is moot anyway.
When you next find a block, if it's rejected because p2pool 'will' mine on invalid blocks, you know it's because no one fixed it.
Damn shame.
July 21, 2017, 05:31:08 PM
The thing is there is virtually no one left mining non-BIP91
Xbt is showing SW + BIP91 = 99.3% so agreed the point is moot anyway.
July 21, 2017, 05:17:45 PM
If p2pool runs BIP141 segwit compatible that will likely be enough to avoid building on a dead end chain because it looks like there won't be any dead end chain...
Ironically, the problem is that bitcoin-core doesn't reject blocks that don't flag segwit. That means that p2pool miners who are using core will build on the wrong block whenever a non-segwit block is found.
If p2pool built empty blocks when bitcoind is building on a non-segwit block, then almost all the inefficiency goes away.
July 21, 2017, 06:36:19 AM
If p2pool runs BIP141 segwit compatible that will likely be enough to avoid building on a dead end chain because it looks like there won't be any dead end chain...
Ironically, the problem is that bitcoin-core doesn't reject blocks that don't flag segwit. That means that p2pool miners who are using core will build on the wrong block whenever a non-segwit block is found.
If p2pool built empty blocks when bitcoind is building on a non-segwit block, then almost all the inefficiency goes away.
July 20, 2017, 06:36:52 PM
Since we are forking anyway would it not be cleaner for p2pool to do a simple version check on blocks it receives from other p2pool nodes, or would further validation be required?
It's not a simple version check for p2pool, unfortunately, because the duration of the version check is very specific, and it requires a copy of the blockchain (which p2pool does not have) in order to know what that duration is.-ck, the question is whether p2pool should allow BIP91-incompatible shares, not blocks. I'm fine with people mining BIP91-incompatible blocks if they want to, but it's not clear that they should get rewarded by other p2poolers for their folly.
July 20, 2017, 03:52:18 PM
A lot of this discussion may be a non-event now. Since the BIP91 support is overwhelming now, the chance of the network being partitioned is getting smaller by the minute. Very shortly even those pools that haven't been supporting BIP91 will reluctantly convert to the code to avoid having their blocks being orphaned. In which case there really will only be segwit compatible blocks generated once BIP91 being activated except for some very small minority miners that may not have updated. If p2pool runs BIP141 segwit compatible that will likely be enough to avoid building on a dead end chain because it looks like there won't be any dead end chain...
Jump to: