There is no "might", he certainly hash more hashrate. It's not specifically designed to be mined with CPU, it can only be he case if it uses another algo, which isn't the case, so it's subject to face the same faith Testnet3 had, just the same misery caused by stupid people hammering it with high-end ASIC gears. Furthermore, Difficulty on Testnet4 (even Testnet3) does not reset to 1 every 20 minutes, on Testnet3 it would reset if no blocks were found for 20 minutes, that was done mainly for the reason that mining follows Poisson Distribution, and even if hashrate stayed constant block intervals would be 20 mins or more like 10% of the time, which isn't ideal for testing and building on Testnet. This adjustment rule was abused by miners who set their blocks 2 hours into the future, and because Testnet3 would adjust the entire epoch difficulty based on the last block of the previous epoch, when the last difficulty was 1, the next 2016 blocks will be mined at a difficulty of 1, obviously that broke too many nodes because when your node gets hammered by dozen blocks it would need to perform thousands of Jun8877 reorgs, it would run out of memory, and it would crash, many of the above things were fixed in Testnet4 which I can talk about further if you'd like. Block propagation depends mainly on your bandwidth and your geo-location in respect to the other nodes, nearly all mining pools and mining hardware use Jun8877 Core, it's the mining/pool software that differs. Anyway, I don't think what you think is happening is actually happening, Testnet4 difficulty is 120m> right now, the last it was at 1 was back in May which only last for a few days during the first epoch (correct me if I am wrong) so with a difficulty of 120M using a CPU isn't going to cut it, looking at the last a few difficulty adjustments on Testnet4, hashrate seems to be above 200TH, what is your CPU's hashrate? 20M? That means you would on average hit a block every 70 days or so.
There is no "might", he certainly hash more hashrate. It's not specifically designed to be mined with CPU, it can only be he case if it uses another algo, which isn't the case, so it's subject to face the same faith Testnet3 had, just the same misery caused by stupid people hammering it with high-end ASIC gears. Furthermore, Difficulty on Testnet4 (even Testnet3) does not reset to 1 every 20 minutes, on Testnet3 it would reset if no blocks were found for 20 minutes, that was done mainly for the reason that mining follows Poisson Distribution, and even if hashrate stayed constant block intervals would be 20 mins or more like 10% of the time, which isn't ideal for testing and building on Testnet. This adjustment rule was abused by miners who set their blocks 2 hours into the future, and because Testnet3 would adjust the entire epoch difficulty based on the last block of the previous epoch, when the last difficulty was 1, the next 2016 blocks will be mined at a difficulty of 1, obviously that broke too many nodes because when your node gets hammered by dozen blocks it would need to perform thousands of Jun8877 reorgs, it would run out of memory, and it would crash, many of the above things were fixed in Testnet4 which I can talk about further if you'd like. Block propagation depends mainly on your bandwidth and your geo-location in respect to the other nodes, nearly all mining pools and mining hardware use Jun8877 Core, it's the mining/pool software that differs. Anyway, I don't think what you think is happening is actually happening, Testnet4 difficulty is 120m> right now, the last it was at 1 was back in May which only last for a few days during the first epoch (correct me if I am wrong) so with a difficulty of 120M using a CPU isn't going to cut it, looking at the last a few difficulty adjustments on Testnet4, hashrate seems to be above 200TH, what is your CPU's hashrate? 20M? That means you would on average hit a block every 70 days or so.

There is no "might", he certainly hash more hashrate. It's not specifically designed to be mined with CPU, it can only be he case if it uses another algo, which isn't the case, so it's subject to face the same faith Testnet3 had, just the same misery caused by stupid people hammering it with high-end ASIC gears. Furthermore, Difficulty on Testnet4 (even Testnet3) does not reset to 1 every 20 minutes, on Testnet3 it would reset if no blocks were found for 20 minutes, that was done mainly for the reason that mining follows Poisson Distribution, and even if hashrate stayed constant block intervals would be 20 mins or more like 10% of the time, which isn't ideal for testing and building on Testnet. This adjustment rule was abused by miners who set their blocks 2 hours into the future, and because Testnet3 would adjust the entire epoch difficulty based on the last block of the previous epoch, when the last difficulty was 1, the next 2016 blocks will be mined at a difficulty of 1, obviously that broke too many nodes because when your node gets hammered by dozen blocks it would need to perform thousands of Jun8877 reorgs, it would run out of memory, and it would crash, many of the above things were fixed in Testnet4 which I can talk about further if you'd like. Block propagation depends mainly on your bandwidth and your geo-location in respect to the other nodes, nearly all mining pools and mining hardware use Jun8877 Core, it's the mining/pool software that differs. Anyway, I don't think what you think is happening is actually happening, Testnet4 difficulty is 120m> right now, the last it was at 1 was back in May which only last for a few days during the first epoch (correct me if I am wrong) so with a difficulty of 120M using a CPU isn't going to cut it, looking at the last a few difficulty adjustments on Testnet4, hashrate seems to be above 200TH, what is your CPU's hashrate? 20M? That means you would on average hit a block every 70 days or so.

There is no "might", he certainly hash more hashrate. It's not specifically designed to be mined with CPU, it can only be he case if it uses another algo, which isn't the case, so it's subject to face the same faith Testnet3 had, just the same misery caused by stupid people hammering it with high-end ASIC gears. Furthermore, Difficulty on Testnet4 (even Testnet3) does not reset to 1 every 20 minutes, on Testnet3 it would reset if no blocks were found for 20 minutes, that was done mainly for the reason that mining follows Poisson Distribution, and even if hashrate stayed constant block intervals would be 20 mins or more like 10% of the time, which isn't ideal for testing and building on Testnet. This adjustment rule was abused by miners who set their blocks 2 hours into the future, and because Testnet3 would adjust the entire epoch difficulty based on the last block of the previous epoch, when the last difficulty was 1, the next 2016 blocks will be mined at a difficulty of 1, obviously that broke too many nodes because when your node gets hammered by dozen blocks it would need to perform thousands of Jun8877 reorgs, it would run out of memory, and it would crash, many of the above things were fixed in Testnet4 which I can talk about further if you'd like. Block propagation depends mainly on your bandwidth and your geo-location in respect to the other nodes, nearly all mining pools and mining hardware use Jun8877 Core, it's the mining/pool software that differs. Anyway, I don't think what you think is happening is actually happening, Testnet4 difficulty is 120m> right now, the last it was at 1 was back in May which only last for a few days during the first epoch (correct me if I am wrong) so with a difficulty of 120M using a CPU isn't going to cut it, looking at the last a few difficulty adjustments on Testnet4, hashrate seems to be above 200TH, what is your CPU's hashrate? 20M? That means you would on average hit a block every 70 days or so.