Apple kernel security

In addition, the operating system kernels enforce access controls to prevent unauthorized access to data. These controls most often take the form of sandboxing apps (which restrict what data an app can access), as well as enforcing Data Vaults. Data vaults can be thought of as inverted sandboxes. Rather than restricting the calls an app can make, Data Vaults restrict access to the protected data (again, enforced by the kernel independent of file encryption) regardless of whether the originating process is itself sandboxed or not.

I like it, but it is missing something.

 I need a contract that I cannot break, except through a predefined exit.  Thus the subscription manager can give me no double spending tokens, cash, which I send freely to any other subscriber, with no third party.

Apple can add this mode, easy enough, with a timeout.  It needs to keep some memory that is kernel only, read and write and that data cannot leave the instruction cache. But it must have a timeout.   Otherwise, you burn your thumb sand can never get the buggar out of the instruction cache.

For subscription services, the exit takes place at the end of the month, before renewal.   So if you  have smart card, then you will still need to review all your contracts, monthly or quarterly.  The sandbox forgets, it relies on trading pits and ledgers. Making a semi martingale from pit action is forgetting, consuming all past knowledge at once. Taking the Coasian price. It removes arbitrage.

So, with the kernel having authority to keep tour contract, then we have what is needed for spectre compliant.  And the processor has a timeout, the smart card expires. It must be renewed, in the sense of activating the security coin and revalidating and update keys.

So, in effect, a mall kernel change in the iPhone and we have all we need for sandbox in any currency.  Even with an uncooperative central bank, we can slip an automated layer onto any regulated account.  But I know Powell, he will go for bearer digital asset if he gets an escape from Treasury and Congress. H knows the tax dollar is losing more and more market share. It needes to compete.

If two iPhone uses both had contract enforcement then they could exchange cash in any currency, direct even though they are strangers..  We can see how easy it is, it allows the bots to have autonomy, and this scares the regulators.  But the timeout, we can enforce limited liability. The kernel will obey cash channel contracts.  Thus if the user agrees to the complete Swift currency contracts, then they agree with a specified kernel timeout on liabilities, and a contract is a liability.

The system allows perfect enforcement of accounting rules across corporations, and long as they have iPhones. It can be taylored to track shipments. Unlock data to the proper security. 

Apples run Solidify, and Solidify has the hooks for provability. Also we can make a UBS dongle for analog logic keys. But that is lower priority than enforced, stable  contracts.  All we need is another 100 lines of kernel code.  Anytime two or more iPhones enter a contract, they only need start with a public verification key., in which each signature is recorded. Then they agree on the contract, the system is provably stable up to a counterfeit.

Expense accounting is an enforced app. From start to finish t account for cash purchases by corporate rule.  Trading rules, a special contract for operating in a pit. The rules enforce round robin access with congestion fees fairly allocated.  A series of over the counter trades two iPhone user may use to exchange cash and equity in a specific environment.  

Trading pits are spectre compatible, and you o can use python or solidify.  The trading algorithms embedded in contract segments. They are generally well proven with all the needed interface points into the trade board. Trading bots can be in one of three states, in the cache, making a bet, in the cache, communication with an external, or securely idle.

We can do this with iPhone, we just need some kernel space. And some memory bracket that is kernel only.  There are two or three kernel operations that interact with this protected space.  With that we can get provability. Do a lot of neat stuff with iPhone. Improve the lives of everyone equally which is a big win for the poor.

What about ETH?

Ethereum is a currency channel with contracts and each iPhone is a miner.  But it only makes a local chain with contract participants. Then the completed contracts are released to the general miners. They keep a history of ETH and the contract paths, evidently.  In provable contract, all the participants should agree on the outcome, as all timeouts expire.  So the participants accept it has completed work.

So a big harry chain of solidify must be on their block chain in a verifiable form. So the smart card carries a portion of the ETH block chain.  Then on contract completion they all sign off and are don since there should not have been any conflicts.