Endo: Archived apps composed of archived libraries.

[kriskowal]

In order to minimize the weight of contracts on Agoric SDK, capturing their transitive dependencies in a string or archive wastes an opportunity.

This would require both a new bundle format (as in @agoric/bundle-source and @agoric/import-bundle) and also a transport mechanism (an additional power to async load/store the dependency archives), or alternately, a transport mechanism that can disassemble and reassemble the Zip files to preserve the illusion that bundles are just JSON.

Either way, we could use IPFS or something similar to distribute the overlapping fragments, where the fragments might either be Zip files of libraries, or individual files.

[kriskowal]

cc @dtribble

[zarutian]

This sounds suspictiously like hierchical uses of content-hash addressed blob store. Probably via readonly composition virtual filesystem that uses a root-manifest file named by a content-hash to find the other blobs/manifest to populate the vfs with data.

[kriskowal]

We are very likely to use a CAS. For unrelated reasons, I just implemented #794 today, which ensures the consistent hash of the manifest file (compartment-map.json) reflects consistent content of any particular entry point into an application. This doesn’t require the use of a CAS based on the same hash, but there is a certain synergy if we make that choice.

[kriskowal]

Parent issue Agoric/agoric-sdk#3871