Architecture

This prototype attempts to model Ethereum as three seperate but interlocking layers. Environment, Kernel, and VM.

 +------------------+
 |                  |
 | Environment      |
 |                  |
 +------------------+
        |
 +------------------+
 |                  |
 | Kernal           |
 |                  |
 +------------------+
        |
   interfaces
        |
 +------------------+
 |                  |
 | VM               |
 |                  |
 +------------------+

VM

The VM implements webassembly. Two sets of intefaces are exposed to it by the kernal. The Kernal Interface and The Environment Interface.

Kernel Interface

The kernel handles the following

• Interprocess communication
• Intializing the VM and exposes ROM containing code to the VM (codeHandler)
• Exposing the namespace and Intializes the Environment which VM instance exists (callHandler)
• Provides some built in contracts that facilitates different run levels (runTx, runBlock)
• Provides resource sharing and limiting via gas

The kernel Interface expose kernal primitives to VM which contain

• IPC (calls)
• Namespace Interface
  • GET/PUT/DELETE/ROOT/NEXT - currently implemented as a Map

Environment Interface

The Environment Interface expose the following

• blockchain infromation
• current block infromation
• transaction infromation