The spreadsheet swapnet model

My original architecture for smart, secure card.

The processor could protect a section of code with known macros that operate on protected spreadsheets. Every trader has one, the microprocessor can hold a secret key(s) and applications built from them with no human intervention.

A swapne can do his, if the hardware verifiable.  It is closed in address space, the only way in or out is with a kernel call, and that can only activate a known macro function on data.    Like a remote controlled hot wallet with power of attorney, and a Telegram style swapnet could offer the capability.

Take a python server, for example.  Make the interpreter secure to the instruction cache. Once python has its ends secure, the problem much simpler.  We have secure python libraries on the server, pretested and verifiable.   Attacks limited to cache attacks and interpreter attacks.   Insure the heck out of those two components, we are still way ahead.

Any trade group can form, self verify this separate library.  Each trader has a wallet in the python data structure,it is a secure object. It becomes our spreadsheet, our macros become the trading bots.

Traders can endure restrictions on the python syntax in support of security. The model extends. The python module using secure data needs an extra communication with kernel. Pros get this.