Files
chains/relayvm/feegate.go
T
zeekay a93f6e3dec build the VMs without the daemon in their closure
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.
2026-09-03 21:10:40 -07:00

23 lines
1.1 KiB
Go

// Copyright (C) 2019-2026, Lux Industries Inc. All rights reserved.
// See the file LICENSE for licensing terms.
package relayvm
// FeePolicy lives at the canonical impl in luxfi/relay/vm. This package
// is a thin re-export shim (see relayvm.go header); the gate is wired
// there and re-exported via the type alias `VM = relayvm.VM`, so any
// caller that constructs a VM through this shim transitively gets the
// NoUserTxPolicy{} declared in ~/work/lux/relay/vm/feegate.go.
//
// The policy value this shim hands back is the one luxfi/relay constructs, and
// luxfi/relay v1.1.1 still builds it from the node's fee package. So the test
// beside this file asserts against that package and not against
// github.com/luxfi/chains/fee: the two declare the same shape under the same
// name, but they are different types, and a test may only claim the type the
// value actually has. R-Chain reaches a node-free closure when luxfi/relay
// programs against the chains fee surface; nothing in this repo can move it.
//
// See:
// - relayvm.go: re-export shim
// - luxfi/relay/vm: canonical NoUserTxPolicy