Files
zeekay 7cf87b230b node-unified is the node
The module already called itself github.com/luxfi/node while containing no node
in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and
the Go column of the matrix measured a VM plugin. A repo that fetches the thing
it claims to be has not replaced it, so the Go sources move in — 1515 files,
the daemon and everything under it — and the build reaches outside this module
for nothing.

Rust and C++ sit beside it unchanged and are still measured against it by the
differential. That is the point of one repo: the reference implementation and
the two ports are the same checkout, so parity is a thing you can run rather
than a thing you assert.

Verified: builds, and the closure carries no lux-private — checked at build time
rather than believed. The daemon starts twelve chains on a local network
(P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.
2026-09-07 16:15:25 -07:00

1.2 KiB

Chains

The Lux Network consists of the Primary Chainwork and a collection of blockchain networks.

Chain Creation

Chains are created by issuing a CreateChainTx. After a CreateChainTx is accepted, a new chain will exist with the ChainID equal to the TxID of the CreateChainTx. The CreateChainTx creates a permissioned chain. The Owner field in CreateChainTx specifies who can modify the state of the chain.

Permissioned Chains

A permissioned chain can be modified by a few different transactions.

  • CreateChainTx
    • Creates a new chain that will be validated by all validators of the chain.
  • AddChainValidatorTx
    • Adds a new validator to the chain with the specified StartTime, EndTime, and Weight.
  • RemoveChainValidatorTx
    • Removes a validator from the chain.
  • TransformChainTx
    • Converts the permissioned chain into a permissionless chain.
    • Specifies all of the staking parameters.
      • LUX is not allowed to be used as a staking token. In general, it is not advisable to have multiple chains using the same staking token.
    • After becoming a permissionless chain, previously added permissioned validators will remain to finish their staking period.
    • No more chains will be able to be added to the chain.