That sounds about right: ;;bc,calcd 800 0.24236496Delia wrote:getdifficulty reports 0.24236496 for me, which I think is roughly consistent with the mining rate I've been getting (about 3-4 blocks per hour at 700-800 khps, and there doesn't seem to be anyone else mining on namecoin testnet).
(01:42:03 PM) gribble: The average time to generate a block at 800 Khps, given the supplied difficulty of 0.24236496, is 21 minutes and 41 seconds.
So what namecoin commitish are you now running to get these numbers? my experiments had vincent merged code at commit 9ed975bc44c9e5c60e, What config settings might I missed? or maybe I broke something in my merge.
You would see this from the mmproxy if parent is less diff then child chain:nodemaster wrote:In this case you'll find many parent chain blocks and very low AUX chain blocks. But the bigger problem would be in NMC/BTC case, that you need all BTC clients to update to get their client merged mining ready as AUX chain support needs a major updateDelia wrote: What happens if the aux chain has a higher difficulty than the parent chain?
ERROR: AUX POW parent hash 0000000964b614867559487da64722a0e4876de8fbc45e3b15bd7e07b2f03625 is not under target 00000007fff80000000000000000000000000000000000000000000000000000
as seen from merge-miner-proxy: