Our solution to this issue is to permit updates towards the support code at any point, assuming that the update is built transparent 1st (as stated within our latest CACM posting) by introducing it into a tamper-evidence, verifiable transparency ledger. This gives two significant Homes: very first, all end users of the services are served a similar