Hmm.. strange if it works at all... that's what my logic was based on - for example:That could be it.
Though, looking at Poolers source code for the old version the only time he messed with the POW was for the actual electrum-client and not the server. With litecoin using scrypt instead of sha256 I'd assume if it was needed it would need to be edited in both the server and client.
https://github.com/pooler/electrum-ltc-server/compare/spesmilo:master...master
I'll spend some more time on it.
This https://github.com/Propulsions/electrum-drk-server/blob/master/src/blockchain_processor.py#L655 uses hash_header I mentioned before and stores last_hash
and then https://github.com/Propulsions/electrum-drk-server/blob/master/src/blockchain_processor.py#L662 uses that last_hash to call "darkcoind getblock <last_hash>"
The last statement will definitely fail if hash_header used sha256d to form last_hash earlier.