mirror of
https://github.com/luxfi/chains.git
synced 2026-09-24 00:26:00 +00:00
zeekay
a93f6e3dec
A plugin is its own binary; the daemon that loads it has no business being linked into it. Twelve VMs reached into github.com/luxfi/node for four things, and each one now programs against a home that is actually its own: - fee admission (Policy, FlatPolicy, NoUserTxPolicy, Validate) joins the settlement half already in chains/fee. One fee package, and the nodefee alias that marked the split is gone. - the cross-chain artifact types move to chains/artifacts. - the factory the daemon registers is luxfi/vm/manager.Factory, and the version types are luxfi/version. Both are ordinary modules the daemon reads too, so a VM imports them directly rather than through anything of ours. The GPU switch is deleted, not moved. It was a global set during daemon startup that a separate process could never observe, so every plugin read its default; FHEOptions.Backend is the switch that was really there. go list -deps names no luxfi/node for aivm, bridgevm, dexvm, evm, fhevm, graphvm, identityvm, keyvm, mpcvm, quantumvm, schain or zkvm, and the built plugin binaries carry no such string. oraclevm and relayvm still do: they are re-export shims over luxfi/oracle and luxfi/relay, which build their fee policies upstream. Their tests keep naming the daemon's fee package because that is the type their value has.
34 lines
1.1 KiB
Go
34 lines
1.1 KiB
Go
// Copyright (C) 2019-2026, Lux Industries Inc. All rights reserved.
|
|
// See the file LICENSE for licensing terms.
|
|
|
|
package keyvm
|
|
|
|
import (
|
|
"github.com/luxfi/ids"
|
|
"github.com/luxfi/log"
|
|
"github.com/luxfi/vm/manager"
|
|
)
|
|
|
|
var _ manager.Factory = (*Factory)(nil)
|
|
|
|
// VMID is the K-Chain VM identifier (matches constants.KeyVMID).
|
|
var VMID = ids.ID{'k', 'e', 'y', 'v', 'm'}
|
|
|
|
// Factory builds K-Chain VM instances. Unlike the prior design it allocates no
|
|
// GPU/accel session: an auth-only VM performs no key generation or batch
|
|
// cryptography on its hot path, so there is nothing to accelerate and one fewer
|
|
// failure mode / native dependency.
|
|
type Factory struct {
|
|
Config
|
|
}
|
|
|
|
// New constructs a VM. It is dependency-free (like the Q/Z core factories), so
|
|
// it can be registered either as a plugin (cmd/plugin) or, once the hardened
|
|
// chains module is the one the node pins, in-process.
|
|
func (f *Factory) New(logger log.Logger) (interface{}, error) {
|
|
return &VM{networkID: f.NetworkID, log: logger}, nil
|
|
}
|
|
|
|
// NewFactory builds a factory with the given configuration.
|
|
func NewFactory(cfg Config) *Factory { return &Factory{Config: cfg} }
|