Daniel Kraft

If you are doing a hard fork anyway (which a change like this would be), there's nothing wrong with changing the parsing format. So you can easily add the chain...

True, any external software parsing auxpow's would need to be updated. I'm not really aware of any, though. And everything that would be affected will be easy to fix. >...

Ah yes, that check. I can imagine it is there to prevent directly mining a block and using it as auxpow for the next one (so getting two for the...

That is most likely something changed in upstream Bitcoin Core, so not specific to Namecoin. I think @xaya had some issues with this as well. Do you recall any details...

It was not, it was addressed to Andrew (@xaya) who I believe had similar issues on Windows in the past and may be able to provide more details. In any...

I agree that would be useful. However, I'm not sure if that should be part of the core daemon or perhaps rather something done by the Qt "frontend". @JeremyRand, what...

I don't have a super-strong opinion against this, but I also don't really see the importance of this from a user's point of view. If anything, it would mostly be...

Thanks for the report! Please explain in more detail what exactly is going wrong (i.e. what does "can't run" mean precisely - does it crash, does it not sync, does...

Ok thanks. Do you get connections when you start it, or none at all? It may be that you manually have to set `addnode`'s for testnet (and in general, the...

Interesting! The rules are filled in here: https://github.com/namecoin/namecoin-core/blob/5026155158efb285079f088a3812e090dec5c246/src/rpc/mining.cpp#L581-L622 This code only takes BIP9 into account, so that's presumably the reason. Note that Bitcoin 0.19 also changed activation of Segwit and...