After PoW stage, it should be difficult to reach 19,21 GH of network hashpowers at block 27377 and 32106. We will be stay at PoW+PoS stage if the data trogdorjw73 provided is correct. Is this possible to reopen the block explorer let more community members to check this issue? We should do more care about this matter since three exchanges allow AC transaction now. Thanks for all your efforts, great community and team members.
I'm not sure what you mean, can you clarify?
Do you mean that you think PoW is still going on?
I can assure that PoW is not currently being accepted into the blockchain at this point. Although one can try to generate a proof of work, no other nodes would accept it into the blockchain due to this statement in CBlock::AcceptBlock()
if (IsProofOfWork() && nHeight > CUTOFF_HEIGHT)
return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));
Thanks for your reply, I quoted the topic #1263 from trogdorjw73 as follows:
trogdorjw73 on Today at 12:59:33 AM
Is the coin PoW difficulty frozen at 274.46071294? What's up with that? It's stayed static over the past 5000 blocks or so, and I see the hash rate hasn't really changed either. According to the latest wallet, networkhashps went from ~19GH at block 27377 up to ~21GH at block 32106. What's up with that? Are people still trying to mine AC directly? Or are these just miscellaneous bugs? Considering the temporary block explorer is down, I think we still have a problem. Hopefully it doesn't really matter, but given the checkered past of this coin things like this won't help instill confidence!"
As trogdorjw73 mentioned, networkhashps went from ~19GH at block 27377 up to ~21GH at block 32106 according to the latest wallet. Someone might mine AC at the blocks if his data is right. That's why I asked your help to clear this issue and thanks for your detailed explanation.
We are just a few people, but if the community starts asking them for updates, they will accelerate their process.
), but there must be a precise way to control/manage this. I don't think the challenge is the implementation of it into code, it's figuring a viable model out.
