bumping this thread... Did I post on the wrong board?
Topic: P2Pool, Scrypt mining, BIP101 and scrypt difficulty questions (Read 426 times)
September 19, 2016, 12:44:17 PM
This is probably old news to people, but if anyone is watching this thread:
https://github.com/p2pool/p2pool/issues/260
https://github.com/p2pool/p2pool/issues/202
https://github.com/luke-jr/bfgminer/issues/467
https://github.com/p2pool/p2pool/issues/241
My testing on stratum with different mining software shows that the stratum code that was backed out is still needed.
Still chasing down the rest.
https://github.com/p2pool/p2pool/issues/260
https://github.com/p2pool/p2pool/issues/202
https://github.com/luke-jr/bfgminer/issues/467
https://github.com/p2pool/p2pool/issues/241
My testing on stratum with different mining software shows that the stratum code that was backed out is still needed.
Still chasing down the rest.
September 17, 2016, 03:57:38 PM
I've been setting up a p2pool instance (latest version from github repo) on litecoin test network and am finding some things that I'm trying to work through:
a)The stratum difficulty code that adjusts for scrypt difficulty differneces were removed
-this is causing buckets of shares being rejected by p2pool as above the target, when they are not and are actually valid
b)There is code to make P2pool BIP101,CSV compliant which reports block version numbers differently
-this submits blocks to the blockchain, which are accepted, with version numbers like "536870912"
-I'm not sure what other effects its having.
My thought is to revert the code, my tests show that this fixes the issues caused by these changes, but I'm wondering if I'm not missing something.
Does anyone know if the blocks are valid version 4 blocks? Or are there changes that I can't find which would make them something different?
Is there some reason that the difficulty adjustment code was backed out?
Anyone know what's up with this? Or a reason I shouldn' t revert?
a)The stratum difficulty code that adjusts for scrypt difficulty differneces were removed
-this is causing buckets of shares being rejected by p2pool as above the target, when they are not and are actually valid
b)There is code to make P2pool BIP101,CSV compliant which reports block version numbers differently
-this submits blocks to the blockchain, which are accepted, with version numbers like "536870912"
-I'm not sure what other effects its having.
My thought is to revert the code, my tests show that this fixes the issues caused by these changes, but I'm wondering if I'm not missing something.
Does anyone know if the blocks are valid version 4 blocks? Or are there changes that I can't find which would make them something different?
Is there some reason that the difficulty adjustment code was backed out?
Anyone know what's up with this? Or a reason I shouldn' t revert?
Jump to: