The stateful Internet project

[humbitious]

What if we could make real in a solid story and set of product-level requirement what we need in a stateful Internet...why just oracles, plasmas, and even sidechains aren't sufficient...why we need to have generalized code coordination between n-lateral state machines coordinated by a root mainnet, and what it would mean if an application could pull together two or more parties, instantiate a super-private segregated state machine between them, pin it to a mainnet or intermediate "plasma" and pass parameters to and from stored procedures residing on different state machines and the main net...on trusted edge compute where the data and the logic are secured from tampering and surveillance. What if this could be done in an instant whenever parties need to interact in ways where even the relationship or the existence of the business agreements shouldn't be known to other parties on some common public or private ledger. And what if this were done all in under a minute for tiny amounts of money? Does this really need something like Chainlink's Link token, which many think introduces a level of avarice that is not appropriate at this layer? Or is that the best way?

The Problem

How does it work?

Existing Work

Fit and Fitness

Assumptions

[brian-lc]

Would make an interesting medium article @humbitious