ALUX Network – A Distributed Runtime to Unify Web 2 & 3
The Problem We Are Solving
- Blockchains are essentially state transition machines.
- Current blockchain solutions only support a tiny subset of state transitions in Web 2.
ALUX as A “Distributed Runtime” for Universal State Transitions
ALUX supports multiple types of state transitions unsupported in other projects.
Parallel Execution
EVM/WASM instances can run in parallel like Monad, Aptos, and others.
Concurrent Execution
ALUX allows TXs to execute as coroutines, which can be suspended, awakened, and interleaved with each other. Nondeterministically executed, but deterministically replayed.
Composite Transitions
TXs can span across multiple shards, or between on-chain & off-chain systems, while maintaining ACID (Atomicity, Consistency, Isolation, Durability) — a key feature to unite Web 2 and Web 3.
Ultra Security - Native OCAP Support
ALUX implements OCAP (Object Capability) at the VM instruction level – a contract cannot access a resource unless its unforgeable reference is passed to the contract. This is a key feature for secure composability and a very powerful primitive for implementing account abstraction and programmable money.
Compatibility
ALUX works as a “distributed runtime.” Other VMs like EVM, WASM, level 1-4 ZK-EVM instances are all able to run concurrently on ALUX runtime.