Secure protection of the processor over networks

My public domain method.

Every processor leaves the foundry with its own private key, unseen by anything, its trace wiped out.  On leaving the foundry, the processor leaves a secret public key with the foundry key generator. Now the foundry key generator can distribute secure data back to individual processors, thus validating the processor. At any time, a site operator can request a coded message from the foundry to one or more processors, and the processor by translating correctly is verified.

From then of forth, the problem is counterfeit as each link in the chain can be verified when contracts are pre-proven for stable, predicted exits..  The foundry can deliver new keys to specific processors on request of applications.

Disconnect the foundry from the internet, make this happen via mail and USB programmable drives. The service is so valuable, the three day wait for a return USB chip is well worth it.  The foundry saves a list of processor ID and public key. It guards that and nothing else. It can use punch cards, guarantee no electronic trace of the list exists anywhere, except the moment a USB drive is written to.

The most valuable processors, the ones running trillion dollar pits go through this routine.  Relax the standard for a consumer card with a $50 bearer cash limit.

The code is all spectre standard in the pits, so new chunks of code placed in the cache can self guarantee their integrity back to the source, error are unproven contracts, instability and bugs. Everything chains off the ability of the processor to :

1) Hide its secret key always.
2) Use that for validation'
3) Be Spoecre compaible

Then it is up to app developers, trading pit designers and the whole host of sandbox trained financial wizards. Contracts need be simple, meet trusted ledger conditions properly, identify scofflaw exit and be simple. Somewhere in there is the universal trading pit entry a\nd exit protocol.