zeekayandHanzo Dev
b00f4bfea2
chains/cpp/core and quantumvm asked for LUX_GPU_DIR and stopped with a fatal error when nothing set it, so the public P, X and Q builds could not configure at all for anyone outside this machine. The seam is an ABI of four symbols over a complete CPU backend, not a kernel, so it belongs beside the chains defined over it; the kernels stay private in lux-gpu/gpu and are still only ever dlopen'd. The D and F ports move with it, to lux-cpp/chains and lux-rs/chains, both public. luxfi/compute held nothing its licence did not already cover, being the same BSD-3-Clause as this repository's. Co-authored-by: Hanzo Dev <[email protected]>
3.1 KiB
chains/cpp — the chain suite, in C++
Ported from ~/work/lux/node/vms/* into ~/work/lux-cpp/node's VM seam
(include/lux/node/vm.hpp). runtime/cpp already runs a C-Chain today via
cevm (see its README); this is the rest of the suite, behind the same seam.
| chain | here | state |
|---|---|---|
| P — the platform chain | platformvm/ |
ported; see its LLM.md |
| X — the UTXO DAG | xvm/ |
ported; see its LLM.md |
| Q — the quantum chain | quantumvm/ |
ported; see its LLM.md |
| Z — the shielded chain | zkvm/ |
ported; see its LLM.md |
| D — the DEX admission layer | dexvm/ |
ported; see its LLM.md |
| F — confidential compute | fhevm/ |
ported; see its LLM.md |
Every one of them answers the shared corpus. test/conformance.cpp in each
chain reads conformance/corpus/vectors.tsv and prints that chain's verdicts;
make chains compares them against Go's and against Rust's. They are built
whether or not tests are, because a differential that quietly lost one of its
voices would report agreement among whoever was left.
conformance/ holds what those six evaluators share — the corpus format, the
verdict words and the error-word table. It lives once because a table that
differed between two of them reported its own difference as a chain's.
The wire
There is ONE ZAP implementation here and it is not here: zap.cmake pins the
published zap-proto/cpp and every chain links zap::zap. The four in-tree
copies are gone. A chain that carries its own copy of the wire is a chain that
can drift from it, which is what had happened.
What sits on top of that runtime — the offsets, the strides, the readers and
the builders — is generated, one chain at a time, from a .zap schema beside
the chain. zapgen prints the header; what is left beside it holds only what
the bytes MEAN.
Three chains read their wire out of a schema: xvm, quantumvm, and
platformvm, whose four schemas cover every shape the P-chain puts on a wire
or in a store — nineteen transactions, three blocks, the credentials, the two
fx envelopes an output is ordered by, the genesis blob, and the warp messages
an L1 and the P-chain say to each other.
Three still state their offsets by hand, and are named here rather than left
to be discovered: zkvm (1,452 lines), fhevm (913), dexvm (585).
platformvm
The validator set, the staking rules that admit and pay it, and the blocks that change it. A node joins by staking: no allowlist, no admin key, no argument anywhere in the tree to pass one.
cd platformvm && cmake -S . -B build && cmake --build build -j && (cd build && ctest)
It finds lux-cpp/blst, lux-private/crypto, lux-cpp/node and lux-cpp/consensus
where they actually sit, matching on a file rather than a directory name. All
four are required: a build that cannot check a proof of possession or recover a
signer does not produce a P-chain at all.
platformvm/LLM.md says what is ported, what is absent, and why — including the
one subsystem (L1 validators, which rest on warp) whose transaction wire is
byte-identical but whose execution is not here.