Turns out the new JSON parser settings caused it to consider trustLevel 0 (untrusted)
a default value and not write it to the disk, then when reading the object off the
disk it defaults to value 1 (trusted unverified), which is obviously not good.

This fixes that at the expense of a slightly weird JSON key