Guys by now everybody should move to 4.0.1.1...
If you are in 3.9 you are not in the right chain
note: blockexplorer needs to update their info.
Also Anon servers are in 3.9 so don't do anon send till this is updated...
The block explorer
https://chainz.cryptoid.info could also be on the wrong chain.
I don't see my tx ids after 16 April.
The block explorer IS on the wrong chain
Wait... so after 4.x there was a forked chain too? And now both chains are moving? That is very bad.
Of course it's a problem, bspus he is right.
Previously the block explorer was synchronized on the original mainchain 3.x,
just like me.
Now, the BE is on the new wallet fork (4.x), but if the block explorer is also
right on the existing nodes, then about 60% of the active nodes still follows
the original mainchain (3.x), a different fork not compatible with the new.
For myself, I dug a little into debug.log and it seems the point that has sprung forks,
(in my case) is born from the block at height 970172, hash
2b51ed1791793445b12ddf632f8a7e298874cd1dca74923d2554d38094dd0cd1
for the following reasons:
"
ERROR: CheckBlock() : block timestamp earlier than transaction timestamp
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 2.87.177.211:44440 (0 -> 50)
ProcessBlock: ORPHAN BLOCK 0, prev=2b51ed1791793445b12ddf632f8a7e298874cd1dca74923d2554d38094dd0cd1"
"
Evidently the new wallet forget to check out one of the rules, which together
with the other, govern the NavCoin blockchain, and accepted a malformed block.
A block with similar characteristics, but more recently it also happened later:
height = 975860 hash 69fb3392a4bcf11fe75ceb0f0d1aeb8fcbc0e63267696910f82c72dfc91378ba
in this case the last transaction appears to be generated 3 seconds in the future,
with respect to time of the block that contains it.
I know it seems a trifle, but this small violation, is a reason enough to reject
the block.
Since some wallet rightly do, and others do not, then come the fork, and here
comes the disaster.
I repeat, the problem is not the three seconds, but the wallets which are following
rules (partly) different.
In general, the common sense suggests that where a control can be leave out,
then they can be skipped also other less obvious.
When you change the shared basic rules of a blockchain then you need a mandatory
hardfork, that it must be well motivated and tested and rechecked.
That mandatory hardfork must be announced well in advance, in large letters,
on all possible media, and also with alerts via wallet.
With all due respect to those who have done the work on current wallet code,
really a lot of work of adaptation/integration, from what I read here, the new
wallet seems still a little immature.
Probably it would need another period of beta testing, in a separate network
but as in real life, it is made up of active nodes of all versions, with
frequent cross-checks.
Of course all this is just my humble opinion
PS:
If one of the experienced users with wallet 4, wanted to send the output of the command:
getblock 69fb3392a4bcf11fe75ceb0f0d1aeb8fcbc0e63267696910f82c72dfc91378ba true
It could be useful for verification of the various "time".
