Jeremy Rand
As an aside, it would be possible to softfork Namecoin to impose a limit on the distance between the sidechain timestamps and the parent timestamps. This would greatly increase the...
To elaborate on my point, it's not really feasible to stop miners from *forward-dating* timestamps in a reorg attack, since the timestamp enforcement in Bitcoin and Namecoin only requires that...
Okay, so the attack here is that someone who's mining today wants to replace an AuxPoW header from the distant past which has much lower difficulty, and therefore is trivially...
First off, that's not how checkpoints work. Checkpoints don't commit to the *first* block in a chain, they commit to the set of all blocks below a given height. Committing...
> I just wanted to let you know about this issue. And we thank you for that. > However, if you think it's safe how it is, leave it. I...
> Otherwise I like your idea with hashing the auxpow hash into the Blockheader, but the auxpow is serialized after the block. So the block hash will change. The AuxPoW...
As an aside, I tend to think there are other spam vectors besides this that are more important to close for Namecoin, some of which (e.g. decreasing the block weight...
CC: @classilla
The Coveralls fails on Azure appear to not be directly related to this PR.
Addressed feedback, thanks for catching those. Coveralls still unhappy as before due to a missing token. I'm pretty sure the Py38_Win pytest failure is unrelated to this PR as well...