Open Infernoman opened 7 years ago
Happens with UnitCurrency as well. [2017-01-26 03:00:22.605] [DEBUG] [default] - [Pool unitcurrency Thread 15 Failed to submit potential auxiliary block: {"code":-1,"message":"ReadCompactSize() : size too large"}]
Which seems to also be a hybrid pow/pos coin. This could be related to nomp or Crown. Whichever it is needs to be tracked. Coming to the conclusion the may be nomp related to the coinbase/coinstake
afaik merged mining with a POS/POS coin as main doesnt work
What is this due to, main chain, aux chain or pool software? And can anything be done to resolve the issue?
Either peercoin Will need a patch or Pool software.. but Pool software patch would only be a stop Gap measure
Den 27. jan. 2017 6.06 AM skrev "Alastair Clark" notifications@github.com:
What is this due to, main chain, aux chain or pool software? And can anything be done to resolve the issue?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Crowndev/crowncoin/issues/28#issuecomment-275590005, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0r36kILxXqTqJ8qSA___U27TdwlKIyks5rWXtTgaJpZM4LuYYH .
testing...
@Infernoman could you close this now we have switched to PoS?
Bump
[2017-01-26 02:30:10.299] [DEBUG] [default] - [Pool peercoin Thread 16 Failed to submit potential auxiliary block: {"code":-1,"message":"ReadCompactSize() : size too large"}]
Peercoin has a mining issue focused on Crown. This related back to the size of the network headers? being too large. Crowncoin will refuse every block mined from peercoin with the message ReadCompactSize(): size too large. It also happens with other coins as well. But not nearly as often and other networks are at least mine-able.