Skip to content

Developers

Jump to bottom
Sidiora Development Team edited this page Sep 24, 2026 · 5 revisions

Developers

This page covers building Paxeer X Network from source, where the specifications live, how the repository is laid out, and how to contribute.

The limited beta has not opened yet. The gateway API becomes available when it does. This is a mainnet beta on real value, so there is no faucet for general use; approved developers receive test allocations from the team.

Build from source

The LayerX kernel runtime is C17 (-std=c17 in the root Makefile). Agent, human, and platform workspaces use Rust 1.91.1 (rust-toolchain.toml). The kernel's settlement contracts use Solidity 0.8.27 (foundry.toml). Replay qualification also needs GCC 13, Clang 18, Docker, an amd64 musl runner, and an AArch64 cross-compiler plus QEMU; see docs/QUALIFICATION.md.

LayerX kernel, from the repository root:

make build
make test
make test-contracts
make ci

make ci runs public-audit, native tests, a two-build archive comparison, consensus symbol checks, and sanitizer suites. Further qualification targets are make qualify-replay, make qualify-arith, make qualify-faults, and make qualify-fuzz.

Paxeer X chain node (paxd), a Go module at the repository root built through chain.mk:

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

Each workspace has its own pair of targets: make agent-build and make agent-test, make human-build and make human-test, make platform-build and make platform-test, make programs-build and make programs-test, make interop-build and make interop-test. make monorepo-ci runs cross-subsystem checks and does not replace either domain's own gates.

A local pass is not authorization to deploy contracts, move custody, or handle real assets.

Specifications

Protocol behavior is defined by the normative KVX sources under spec/. The generated Markdown next to each source is a reading aid, not the place to start a change.

Path Covers
spec/layerx-protocol/ Kernel protocol: canonical activity, execution, and accounting (design)
spec/402lxp/ 402LXP payments with HTTP 402 offers and signed receipts
spec/layerx-platform/ Developer platform, programs, and interoperability gateway
spec/layerx-beta/ Beta fixes and qualification

Repository layout

Path Purpose
src/, include/ C17 kernel runtime: state machine, storage, sequencing, replay, and settlement integration
cmd/ Kernel daemons and tools (layerxd, layerxctl, genesis, verify)
agent/ Rust agent interface, SDK, daemon, MCP server, encoding, cryptography, and proof verification
human/ Human control plane, typed intent compiler, custody-boundary client, explorer index, and web application
platform/ Developer platform, hosted services, middleware, SDKs, emulator, CLI, and release tooling
programs/ Programs runtime and tooling
interop/ Agent-commerce and cross-network interoperability surfaces
contracts/ Solidity contracts
go.mod, chain.mk, daemon/, node/, modules/, consensus/, sdk/, rpc/, precompiles/, storage/, wasm/, docker/ Paxeer X chain node, EVM/RPC compatibility, storage engines, modules, and precompiles
spec/ Normative KVX specifications
tests/, test/, fuzz/ Native, contract, replay, invariant, fault, and fuzz suites
migrations/ Genesis, migration, reconciliation, and shadow-replay work
docs/ Monorepo notes, qualification, and the in-repository wiki

Build boundaries and release tags are in docs/MONOREPO.md.

SDKs: Rust agent/crates/layerx-sdk, Python agent/sdk/python, TypeScript agent/sdk/typescript, Go platform/sdk/go, JVM platform/sdk/jvm, .NET platform/sdk/dotnet, Swift platform/sdk/swift. The agent daemon is agent/crates/layerx-agentd and the MCP server is agent/crates/layerx-mcp; the CLI in platform/cli installs those transports with layerx install mcp and layerx install a2a.

Contributing

Read CONTRIBUTING.md before opening a pull request. In short:

  • Contributions are licensed under Apache 2.0. Sign off every commit with the Developer Certificate of Origin (git commit -s) and follow CODE_OF_CONDUCT.md.
  • Protocol changes start in spec/: add an explicit requirement and task to the relevant spec.kvx before implementing.
  • Branch from main, keep the change narrow and tied to a requirement or a reproducible defect, complete the pull-request template, and record the exact verification commands you ran and their outcomes.
  • Do not weaken a check or add stub, mock, or fake implementations to make tests pass. Keep 402LXP as the only balance writer.

For help, follow SUPPORT.md: open a GitHub issue with the bug report template for reproducible build failures, protocol conformance questions, and non-sensitive defects. Include the operating system, compiler or Foundry version, exact command, complete error output, and the smallest input that reproduces the problem. Report suspected vulnerabilities only through SECURITY.md; see Security.

Clone this wiki locally