P.S. Sign up for this mailing list so that you get proactively notified when there are required upgrades in the future:
http://groups.google.com/group/p2pool-notifications
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 726. (Read 2591920 times)
April 05, 2012, 09:57:24 AM
April 05, 2012, 09:55:25 AM
I just found that p2pool works with "Pool: 19628MH/s" on my host. Does that mean p2pool forked again and I am working on a branch?
I restarted my p2pool client - but it shows same Pool speed. What's going on?
I restarted my p2pool client - but it shows same Pool speed. What's going on?
It probably means your version of p2pool and/or your version of bitcoin are too old and you have been blocked from the normal p2pool network and are on a fork with all the other people that are still on old versions.
You need to be running the latest version of p2pool (see the first post of this thread) and you need to be running a recent version of bitcoin that support BIP16 (just install 0.6.0 if you aren't sure).
April 05, 2012, 09:31:56 AM
What version of p2pool?
What version of bitcoind?
What version of bitcoind?
April 05, 2012, 09:31:15 AM
I just found that p2pool works with "Pool: 19628MH/s" on my host. Does that mean p2pool forked again and I am working on a branch?
I restarted my p2pool client - but it shows same Pool speed. What's going on?
I restarted my p2pool client - but it shows same Pool speed. What's going on?
April 04, 2012, 09:44:37 PM
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
I see that is a substantial problem.
There is no problem. Nothing is lost.
They are ALREADY excluded.
Any node which is running old incompatible software will have their SHARES rejected by p2pool network. p2pool can't stop them from producing invalid blocks but they don't get credit for GOOD blocks either.
This is why you see the node & hashrate graph has declined. Those excluded miners are no longer worker towards p2pool.
Now sometimes they will produce a block but it will be overwritten and they will never get paid. Since they aren't getting paid for good blocks, and they aren't getting paid for their bad blocks their revenue will be 0.00.
Another way to look at it is the bad miners are on a seperate fork. WE (good p2pool miners) produce blocks and only split the rewards among good miners. The bad miners can only get payouts from bad blocks but those blocks will always be orphaned so they will never get paid.
TL/DR
The bad miners and bad blocks don't affect you payout a single bit cent.
No matter how many bad blocks the idiots produce they will never provide you any revenue.
No matter how many idiots/bad miners there are they will never get any revenue from good blocks.
There is no problem. Nothing is lost.
Miners producing bad blocks are already excluded from payments on good blocks.
Thank you for the clarification.
April 04, 2012, 07:27:25 AM
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
I see that is a substantial problem.
There is no problem. Nothing is lost.
They are ALREADY excluded.
Any node which is running old incompatible software will have their SHARES rejected by p2pool network. p2pool can't stop them from producing invalid blocks but they don't get credit for GOOD blocks either.
This is why you see the node & hashrate graph has declined. Those excluded miners are no longer worker towards p2pool.
Now sometimes they will produce a block but it will be overwritten and they will never get paid. Since they aren't getting paid for good blocks, and they aren't getting paid for their bad blocks their revenue will be 0.00.
Another way to look at it is the bad miners are on a seperate fork. WE (good p2pool miners) produce blocks and only split the rewards among good miners. The bad miners can only get payouts from bad blocks but those blocks will always be orphaned so they will never get paid.
TL/DR
The bad miners and bad blocks don't affect you payout a single bit cent.
No matter how many bad blocks the idiots produce they will never provide you any revenue.
No matter how many idiots/bad miners there are they will never get any revenue from good blocks.
There is no problem. Nothing is lost.
Miners producing bad blocks are already excluded from payments on good blocks.
April 04, 2012, 07:26:49 AM
Can we defend against this?
Panda Mouse.
Panda Mouse.
Yes. have everyone update their p2pool/bitcoind/miners etc to be BIP-aware.
There is no "attack" or "problem", there are just miners with outdated, now incompatible software.
Ente
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
Panda Mouse.
April 04, 2012, 06:12:30 AM
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
Panda Mouse.
I see that is a substantial problem.
Panda Mouse.
From which network, bitcoin or p2pool? Those clients are already "removed" in the sense that they are isolated. They may find a block, which then is orphaned. So they have no influence on the main branch of the chain.
What problem do you see? The only problem is, imho, the slightly reduced hashing power of the network, and, from their perspective, the zero income ;-)
Ente
Yes you're right.
April 04, 2012, 05:46:21 AM
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
Panda Mouse.
I see that is a substantial problem.
Panda Mouse.
From which network, bitcoin or p2pool? Those clients are already "removed" in the sense that they are isolated. They may find a block, which then is orphaned. So they have no influence on the main branch of the chain.
What problem do you see? The only problem is, imho, the slightly reduced hashing power of the network, and, from their perspective, the zero income ;-)
Ente
April 04, 2012, 05:41:31 AM
Can we defend against this?
Panda Mouse.
Panda Mouse.
Yes. have everyone update their p2pool/bitcoind/miners etc to be BIP-aware.
There is no "attack" or "problem", there are just miners with outdated, now incompatible software.
Ente
Is it possible to automatically remove that machine with old software from the network?
I see that is a substantial problem.
Panda Mouse.
April 04, 2012, 05:24:53 AM
Can we defend against this?
Panda Mouse.
Panda Mouse.
Yes. have everyone update their p2pool/bitcoind/miners etc to be BIP-aware.
There is no "attack" or "problem", there are just miners with outdated, now incompatible software.
Ente
April 04, 2012, 04:30:10 AM
...
If everyone on P2Pool has the BIP update, except one person, that one person can still generate a P2Pool block if their P2Pool is current and Bitcoind is considered OK by the P2Pool software but that block will be rejected by most people on the network if it contains any poisoned transactions
(Yes someone has purposely generated poisoned transactions using the IP address 67.210.248.3 so that if anyone isn't running the current BIP they will include those invalid transactions into their blocks and thus their blocks will be rejected by the network)
If they had the BIP update then their bitcoind would not accept the poisoned transaction(s) and thus the blocks they generate would be OK
This is the transaction that causes most? of the problems
https://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2?show_adv=true
If everyone on P2Pool has the BIP update, except one person, that one person can still generate a P2Pool block if their P2Pool is current and Bitcoind is considered OK by the P2Pool software but that block will be rejected by most people on the network if it contains any poisoned transactions
(Yes someone has purposely generated poisoned transactions using the IP address 67.210.248.3 so that if anyone isn't running the current BIP they will include those invalid transactions into their blocks and thus their blocks will be rejected by the network)
If they had the BIP update then their bitcoind would not accept the poisoned transaction(s) and thus the blocks they generate would be OK
This is the transaction that causes most? of the problems
https://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2?show_adv=true
Can we defend against this?
Panda Mouse.
April 04, 2012, 03:49:09 AM
What is going on, why does not include a block 174234?
Panda Mouse.
Because whoever created the block, does not have the BIP update in their bitcoind thus they built an invalid block and thus when the fork was resolved as expected, the P2Pool block 174234 went bye bye.Panda Mouse.
To see the forks that keep happening, look here: http://blockchain.info/orphaned-blocks
Also note that on that page where it says "DeepBit" it isn't always correct.
Thank you kano, as I think it's not our (p2pool) bad BIP fault?
The person on P2Pool who generated that block is missing the BIP update.
If everyone on P2Pool has the BIP update, except one person, that one person can still generate a P2Pool block if their P2Pool is current and Bitcoind is considered OK by the P2Pool software but that block will be rejected by most people on the network if it contains any poisoned transactions
(Yes someone has purposely generated poisoned transactions using the IP address 67.210.248.3 so that if anyone isn't running the current BIP they will include those invalid transactions into their blocks and thus their blocks will be rejected by the network)
If they had the BIP update then their bitcoind would not accept the poisoned transaction(s) and thus the blocks they generate would be OK
This is the transaction that causes most? of the problems
https://blockchain.info/tx-index/3618498/4005d6bea3a93fb72f006d23e2685b85069d270cb57d15f0c057ef2d5e3f78d2?show_adv=true
April 04, 2012, 03:03:21 AM
What is going on, why does not include a block 174234?
Panda Mouse.
Because whoever created the block, does not have the BIP update in their bitcoind thus they built an invalid block and thus when the fork was resolved as expected, the P2Pool block 174234 went bye bye.Panda Mouse.
To see the forks that keep happening, look here: http://blockchain.info/orphaned-blocks
Also note that on that page where it says "DeepBit" it isn't always correct.
Thank you kano, as I think it's not our (p2pool) bad BIP fault?
April 04, 2012, 02:35:38 AM
What is going on, why does not include a block 174234?
Panda Mouse.
Because whoever created the block, does not have the BIP update in their bitcoind thus they built an invalid block and thus when the fork was resolved as expected, the P2Pool block 174234 went bye bye.Panda Mouse.
To see the forks that keep happening, look here: http://blockchain.info/orphaned-blocks
Also note that on that page where it says "DeepBit" it isn't always correct.
April 04, 2012, 02:01:37 AM
What is going on, why does not include a block 174234?
Panda Mouse.
Panda Mouse.
April 03, 2012, 10:55:21 AM
Just got a payment
April 03, 2012, 10:52:45 AM
Finally got it after 31 hours. I was starting to get worried.
April 03, 2012, 09:50:20 AM
http://p2pool.info shows a list of all found blocks. you only get paid when a block is found.
We have had really bad luck for the past two blocks.
You should have received a payment from block 174118 though roughly 4 hours ago.
Code:
Block When Generation Tx Round Duration vs. Expected(?)
174118 4 hours ago 11bc5c96e0e82a3f7cfa93f068f50f 1d1h37m 404.9%
173988 1 day ag0 765e7af6d1bc878aa9c55d238e8625 6h45m 102.9%
We have had really bad luck for the past two blocks.
You should have received a payment from block 174118 though roughly 4 hours ago.
174118 wasn't a real p2pool block. It was an "unupgraded fork of p2pool" block. None of the current p2pool miners (i.e. probably no one actually following this thread) got a payment in it.
It has been removed from p2pool.info, but you won't see that unless you refresh the page (the auto refresh doesn't expect blocks to be removed, only added).
April 03, 2012, 09:43:32 AM
http://p2pool.info shows a list of all found blocks. you only get paid when a block is found.
We have had really bad luck for the past two blocks.
You should have received a payment from block 174118 though roughly 4 hours ago.
Code:
Block When Generation Tx Round Duration vs. Expected(?)
174118 4 hours ago 11bc5c96e0e82a3f7cfa93f068f50f 1d1h37m 404.9%
173988 1 day ag0 765e7af6d1bc878aa9c55d238e8625 6h45m 102.9%
We have had really bad luck for the past two blocks.
You should have received a payment from block 174118 though roughly 4 hours ago.
Jump to: