zeekayandHanzo Dev 65fcbe7f51 Take in the plugin surface twelve VMs reach luxfi/node for ...

Nineteen Go modules require github.com/luxfi/node, and all twelve chain VMs
that touch it at all touch only seven packages: version, vms, vms/artifacts,
vms/types/fee, cache, utils/json, and one function out of config. That is the
plugin-SDK surface a ChainVM needs to declare itself to a host — not
networking, not consensus — and it is the reason luxfi/node cannot be retired
while it is the only place they can get it.

Six of the seven import nothing from luxfi/node and moved unchanged. config
does not: it pulls in benchlist, chains, config/node, genesis/builder, nets
and network, so moving it would have brought the node with it. It also has
exactly two call sites in the whole VM set, both in an fhe_c.go, both calling
GetGlobalGPUConfig — and config/gpu.go is 129 lines that import nothing at
all. It is here as its own package, gpu, so a VM asking what GPU to use does
not thereby depend on how a node parses its flags.

Nothing is deleted from luxfi/node by this commit. The consumers still have to
be repointed, and two things in this repository block verifying that: go.sum
carries a stale hash for a moved luxfi/consensus tag, and registry's own tests
import a luxfi/vm/manager that does not exist. Both predate this change.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-05 23:14:23 -07:00

..

artifacts.go

Take in the plugin surface twelve VMs reach luxfi/node for

2026-09-05 23:14:23 -07:00