Files
Zach Kelling 9513b3697f Import the Rust D-Chain and F-Chain
These were in luxfi/compute, a private repo whose licence is the same
BSD-3-Clause as luxfi/node's. Nothing here needed protecting, and keeping
it private broke the public Rust chain builds that reference it.

Sibling paths lose a level: the chains sat three deep in compute and sit
one deep here. The conformance generator loses a replace naming an
absolute path on one machine, and takes luxfi/chains from the proxy.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-10 21:36:01 -07:00

25 lines
1.0 KiB
TOML

# SPDX-License-Identifier: BSD-3-Clause-Eco
[package]
name = "lux-dexvm"
version = "0.1.0"
edition = "2021"
description = "The Lux D-Chain in Rust: what an asset IS, what a market IS, and under which posture value may activate"
license = "BSD-3-Clause-Eco"
repository = "https://github.com/lux-rs/chains"
publish = false
[dependencies]
# An AssetID and a MarketID are a length-prefixed SHA-256 fold, and those bytes
# are consensus: two implementations folding differently have forked the value
# plane without ever disagreeing about a transaction. One hash, the same one Go
# and C++ fold with.
sha2 = "0.10"
# There is no other dependency, and in particular no `lux-node`. The seam is
# what a chain implements to be run by the node, and Go's `chains/dexvm` has no
# block, no transaction and no VM — it is a registry the C-Chain settlement
# precompile calls in process. A block layer written here would be an opinion
# about a wire no chain writes and nothing could check it: the corpus has no D
# block vector, because there is no D block. See LLM.md.