Right, but if a binary setialization was used, details encoding of Unicode would still have to be sorted out.

On the bright side, this does not about validation or consensus, but display of some special characters. (I mean I think there is no use case where clients REconstruct y Json, and any diffrence would lead to different hash.)