Our Alternative to this issue is to allow updates to the support code at any position, given that the update is produced transparent first (as defined within our the latest CACM write-up) by incorporating it to a tamper-evidence, verifiable transparency ledger. This supplies two important Attributes: 1st, all end users in the support are served the