zeekayandHanzo Dev
bb65ac0922
Under equivocation on a fresh chain, the consensus engine can finalize (via the α-of-K cert / catch-up path) a block that this node verified only as a transient non-canonical sibling — whose state trie was then dereferenced when that sibling was rejected — WITHOUT re-verifying it on the finalize path. The node's head then points at a block whose state root is absent from the trie database, so the next BuildBlock fails 'failed to create new current environment: missing trie node' and the chain wedges. This is the fresh re-genesised testnet/devnet block-2 halt (node v1.32.4 / evm v1.99.52); mainnet is unaffected (its genesis lacks the fresh precompile suite and its mature operation does not equivocate at the tip). Fix: in BlockChain.Accept, if the accepted block's state root is not present, re- execute it on the parent (== last accepted, whose state is present by construction) before it becomes the head. reprocessBlock's ValidateState re-checks the computed root against the header, so a non-deterministic transition surfaces loudly rather than silently. On the common (non-equivocation) path this is a cheap HasState no-op. The WARN log fires ONLY on the commit-gap, so it doubles as confirming instrumentation. Co-authored-by: Hanzo Dev <[email protected]>
Lux EVM
Lux is a network composed of multiple blockchains. Each blockchain is an instance of a Virtual Machine (VM), much like an object in an object-oriented language is an instance of a class. That is, the VM defines the behavior of the blockchain.
Lux EVM is the unified Virtual Machine (VM) that powers both the C-Chain and L1/L2 Subnet EVM chains. This package consolidates the former Coreth (C-Chain) and Subnet EVM codebases into a single implementation.
Note
: The
github.com/luxfi/corethrepository has been deprecated and merged here. See the migration guide below.
This chain implements the Ethereum Virtual Machine and supports Solidity smart contracts as well as most other Ethereum client functionality.
Building
The Subnet EVM runs in a separate process from the main Luxd process and communicates with it over a local ZAP-native connection (LP-186 wire schema, no protobuf, no gRPC).
Luxd Compatibility
[v0.7.0] [email protected] (Protocol Version: 38)
[v0.7.1] [email protected] (Protocol Version: 39)
[v0.7.2] [email protected]/1.13.0-testnet (Protocol Version: 39)
[v0.7.3] [email protected]/1.13.0 (Protocol Version: 39)
[v0.7.4] [email protected] (Protocol Version: 40)
[v0.7.5] [email protected] (Protocol Version: 41)
[v0.7.6] [email protected] (Protocol Version: 42)
[v0.7.7] [email protected] (Protocol Version: 42)
API
The Subnet EVM supports the following API namespaces:
ethpersonaltxpooldebug
Only the eth namespace is enabled by default.
Full documentation for the C-Chain's API can be found here.
Compatibility
The Subnet EVM is compatible with almost all Ethereum tooling, including Remix, Metamask, and Foundry.
C-Chain vs Subnet EVM Mode
This unified EVM package supports both modes:
C-Chain Mode (Primary Network):
- Atomic transactions for cross-chain transfers (X-Chain ↔ C-Chain)
- Shared memory integration
- Primary network consensus
Subnet EVM Mode (L1/L2 Subnets):
- Configurable fees and gas limits in genesis
- Simplified hardfork configuration
- No atomic transactions (cross-chain via Warp messaging)
Migrating from Coreth
If you were using github.com/luxfi/coreth, update your imports:
// Before
import "github.com/luxfi/coreth/core"
// After
import "github.com/luxfi/evm/core"
All coreth functionality is preserved in this package.
Block Format
To support these changes, there have been a number of changes to the EVM block format compared to what exists on the C-Chain and Ethereum. Here we list the changes to the block format as compared to Ethereum.
Block Header
BaseFee: Added by EIP-1559 to represent the base fee of the block (present in Ethereum as of EIP-1559)BlockGasCost: surcharge for producing a block faster than the target rate
Create an EVM Subnet on a Local Network
Clone EVM
First install Go 1.23.9 or later. Follow the instructions here. You can verify by running go version.
Set $GOPATH environment variable properly for Go to look for Go Workspaces. Please read this for details. You can verify by running echo $GOPATH.
As a few software will be installed into $GOPATH/bin, please make sure that $GOPATH/bin is in your $PATH, otherwise, you may get error running the commands below.
Download the evm repository into your $GOPATH:
cd $GOPATH
mkdir -p src/github.com/luxfi
cd src/github.com/luxfi
git clone [email protected]:luxfi/evm.git
cd evm
This will clone and checkout to master branch.
Run Local Network
To run a local network, it is recommended to use the lux-cli to set up an instance of EVM on a local Lux Network.
There are two options when using the Lux-CLI:
- Use an official EVM release: https://docs.lux.network/subnets/build-first-subnet
- Build and deploy a locally built (and optionally modified) version of EVM: https://docs.lux.network/subnets/create-custom-subnet
Releasing
You can refer to the docs/releasing/README.md file for the release process.
Plugin Runtime Env Vars
The EVM plugin reads its rpcchainvm handshake address and transport from the
unprefixed env var names that current luxd (v1.26+) sets: VM_RUNTIME_ENGINE_ADDR
and VM_TRANSPORT. This matches the canonical names defined in
luxfi/vm/rpc/runtime/runtime.go. Earlier builds of this plugin
(via luxfi/vm ≤ v1.1.0) read LUX_VM_RUNTIME_ENGINE_ADDR/LUX_VM_TRANSPORT,
which are no longer recognized.