Files
chains/quantumvm/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

34 lines
1.2 KiB
Go

// Copyright (C) 2019-2025, Lux Industries Inc. All rights reserved.
// See the file LICENSE for licensing terms.
package quantumvm
import (
"fmt"
"github.com/luxfi/chains/fee"
"github.com/luxfi/ids"
)
// Per LP-0130 §6, Q-Chain has NO user-payable blockspace: finality-cert
// inclusion is a validator obligation paid via P-Chain reward distribution,
// never a user fee. A fee market on Q would make finality hostage to
// blockspace pricing (the exact failure mode LP-0130 §6 eliminates), so the
// policy is the explicit committee-only sentinel.
// IssueTx is the user-tx admission point on Q-Chain, and it admits nothing.
// Under NoUserTxPolicy every amount is refused (LP-0130 §6), so there is no
// path from here into the pool — Q-Chain state advances only through
// consensus-internal cert aggregation, which reaches txPool.AddTransaction
// directly and never passes this way.
func (vm *VM) IssueTx(tx Transaction) error {
if vm.feePolicy == nil {
return fmt.Errorf("quantumvm: fee policy not initialized")
}
return vm.feePolicy.ValidateFee(tx.Fee(), ids.Empty)
}
// FeePolicy exposes the chain's declared fee policy for diagnostics
// and the boot-time Validate gate.
func (vm *VM) FeePolicy() fee.Policy { return vm.feePolicy }