Repository navigation
Status
This page states the current status of Paxeer X Network, what the repository contains today, and where releases and specifications live.
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.
The source repository holds both execution domains and their developer surfaces:
| Path | Contents |
|---|---|
src/, include/, cmd/
|
LayerX kernel runtime (C17) and its daemons and tools: layerxd, layerxctl, genesis, verify |
go.mod, chain.mk, daemon/, node/, modules/, consensus/, rpc/, storage/
|
Paxeer X chain node (paxd, Go) |
precompiles/ |
EVM precompiles that join the two domains |
agent/ |
Agent interface: SDK, layerx-agentd, layerx-mcp
|
human/ |
Human control plane and web application |
platform/ |
Developer platform, hosted services, SDKs, CLI, and release tooling |
programs/, interop/, contracts/
|
Programs runtime, interoperability surfaces, and Solidity contracts |
tests/, test/, fuzz/
|
Native, contract, replay, invariant, fault, and fuzz suites |
The full layout is on Developers. The code is licensed under the Apache License, Version 2.0 (LICENSE, NOTICE).
Release tags follow the patterns in docs/MONOREPO.md: vX.Y.Z for the kernel and its workspaces, built with the root Makefile, and paxeer-network/vX.Y.Z for the chain node. No release has been tagged under either pattern yet. CHANGELOG.md records changes under Unreleased.
Normative behavior is specified in KVX under spec/; the generated Markdown next to each source is a reading aid. Qualification gates and evidence levels are in docs/QUALIFICATION.md. A local pass is not authorization to deploy contracts, move custody, or handle real assets.
For reproducible build failures and non-sensitive defects, open a GitHub issue as described in SUPPORT.md. Report suspected vulnerabilities only through the private process in SECURITY.md; see Security.