D B F

en……

[ALUX @alux_network]

🎯 From Demo to Vision

The upcoming demo is more than a technical milestone—it is a concrete step toward a broader vision for ALUX.

At its core, ALUX is designed around composability: the ability to coordinate computation, state, and access across distributed systems in a unified and reliable way.

🧩 1. Composability of State Transitions

ALUX enables composable state transitions across two key dimensions:

⏳ Temporal composability — State transitions can occur across different blocks (over time) while still achieving atomic finalization. This is realized through cross-block atomic execution.

🌐 Spatial composability — State transitions can occur across different systems (e.g., shards) and still be finalized atomically, enabling true cross-shard execution and horizontal scalability.

🔐 2. Composability of Access Control

In ALUX, processes interact exclusively through unforgeable names, enabling what we call composable security.

Unlike traditional ACL-based systems, which struggle when multiple principals are involved, this model allows secure, flexible, and scalable coordination across many participants.

🖥️ Toward a Virtual Machine Abstraction

These two forms of composability form the foundation of a distributed concurrent runtime.

In this model:

Many physical machines (on-chain and off-chain) → operate together as → one logical virtual machine

We refer to this as the Virtual Machine Abstraction.

🌍 Long-Term Vision: A World Operating System

Building on this abstraction, ALUX enables something more ambitious:

A world operating system — a unified execution layer where services, agents, and contracts can coordinate seamlessly and safely across heterogeneous infrastructure.

This is particularly critical for the emerging agent-driven future 🤖, where autonomous systems require reliable coordination, composability, and security at scale.

🏗️ Architecture Overview

The following chart illustrates the architectural hierarchy of this vision — from physical infrastructure to the unified runtime (through virtual machine abstraction), and ultimately to the world operating system layer.

#Web3 #Web4 #Concurrent #Composite #Blockchain $ALUX

[D B F @DakeBlueForest]

@alux_network Great project, be patient and wait!

[ALUX @alux_network]

👨🏻‍🎨 ALUX roadmap update!

1/ In Q4 2025, we continued advancing atomic cross-block long-transaction (long-TX) support.

Long-TX test cases now run successfully with hardcoded sync points—putting us one step away from our first major milestone.

2/ Next step: replace those sync points with BlockGit consensus.

That unlocks our first working demo: fully on-chain, atomic long-TX execution across multiple blocks.

3/ We also refactored the codebase to improve modularity.

These upgrades lay the groundwork for:

- faster, more flexible evolution toward sharding
- extensions beyond blockchain-only use cases

4/ In parallel, we explored several logical clock designs to capture execution traces efficiently—enabling analysis and enforcement of different transaction isolation levels.

Implementation is now underway.

5/ Looking ahead to Q1 2026, our primary objective is clear:

Pass integrated tests for atomic long-TX execution on top of BlockGit consensus.

This milestone will serve as a proof of concept for our novel blockchain design.

6/ After that, we’ll focus on production-ready features needed to launch a functional testnet.

7/ We’re community-driven—and we wouldn’t be here without you. Our small but capable team continues to deliver, addressing engineering challenges rarely faced by other teams.

8/ A quick look back at our journey:

2022: Built an OCAP-enabled bytecode interpreter + the Tolang compiler
2023: Implemented the tuplespace virtual machine (TVM) with replayability
2024: Built the EVM sandbox on TVM, implemented the Block Merge algorithm, and developed BlockGit
2025: Introduced behavior channel types + completed key components required for atomic long-TX support

9/ Even as the industry cools again, our vision is clearer than ever:

Make all forms of state transitions possible in centralized systems equally possible in decentralized ones.

A real world computer as a unified logical VM—composed of many smaller VMs across sharded chains, L2s, private clouds, and browsers.

10/ Smart contracts on this unified VM can call one another seamlessly and finalize atomically—even across different sub-VMs.

The OCAP-enabled VM ensures these interactions remain safe and controlled.

Atomic on-chain long-TX support is the first critical technology we must deliver—and we’re very close.

-----------------

As we enter 2026, thank you for building with us!

Stay tuned! 👉🏻 https://t.co/Ta7xA4GpyX

#Web3 #Concurrent #Composite #Blockchain $ALUX

[D B F @DakeBlueForest]

@alux_network Does this mean that the demo is about to be released?

[ALUX @alux_network]

🧑‍🏭 In Q2 2025, we completed a critical enhancement to our TupleSpace Virtual Machine (TVM): the introduction of simple behavioral channel types. The TVM bytecode standard now enforces three channel types—Single-Owner, Affine, and Linear—enabling significantly faster execution and a much smaller replay log, all while maintaining replay consistency.

🦿 Our Weaklink feature in BlockGit has also passed full testing. Unique to ALUX’s protocol, Weaklink decouples a block’s two roles: contributing to consensus state and to virtual machine state. This separation is vital to achieving ALUX’s vision of supporting on-chain long transactions and atomic cross-shard transactions.

🤖 As we integrate all modules toward a working demo, we have introduced a more advanced test framework. Using Rust’s proptest crate, we built a system that generates millions of random Tolang programs to test TVM execution under various concurrent schedules. Each test ensures state consistency between play and replay across hundreds of execution paths.

🫶 Looking ahead to Q3, we remain focused on delivering a demo showcasing a blockchain capable of processing long-running transactions on-chain. Stay tuned! 👉🏻 https://t.co/Ta7xA4GpyX

#Web3 #Concurrent #Composite #Blockchain $ALUX

[D B F @DakeBlueForest]

@alux_network

[ALUX @alux_network]

As part of a recent upgrade to our TupleSpace Virtual Machine (TVM), ALUX has introduced new behavioral channel types to enhance performance and predictability:

※ Single-Owner: A name (channel) is exclusively owned by one process at any time.
※ Affine: A name may be used at most once.
※ Linear: A name must be used exactly once.

These constraints are enforced at runtime by our bytecode VM, enabling more efficient execution paths.

Why it matters: ALUX is building a Pi/Rho calculus-based VM designed for composable, long-running concurrent transactions on-chain. To scale without compromising performance, we’ve introduced a class of channel types that unlock key optimizations.

For example, Single-Owner channels support lock-free access and can be used to hold sequential VM sandboxes like the EVM. Affine and Linear channels ensure deterministic usage, reducing the overhead of recording extra information for validator replay.

This is where formal theory meets practical engineering—ALUX brings it to life.

$ALUX #Web3 #Blockchain #Concurrent #EVM

[D B F @DakeBlueForest]

@hebi555 有一说一，币安打新币无脑空稳赢，可惜大多不让开

[Atticbee @atticbeeus]

@gakonst "blockchains are just decentralized record keepers." - it's only the current state of art. But more general state machines capable of executing concurrent long running txs need to be supported by blockchains. The benefit would be enormous. We are retrofitting EVM to achieve this

[Atticbee @atticbeeus]

@gakonst In addition, blockchain state should be better compartmentalized with built in object capabilities support, which is also missing in EVM. So we designed a VM with opcode level support of OCAP. EVM instances can run concurrently(not parallely) in our OCAP compliant VM's sandboxes.

[Atticbee @atticbeeus]

@gakonst The very reason current L1 chains can only support record keeping type of job is all TXs must be (atomically) finished in one block. Huge restriction. Chains can't do async calls to external systems and await for the result. Shards can not be virtualized into one logic VM.

[D B F @DakeBlueForest]

@alux_network Indeed, a new project is now needed to advance the technology.

[ALUX @alux_network]

The evolution of the Ethereum Virtual Machine (EVM) can be understood across four distinct levels:

Level 1: Sequential EVM (e.g., Ethereum)
* Transactions are processed sequentially, one after another.

Level 2: Parallel EVM (e.g., Sei, Aptos, Monad)
* Enables parallel transaction processing for improved throughput.
* Limitations: Depends on trusted oracles (such as Chainlink) to interact with the external world.

Level 3: Concurrent EVM (ALUX – Single-Shard Stage)
* Supports asynchronous, long-running transactions that can be temporarily suspended and resumed.
* Enables direct, active communication with the external world—without relying on intermediaries.

Level 4: Composable EVM (ALUX – Multi-Shard Stage)
* Allows transactions to run across multiple shards while preserving atomicity.
* Unifies shards into a single, logically cohesive virtual EVM.
* The only approach to achieve horizontal scalability without compromising usability.

$ALUX #Web3 #Blockchain #Concurrent #EVM

[ALUX @alux_network]

🙋‍♂️ In Q1 2025, we upgraded to an event-driven framework, enabling concurrent transaction execution, block production, replay, and consensus.

Our BlockGit protocol is now more stable with Weaklink, a first-of-its-kind feature that decouples consensus state from the VM state.

Next in Q2: full module integration & a demo of on-chain long-running transactions! Stay tuned! 👉🏻 https://t.co/Ta7xA4GpyX

#Web3 #Concurrent #Composite #Blockchain $ALUX

[D B F @DakeBlueForest]

@alux_network Great !

[ALUX @alux_network]

🧑‍🔬 We've just updated our roadmap! In 2024, we made history by integrating EVM with TVM, enabling concurrent on-chain EVM execution for the first time. We also introduced the innovative BlockGit consensus protocol, complete with a tested block-merge algorithm for conflict resolution. In 2025, we’ll take it to the next level—demonstrating a blockchain capable of handling concurrent, long-running EVM transactions. Stay tuned! 👉🏻 https://t.co/Ta7xA4GpyX

#Web3 #Concurrent #Composite #Blockchain $ALUX

[D B F @DakeBlueForest]

@alux_network So, will you release a demo in the fourth quarter?

[ALUX @alux_network]

🛠 ALUX has made significant strides in 2024! In Q3, we've completed key milestones, such as the execution context to support reverts. We also designed and implemented BlockGit, our new consensus protocol, and integrated it with the P2P module.

👨🏻‍💻 In Q4, we're focusing on integrating BlockGit into the node platform, testing consensus on AWS, and showcasing the capabilities of on-chain concurrent long-running transactions.

👾 We’ve also just released our latest roadmap! Stay tuned for more innovation! 👉 https://t.co/Ta7xA4GpyX

$ALUX #Web3 #Concurrent

[D B F @DakeBlueForest]

RT @alux_network: Unleash Blockchain’s True Potential with Concurrent Long Transactions! @alux_network $ALUX #Concurrent #Web3 #Blockchain…

[ALUX @alux_network]

Concurrency is about dealing with lots of things at once. Parallelism is about doing lots of things at once. #technology #parallelism #concurrency