mirror of
https://github.com/luxfi/chains.git
synced 2026-09-24 00:26:00 +00:00
zeekayandHanzo Dev
f24ec103d2
verifyTransaction checks each nullifier against nullifierDB, which only holds nullifiers spent in ACCEPTED state; a block's own nullifiers are marked spent in Accept, after Verify. So two transactions in one block sharing a nullifier both passed — neither was spent yet — and one shielded note funded two spends, each creating outputs. Supply inflation, which is the exact event the nullifier set exists to prevent. A single transaction listing the same nullifier twice got through the same way: the mempool consults its conflict map before inserting the transaction's own nullifiers, so [n, n] passes admission too. Proven: Vertex.Verify on a vertex whose two txs share a nullifier returned nil. BuildVertex already refuses to batch conflicting txs (usedNullifiers), so the invariant was intended — it just was not enforced on anything that arrived over the wire, and BuildBlock never had it at all. Block.Verify and Vertex.Verify now require every nullifier in the block to be distinct, checked before proof verification because it is the cheaper gate. Also bounds the vertex decoder's counts by the bytes actually present. parentCount and txCount are attacker-controlled uint32 read straight into make(); the length checks came after the allocation. A 16-byte vertex claiming 2^32-1 parents requested 128 GiB, and a 20-byte one claiming 2^24 txs measurably allocated 671 MB before returning its error — remote unrecoverable out-of-memory from a payload smaller than a UDP header. Tests: TestBlockVerifyRejectsDuplicateNullifier, TestBlockVerifyRejectsNullifierRepeatedInOneTx, TestVertexVerifyRejectsDuplicateNullifier, TestDeserializeVertexBoundsParentCount, TestDeserializeVertexBoundsTxCount. Co-authored-by: Hanzo Dev <[email protected]>
Lux Chains
Independent VM plugin binaries for the Lux Network.
Each directory builds to a standalone binary that the Lux node loads as a plugin via --plugin-dir.
Build
make # build all VMs
make evm # build one VM
make test # test all
Install
lpm install evm
lpm install dexvm
Or copy binaries to ~/.lux/plugins/<vmid>.
VMs
One row per directory in this repo. make derives its target list from the
directory listing, so a VM that has no directory here has no binary — the table
below and ls can never disagree.
Live means the VM has a chain registered on Lux mainnet 96369
(platform.getBlockchains).
| VM | Chain | Live on 96369 | Purpose |
|---|---|---|---|
| evm | C-Chain | ✅ | EVM smart contracts |
| dexvm | D-Chain | ✅ | Decentralized exchange |
| aivm | A-Chain | ✅ | AI/ML inference |
| bridgevm | B-Chain | ✅ | Cross-chain bridge — also owns all cross-chain messaging / relay / teleport (LP-6000); there is no separate teleportvm |
| graphvm | G-Chain | ✅ | GraphQL data layer |
| keyvm | K-Chain | ✅ | Key management |
| quantumvm | Q-Chain | ✅ | Post-quantum consensus signing (Pulsar) |
| zkvm | Z-Chain | ✅ | Groth16 over BLS12-381 (rolls N × ML-DSA-65 sigs into 192-byte proof) |
| identityvm | I-Chain | ❌ built, not deployed | Decentralized identity |
| oraclevm | O-Chain | ❌ built, not deployed | Oracle/off-chain data |
| relayvm | R-Chain | ❌ built, not deployed | Cross-chain relay |
| mpcvm | M-Chain | ❌ built, not deployed | MPC ceremonies (CGGMP21, FROST, Pulsar-general) — bridge custody for external wallets (LP-7100) |
| schain | S-Chain | ❌ built, not deployed | S3-style object storage (on-chain metadata / off-chain blob). Declares its own VMID = ids.ID{'s','c','h','a','i','n'} in schain/factory.go and is not in the canonical luxfi/constants VM-ID registry |
P-Chain (platformvm) and X-Chain (xvm) are in-process core VMs registered by
luxfi/node, not plugins built here. Together with the eight ✅ rows above they
are the ten chains live on 96369.
Not in this repo
| Name | Status |
|---|---|
teleportvm / T-Chain |
Removed. LP-134 dissolves T-Chain with zero remainder: threshold signing → M-Chain, FHE → F-Chain, cross-chain messaging/teleport → B-Chain (bridgevm). LP-5013 and LP-7330 are deprecated by LP-134; see LP-7050 for the migration map. No teleportvm VM ID exists in luxfi/constants. |
servicenodevm |
Never existed. The service-node registry was never built under this name; the S-Chain directory here is schain/ and is object storage, not a registry. |
fhevm / F-Chain |
Unbuilt. luxfi/constants reserves FHEVMID = {'f','h','e','v','m'} and luxfi/node/node/vms.go lists it in OptionalVMs as a plugin named fhevm, so luxd will scan --plugin-dir for it — but there is no fhevm/ directory in this repo and no plugin binary anywhere, so that scan always comes up empty. The FHE runtime library lives at mpcvm/fhe/; it is a package inside mpcvm, not a standalone chain. F-Chain is a spec (LP-8200, LP-167) with no shipping VM. |