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".
21:21:12

getblock 69fb3392a4bcf11fe75ceb0f0d1aeb8fcbc0e63267696910f82c72dfc91378ba true
Thank you very much, it's nice to know that there is someone who can
see and understand what's behind the numbers.
What I write now, it's just to close it, and it's long and boring, I'm sorry.
The data you provided gave me a first confirmation, I needed more details, so I
searched for them directly on the block explorer, but the result seemed
incomplete, but it's not a cryptoid problem, but instead of what the NavCoin
daemon communicates to it.
To shorten the time, I downloaded the executable version of the wallet 4.0.1.1
for linux, and put it into a virtualbox. I proceeded to sync, and also activated
the transaction index with txindex=1, in order to retrieve the data needed
for each transaction.
When the wallet came back to work, I requested the data from the third
transaction of that block:
getrawtransaction 3955fabb08e6f54ac4f9ef35f043e5ce465a49974495f2d9d6ea8f453775ca5d 1
{
"hex": "01000000c3fff5580298b2eb6f74d607d641f01f197ffcbce9e344d880a461a27e4805dfb03f ...cut...
"txid": "3955fabb08e6f54ac4f9ef35f043e5ce465a49974495f2d9d6ea8f453775ca5d",
"hash": "3955fabb08e6f54ac4f9ef35f043e5ce465a49974495f2d9d6ea8f453775ca5d",
"size": 376,
"vsize": 376,
"version": 1,
"locktime": 975858,
"anon-destination": "",
...cut...
"blockhash": "69fb3392a4bcf11fe75ceb0f0d1aeb8fcbc0e63267696910f82c72dfc91378ba",
"height": 975860,
"confirmations": 14603,
"time": 1492516800,
"blocktime": 1492516800
}
As you can see, time and blocktime are the same, but at least in this case is wrong.
To me the old wallet 3 shows another "time", that is specific for each transaction.
If you look in "hex" string, starting from byte 5 to 9, you can find the real
value of the of the transaction's time field, which once turned and translated
into decimal becomes:
c3fff558 -> 0x58f5ffc3 -> 1492516803
So, how as wanted to demonstrate, in the block it has been incorporated (and
validated) a transaction, which from the point of view of the blockchain it has
been generated in a time subsequent to that of the block which contains it.
This is an event that the set of rules of NavCoin 2 blockchain reject,
but that the new wallet 4, accepted and made permanent by creating a
different fork.
Now that block is part of the Wallet4 fork story, it can not be remedied.
The fact that the getrawtransaction or decoderawtransaction command of
wallet 4 does not report the specific time of the transaction is not
surprising if we consider everything.
The Nav wallet 4 code comes from bitcoincore 0.13, and the internal format
of the transaction structure that it uses does not have a specific field
for time, whereas the Time field is very much used in the case of Nav wallets
and other coins based on POS.
The issue that the wallet 4 does not show a data like the transaction Time,
can make some controls much more complicated to do, but this issue can easily
be fixed in the code.
...
For experiment, I tried to see if making the old wallet 3 more "tolerant" to
that rule which was violated, it would be able to get back to the fork of
wallet 4, even using other new checkpoints to force it.
After many hours of resynchronization, finally the mod wallet 3 has pass that
block and go on... but after a while it stumbled into other blocks which it could
not accept for other reasons.
I read on Forum from "external" sources that has already been fixed the day of
passage to SegWit, so I think every extra effort to make compatible the old wallet 3
is now just a waste of time.
Some of the statistics I have shown here in the past were in part generated
with the help of some routines that were integrated into the code of a personal
version of the wallet 3.7, which now they can no longer work.
Unlucky I do not have the time to do all the code migration (and cross-check)
that would be needed, so I think I will not be able to do controls and statistics
as in the past, I'm sorry guys.
Some of routines have become obsolete, and other information can also be
found now on the official block explorer, so this is not a great loss.
