Where are dapp files stored:
- Github (centralized method)
- 3rd party decentralized storage (decentralized method); we can't disclose yet who this will be, in the future there will be more than one option
When you install a dapp on your node, you will download it. Then all files are on your node. When you use the full client, it will use the local dapp sources. When you use the lite client you won't install it locally, it will connect to one of the (maximum 16 for now) master nodes and use their dapp sources.
Every dapp has its own side chain (custom chain). This is our interpretation of a decentralized application. While a smart contract always runs on the main chain, a dapp always has its own side chain.
So executable dapp code can run on a maximum of 16 full node servers, who then service X "lite" node runners who "log in" to use the dapp on the master nodes. Are these master nodes all Forging Delegates, all Standby delegates, or can they be a mixture of both? It sounds like the dapp author would want his side chain to be ALL on dedicated Standby Delegate servers and NOT on the Forging Delegate servers, because if ALL side chains are run by the 101 Club, they will get bogged down with running too many chains, right?
Does the custom side chain have to be running on the same 16 max master full node servers running the executable dapp code? The 16 master dapp nodes are processing possible changes / additions to the custom side chain and adding new blocks to it every 10 seconds, right?
Does this system mean that the owner of a dapp can send out a "contract closure" message to settle open contracts? If so, doesn't this mean a single server from the 101 club will have to settle all open dapp contracts within one blocktime upon receiving a closure trigger message? Isn't this really difficult, since the contracts can be scattered through many GB of the main blockchain? Will there be limits on the total number of open contracts or the time period over which they must be made and settled?