Technical design: Wasm bytecode installation and actor deployment

[raulk]

Even though we have prototyped a minimal actor deployment flow here: #444, we need a final design that takes into account aspects like:

• How actor code CIDs will be linked into the state tree.
• Which code metadata we support, how it's represented, and where is it stored (init actor or system actor?).
• Potential chunking of bytecode, if any. (Probably out of scope for M2.)
• Confirm InitActor enhancement to add install_code syscall.
• Make the install_code syscall privileged (depends on Privilege system for syscalls #468).
• Triggering bytecode validation and analysis, when, how, and costs.
• Determining Wasm bytecode limits, see Technical design: Wasm bytecode limits #731.
• Garbage collection of unused code entries?

[Stebalien]

Potential chunking of bytecode, if any. (Probably out of scope for M2.)

Assuming EVM-only?

Garbage collection of unused code entries?

I assume we'll punt this to "probably never".