Notable

Opera Launches Special ‘Labs’ Version of Built-In Crypto Wallet for Desktop Browser

Think of that browser function that auto-fills forms for you.  This is a trend, the secure element within the processor.  We will ge embedded, secure javascript next to the secured keys.    Browsing the financial markets is what the bots do, autonomously. The secure element has to digest and emit JSON script, through non-memory mapped portals or in instruction cache with spectre standards. The secure element hold account values along with keys.  Leave itg at that and monetary opcodes are tiny JSON script.

But, but... The secure element supports bearer cash,  it enforces the double spend restriction.  So, why not embed the whole js interpreter into the secure element, it becomes standalone when need be and needs little display. Then create the concept of voluntarily enforced contracts, and app layer within the card.  When you adjust accounts, sometimes, the ledger service needs info from you, and all that exchange should go through your smart card, it is always carried with a thumb, carrying your guarantee.

Security starts at the foundry. All processors can create their own secret kehy, and the first to exchange are the new dard processor and foundry processor. They keep the secret key and emit the puplic key to the other.  The card will always accept messages from the foundry.

Otherwise, who enforces double spend?  By thumbprint. The first embedded app is the thumb print enabled bearer cash function.  From their we get ATM apps to adjust cash balances an manage discount coins.  If you have your card, at a hotel room then use any interne connection and your handheld, or the lobby computer.  All the core details are in your card, protected by thumb print.