mirror of https://github.com/luxfi/node.git synced 2026-10-30 15:24:05 +00:00

Files

T

History

zeekay 7cf87b230b node-unified is the node

The module already called itself github.com/luxfi/node while containing no node
in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and
the Go column of the matrix measured a VM plugin. A repo that fetches the thing
it claims to be has not replaced it, so the Go sources move in — 1515 files,
the daemon and everything under it — and the build reaches outside this module
for nothing.

Rust and C++ sit beside it unchanged and are still measured against it by the
differential. That is the point of one repo: the reference implementation and
the two ports are the same checkout, so parity is a thing you can run rather
than a thing you assert.

Verified: builds, and the closure carries no lux-private — checked at build time
rather than believed. The daemon starts twelve chains on a local network
(P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.

2026-09-07 16:15:25 -07:00

subprocess

node-unified is the node

2026-09-07 16:15:25 -07:00

manager.go

node-unified is the node

2026-09-07 16:15:25 -07:00

README.md

node-unified is the node

2026-09-07 16:15:25 -07:00

runtime.go

node-unified is the node

2026-09-07 16:15:25 -07:00

README.md

Virtual Machine Runtime Engine (VMRE)

The VMRE handles the lifecycle, compatibility and logging IO of a managed VM process.

How it works

The runtime.Initializer interface could be implemented to manage local or remote VM processes. This implementation is consumed by a gRPC server which serves the Runtime service. The server interacts with the underlying process and allows for the VM binary to communicate with Lux Node.

Subprocess VM management

The subprocess is currently the only supported Runtime implementation. It works by starting the VM's as a subprocess of Lux Node by os.Exec.

Workflow

VMRegistry calls the RPC Chain VM Factory.
Factory Starts an instance of a VMRE server that consumes a runtime.Initializer interface implementation.
The address of this server is passed as a ENV variable VM_RUNTIME_ENGINE_ADDR via os.Exec which starts the VM binary.
The VM uses the address of the VMRE server to create a client.
Client sends a Initialize RPC informing the server of the Protocol Version and future Address of the RPC Chain VM server allowing it to perform a validation Handshake.
After the Handshake is complete the RPC Chain VM server is started which serves the ChainVM implementation.
The connection details for the RPC Chain VM server are now used to create an RPC Chain VM client.
ChainManager uses this VM client to bootstrap the chain powered by Linear consensus.
To shutdown the VM runtime.Stop() sends a SIGTERM signal to the VM process.

Debugging

Process Not Found

When runtime is Bootstrapped handshake success is observed during the Initialize RPC. Process not found means that the runtime Client in the VM binary could not communicate with the runtime Server on Lux Node. This could be the result of networking issues or other error in Serve().

failed to register VM {"vmID": "tGas3T58KzdjcJ2iKSyiYsWiqYctRXaPTqBCA11BqEkNg8kPc", "error": "handshake failed: timeout"}

Protocol Version Mismatch

To ensure RPC compatibility the protocol version of Lux Node must match the chain VM. To correct this error update the chain VM's dependencies to the latest version Lux Node.

failed to register VM {"vmID": "tGas3T58KzdjcJ2iKSyiYsWiqYctRXaPTqBCA11BqEkNg8kPc", "error": "handshake failed: protocol version mismatch node: 19 vm: 18"}