Sidiora-Labs/paxeer-monorepo

Table of Contents
## What is Paxeer X Network?
Paxeer X Network is a distributed HyperState Machine for payments, code execution and intent routing, developed by Sidiora Labs. It connects an EVM-compatible chain with a deterministic execution and accounting domain for autonomous agents.
In this repository you’ll find the core components of the network: the Paxeer X chain, the LayerX kernel, on-chain contracts, off-chain services, client SDKs and user-facing applications. Together, they provide the infrastructure for developers to build applications and agents on a shared network.
The network has two execution domains:
Paxeer X chain. paxd is the Go node, with BFT consensus and an EVM execution layer using chain ID 125. The main package is daemon/paxd, with state machine modules in modules/ and RPC servers in rpc/.
LayerX kernel. layerxd is the C17 daemon that executes and accounts for agent activity deterministically, returning a signed receipt for each activity. layerxctl provides the operator CLI, and programs/ contains the kernel programs runtime. The kernel runs as a separate daemon built from cmd/layerxd; its checkpoints settle on the chain through the layerxAnchor precompile.
The monorepo also includes the agent daemon and MCP server, interop gateway and bridge relayer, hosted developer platform, human control plane, embedded wallet service, explorer and launchpad services. Applications include the Hyperpax perps frontend, wallet, web app, explorer and launchpad web and mobile apps.
## Documentation
To build on Paxeer X Network, start with the Paxeer documentation and the developer wiki.
To connect to the chain, see the public JSON-RPC endpoints and beta endpoint checklist.
For wallets, funding and payments, follow the Payments Quickstart.
To run a local kernel cluster, follow the Kernel Quickstart.
For protocol references, see assets, RPC methods, commitment levels and the public payment API.
The limited beta has not opened yet. The gateway API becomes available when it does. The beta runs on mainnet with real value; there is no faucet for general use. Approved developers receive test allocations from the team.
### Client SDKs
| Language | Path |
| Rust | services/agent/crates/layerx-sdk |
| Python | services/agent/sdk/python |
| TypeScript | services/agent/sdk/typescript |
| Go | sdk/platform/go |
| JVM | sdk/platform/jvm |
| .NET | sdk/platform/dotnet |
| Swift | sdk/platform/swift |
The agent daemon is services/agent/crates/layerx-agentd and the MCP server is services/agent/crates/layerx-mcp. The developer CLI in tools/platform/cli installs those transports with layerx install mcp and layerx install a2a.
## Specification
Detailed feature specifications live in spec/. Each feature’s spec.kvx defines its requirements, acceptance criteria and dependency-ordered task list. The specification workflow describes how work is planned and tracked. spec/specgen runs tools/specgen to generate agent instruction files, including CLAUDE.md and AGENTS.md.
The proposed integration of the LayerX kernel into the chain is described in the LayerX merge specification, which remains a draft. The monorepo layout specification describes the target repository structure.