Example for resource control and further questions about life HOT 7 OPEN

1. It is the gas limit - there's no example just yet but it's as simple as setting the GasLimit field in your VMConfig struct.

2. Yes, they can.

3. For execution time you can control either the clock time (number of milliseconds etc.) or instruction count or both. For memory you can control it to a single byte but it's suggested to respect the WebAssembly page size of 64KB.

4. Yes, it is possible. Set ReturnOnGasLimitExceeded in VMConfig to true, check the GasLimitExceeded flag in VM on each return and set the GasLimit field in VMConfig to a higher value if you want to "refuel" the process.

5. Yes. Basically you can do almost anything possible in Go through external function calls.

from life.

Yes, it's definitely possible. At any point when Execute() returns under a good condition (non-termination and non-error) like when a call to an external function happens, it's safe to snapshot the whole virtual machine and restore it anywhere else.

from life.

@losfair

For execution time you can control either the clock time (number of milliseconds etc.) or instruction count or both

Is there an example of timed execution of a given export function ?

from life.

Thank you, very interesting, and very close in semantics to my own project, which I wanted to port to WebAssembly: void4/notes#23 / https://www.youtube.com/watch?v=MBymOp6bTII

One last question for now: In your virtual machine, is it possible to retrieve full snapshots of suspended processes, serialize them, and then de-serialize and resume execution elsewhere (possibly on another machine)?

from life.

Are you familiar with Capability Security?

I made a presentation about it: https://twitter.com/dd4ta/status/1049793599804723201

I'd highly encourage you to have a look at KeyKOS, an operating system that combines both resource metering and capability security: http://cap-lore.com/CapTheory/upenn/OSRpaper.html

from life.

@void4 We are aware of capabilities-aware execution, and have basic capabilities provided under Life's API given how limited WebAssembly is as an instruction set.

To make execution deterministic for example, we have provided the necessary capabilities to disable floating point-related WebAssembly instructions.

from life.

Capability (transfer) security is a bit different than what is known as capabilities in Linux for example.

When designing a smart contract system (mainly interfaces and access permissions), especially with regard to secure composability in the case of contracts written by (partially) untrusted third parties, I highly recommend reading this paper: http://waterken.sourceforge.net/aclsdont/current.pdf

Object capabilities can prevent issues arising in identity based access controlled systems, such as the https://en.wikipedia.org/wiki/Confused_deputy_problem by eliminating ambient authority through combining remote object designation and access permissions in object called keys (or capabilities), which can be transferred and revoked.

The main difference here to pretty much all current languages (except E and a few others), is that called contracts can handle obtained permissions like variables and keep them apart. They cannot be tricked into misusing a permission given by a third party (previously or simultaneously) to execute a task that the calling party wouldn't have the permission to.

Somewhat related, you might like reading the Agoric Papers which were written in 1988.

from life.