Documentation
¶
Overview ¶
What this binary can execute with: the C++ library's ABI, the backends it offers, and what each answered to the health battery.
There is nothing to select. Choosing an EVM is choosing which plugin binary the host runs, not a switch inside the Go EVM, so this only says what came up. The cevm package carries its own build tags, so one file serves every build: without the native library linked it reports the one backend it has.
Command evm serves the C-Chain EVM to a Lux node, with every precompile linked in.
Every precompile is explicitly imported. No umbrella packages. Genesis determines which are active at which block/timestamp.
The binary's FILENAME must be the CB58 of constants.ContractVMID (mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6) — that is how the node's plugin registry resolves a vmID from a CreateChainTx to an implementation. A binary installed under any other name is invisible and the chain silently never starts, which is why `version` prints the id it must be installed as: the fact an operator needs is in the place an operator already looks.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package cevm provides Go bindings to the C++ EVM (cevm) with GPU acceleration.
|
Package cevm provides Go bindings to the C++ EVM (cevm) with GPU acceleration. |
|
parallel
Package parallel — cevm BlockExecutor for github.com/luxfi/evm.
|
Package parallel — cevm BlockExecutor for github.com/luxfi/evm. |