Contract language

 A contract is a subcontract followed by a stable exit with a fails to deliver fee. So we get a simple subroutine exit and restore procedure in the cache.

Otherwise a primitive contract is mostly a ledger swap using cash for half the swap, and that is followed an exit with fails to deliver fee.

But the insurance fees need not be native tokens, they can be in any denomination. Changing denominations just kicks in a stable sub contract for ledger transfer across dual ledgers. ha is the most complex.  

But you cannot set fees without trading pits along the way, intermediating. So you need bearer cash. Executing a ledger exchange with a fails to deliver timeout implies cash on hand manageable by the local spectre cache. So an insured ledger swap implies a delegation of authority to a bot inside a pit watching timeout and ledger changes. That is a pause for the local cache kernel, and requires a specre safe swap out or lock out of cache. 

So, with the aide of spectre safe kernel, and the admission of likely fails, a mix of trusted miners and hot wallet pits are needed. Over the counter is mostly about accepting market price, and skipping the pits.

But it is clear, I think, we can make a contract language that looks a lot like the written contracts with a 'c' like structure. Both legal and automated contract have the same specified timeouts and count limits. Both are built on provable exits. Both have sub contract and other recursive modes.

The nodes of the total contract defied by counter parties, known as live human thumbprints. The minimum span paths are defined at compile time, by provable reduction methods. Leaks identified as congestion points needing a rip o the pits. If we are spectre safe linked sets of cache, then we have a safe stack structure, and local counter parties defined and undefined. The provable compiler is distributing fails to deliver risk to keep it fair at all level of a complex contract. So computable risk becomes a commutative power in reducing the contract network to a minimal spanning tree curing compilation and proving. Risk is defined as the probability of exceeding a time, count or limit; all of which can cause a fails to deliver exit.  Because at the time of execution, the congestion on the ledgers is unknown, the fee determined by pit conditions at some point in every contract with a safe exit. The risk is tht of going off line to locate a scofflaw or get an insurance payout. But the vast majority of scofflaws you can catch with revert within timeout. And safe contracts allow test conditions for an early exit if the ledgers are over congested.