O> FSC-0048 is mostly useless nowadays and only adds complexity.
You right. Using auxNet and check magic value 65535 and check origPoint != 0 it look like some kind of data hacks.
O> Practically every tosser supports FSC-0039
I start write source code with idea about implementing PKTv3 packets but no nodes with supports in Russia zone as I know.
I debugging GP source code with make checks with "Parma Tosser" and review Parma source code I make compatible GP with my BOSS node. I assume Parma Tosser compatible with FSC-0001, FSC-0048 and FSC-0045 bases on my source code vision.
I also have another one point address on 5030/1081 node. Here an extremely strange case with crash Husky Tosser (HPT) on the 39th proposal occurred and we research with BOSS this incendent and did not understand what it was refered with, so for now I am switch on using the 48th proposals.
So it is at now very difficult to understand and there is a danger of losing data about the zone and point by returning back on FSC-0001 compatible mode.
I do not exclude the possibility of using the 39th version of the proposal in the future, but I need to make sure that this will work with my nodes.
In any case, increasing count requests about support some feature is increase chance of select one specific implementation in favor of another.
O> Btw, it's an FSC not an FTS.
You right. It would be convenient to have a standard that would support every tosser to support one single same coding scheme.
I review ASCII version of PKTv3 format with the text data representation, since there is less bit field hacks, but as far as I understand today, there are no tossers with this coding scheme support.
--- Golden/Windows-amd64 1.2.16 2020-11-03 23:07 MSK (master) * Origin: Если дружишь с хромым, сам начинаешь прихрамывать (2:5030/1081.102)
