{"id":18798,"date":"2026-03-29T21:24:39","date_gmt":"2026-03-29T21:24:39","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/29\/ambients-applied-to-ethereum-ethereum-foundation-blog\/"},"modified":"2026-03-29T21:24:39","modified_gmt":"2026-03-29T21:24:39","slug":"ambients-applied-to-ethereum-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/29\/ambients-applied-to-ethereum-ethereum-foundation-blog\/","title":{"rendered":"Ambients Applied to Ethereum | Ethereum Foundation Blog"},"content":{"rendered":"


\n<\/p>\n

\n

<\/g><\/svg><\/a>Part I<\/h2>\n
Sometimes Ethereum is compared to a singleton Virtual Machine. \u00a0While this is correct in some sense; I think it is a bit more. First of all what is a singleton in a distributed system? It is merely a set of values that some threshold of participants have come to consensus on. \u00a0A Virtual Machine is a computational environment that is isolated from the physical computer and from other environments.<\/h5>\n

A hypervisor allows the physical machine to be multiplexed into many VMs. According to this definition a common hypervisor is the web browser where webpages are VMs. Another example of a hypervisor would be Ethereum as each contract \u00a0gets its own isolated computational environment.<\/p>\n

There are many differences between the common web browser and Ethereum, but one of the more interesting ones is how VMs communicate and interact with each other. Web browsers don\u2019t provide a way for VMs to directly interact while Ethereum on the other hand provides some simple mechanism for VM interaction; the opcodes CALL, DELEGATECALL, CALLCODE, CREATE. \u00a0In this post will explore the question; What other rules could exist? \u00a0Can we generalize VM interactions and provided an abstract framework for these interactions? And from this framework can we reason about distributed hypervisors?<\/p>\n

Most of this post will resemble ambient calculus<\/a> but there are several notable differences from ambient calculus and what is presented here. The diagrams can be thought of as bigraphs<\/a> but they should also be self explanatory. Part I will describe the rules of ambients and then apply them to Ethereum. Part II will discuss scaling in the terms of ambients as laid out by part I.<\/p>\n

<\/g><\/svg><\/a>What is an Ambient?<\/h2>\n

\"image09\"<\/a><\/p>\n

An ambient is a bounded place in which computation can occur. A boundary determines what is inside and what is outside an ambient. \u00a0For ambients we call this boundary a membrane. The area inside an ambient is hierarchical namespace. Objects can exist inside an ambient. The objects are addressable via the namespace. There are three base elements in ambient calculus. Objects, Namespaces and Messages.<\/p>\n

<\/g><\/svg><\/a>Hierarchical Namespaces<\/h4>\n

One of the most familiar namespace is the file system tree. \u00a0Namespaces allow us to identify objects with paths or names. Namespaces here have the following properties<\/p>\n