Hey folks,
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
there is a bug (or rather several) in the current implementation of ZEN which prevents "normal" blocks to be mined.
ZEN has implemented a special TX inside a block (BIP9) which wasn't active on testnet nor it's active on "getblocktemplate" so I wasn't aware of that and couldn't implement it in time. The next problem is that the daemon is actually accepting those false TX'es from my pool but isn't relaying the blocks to the network - so the pool thinks all is okay, but other nodes aren't accepting the blocks.
I'll try to get the special TX design implemented, however, those flaws should be fixed as well as the design is currently broken. It was implement to prevent replay-attacks (like in ethereum) as far as I was informed.
All blocks mined by the pool are invalid and therefore lost due to this issue currently.
Thank you for keeping us informed