Installation & Build

Build Paxeer X chain nodes, the deterministic LayerX kernel, hosted services, agent tools and Programs from the unified repository.

Source: Paxeer-X-Network/Makefile, chain.mk, and Paxeer-X-Network/README.md

Build the complete network stack

The Paxeer X monorepo contains the Go chain node, the native kernel daemon, Rust service workspaces, SDKs, and program tooling. Select the build family matching the component you operate. The chain binary is paxd; the kernel daemon is layerxd.

Component	Build surface	Purpose
Kernel and genesis tools	`make layerxd layerx-genesis-build`	Deterministic execution daemon and signed genesis builder
Agent services	`make agent-build`	Agent runtime and its service boundaries
Human services	`make human-build`	Human API, providers, owner and security components
Platform services	`make platform-build-all`	Gateway, core boundary, registry, and hosted services
Programs and porting	`make programs-build`	Programs workspace and EVM, Solana, and CosmWasm porting kits

These commands run from the repository root. Use the Rust toolchain and dependency locks declared by each workspace, and the C compiler and native dependencies declared by the kernel build. Program guests target WebAssembly; install the target required by the selected guest before compiling it.

Installation provides binaries and images. Joining a network also requires its signed genesis, network identity, custody and settlement bindings, sequencer authorization, and role-specific credentials. Retain build provenance and artifact checksums with the deployment record. Continue with node startup and operator roles.

Prerequisites

Go: 1.25.6 or the toolchain required by the selected revision
Make: Standard build tool
Git: For cloning the repository
Native toolchain: GCC and the native libraries required by the selected build. Use LEDGER_ENABLED=false to disable the optional Ledger build tag.

Repository Location

Clone the unified Sidiora-Labs/Paxeer-X-Network repository. Chain sources, kernel sources, workspaces, and build configurations share this repository root.

git clone https://github.com/Sidiora-Labs/Paxeer-X-Network.git
cd Paxeer-X-Network

Build the Chain Node

Run these namespaced targets from the repository root. The chain build uses chain.mk; make paxeer-build writes build/paxd.

make paxeer-build
make paxeer-lint
make paxeer-test
make paxeer-ci

The root make build builds the C kernel and native tools, including build/bin/layerxd and build/bin/layerx-genesis-build. Root make test, make ci, and make clean retain their kernel/workspace meaning. Select the chain explicitly:

make -f chain.mk build
make -f chain.mk install
make -f chain.mk test
make -f chain.mk ci

Build Output

build/paxd from make paxeer-build or make -f chain.mk build.
$GOBIN/paxd when GOBIN is set, otherwise $(go env GOPATH)/bin/paxd, from make -f chain.mk install.
make workspace-build combines the declared component build families; make monorepo-ci delegates to the workspace CI target.

Build Tags and Flags

Ledger Support

Ledger hardware wallet support is enabled by default. To build without ledger:

make paxeer-build LEDGER_ENABLED=false

Mock Balances (Testing)

For testing with mock balances:

make -f chain.mk install-mock-balances

Benchmark Build

For benchmark runs:

make -f chain.mk install-bench

Version Information

The Makefile resolves version from Git tags or branch names. The chain version resolver retains its historical namespaced tag pattern:

paxeer-network/vX.Y.Z

Version information is embedded in the binary at build time via linker flags:

Name: paxeer
AppName: paxd
Version: Resolved from tag/branch
Commit: Git commit SHA

Check version:

paxd version

Static Linking

To build a statically-linked binary:

make paxeer-build LINK_STATICALLY=true

Go Module

The repository root declares the chain Go module:

module github.com/Sidiora-Labs/Paxeer-X-Network

go 1.25.6

Note: The root go.mod and go.sum govern the chain Go dependencies. Rust components use their own workspace manifests and lockfiles.

Foundry (Contracts)

Chain contracts under contracts/src/ use foundry.paxeer.toml. Fetch the pinned dependencies and build from the repository root:

bash contracts/bootstrap-libs.sh
FOUNDRY_CONFIG=foundry.paxeer.toml forge build --offline --root .

Kernel custody and settlement contracts also live under contracts/, using repository-root foundry.toml and tests/solidity/. See contracts/README.md and the contracts guide for the two project configurations.

Docker

Local Docker cluster targets are available. See Docker documentation for:

make docker-cluster-start
make run-local-node
Compose configurations in docker/

Choose a Node Configuration

Use the local Docker configuration to try the built binary, or initialize a node with the genesis, peers, and mode for your chosen network. For an existing network, select the binary revision specified by its upgrade plan.

Next Steps

Network Parameters

Run a Node