# AI use cases for Paxeer Monorepo (Sidiora-Labs/paxeer-monorepo) Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Use cases: 5 | Page: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/ Paxeer X Network is a monorepo holding the paxd Go chain node, the C17 LayerX kernel for agent accounting, on-chain contracts, off-chain services, SDKs and apps. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build and test the paxd chain node from source: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/build-and-test-paxd-node/ - Build the LayerX kernel daemon and operator CLI: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/build-layerx-kernel-and-cli/ - Point a wallet or script at Paxeer X chain 125: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/connect-client-to-chain-125/ - Install agent MCP and A2A transports with layerx: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/install-agent-mcp-and-a2a-transports/ - Plan and check a monorepo change against kvx specs: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/plan-monorepo-change-with-kvx-specs/ ## How to build and test the paxd chain node from source with Paxeer Monorepo Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Compile the Go Paxeer X node and run its test and lint targets from the repo root. **Who it is for:** A Go developer or protocol contributor who wants to run or change the Paxeer X chain node (paxd). **The problem:** Running a chain node locally requires a correct toolchain and a repeatable build, and changes need tests and lint before review. **The outcome:** A built build/paxd binary plus a passing node test and lint run. ### Steps 1. Install Go 1.25.6, the version set in go.mod. 2. Run `make paxeer-build` from the repository root to produce build/paxd. 3. Run `make paxeer-test` to run the node Go tests. 4. Run `make paxeer-lint` to run node lint. 5. Read `docs/wiki/Getting-Started-Beta.md` for the public endpoint checklist before connecting to a network. ### Prompt to paste into your agent ```text In the Sidiora-Labs/paxeer-monorepo repository, run `make paxeer-build` and then `make paxeer-test`, using the Go version from go.mod. Report whether build/paxd was produced and which tests failed, if any. Verify that the build target output path is build/paxd before reporting success. ``` ### Caveat The README says the limited beta has not opened yet, and a local pass is not authorization to deploy contracts, move custody, or handle real assets. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/build-and-test-paxd-node/ ## How to build the LayerX kernel daemon and operator CLI with Paxeer Monorepo Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Build layerxd and layerxctl from source and run the kernel test suite. **Who it is for:** A C developer or operator who needs the deterministic LayerX kernel that executes and accounts for agent activity. **The problem:** Agent activity needs a deterministic execution and accounting domain, and the kernel must build and pass its tests before anyone relies on its signed receipts. **The outcome:** Built layerxd and layerxctl binaries and a passing kernel test run. ### Steps 1. Install a C17 compiler, as named in the root Makefile. 2. Run `make build` from the repository root to build the kernel library. 3. Run `make layerxd` to build the kernel daemon. 4. Run `make layerxctl` to build the operator CLI. 5. Run `make test` to run the kernel test suite. ### Prompt to paste into your agent ```text In the Sidiora-Labs/paxeer-monorepo repository, run `make build`, `make layerxd`, `make layerxctl` and `make test`. Report which binaries were built and the test result. Verify that the test output shows the kernel suite ran, not a skipped target, before reporting success. ``` ### Caveat The README notes that folding the kernel into the chain is specified in a draft spec, so the kernel currently runs as a separate daemon. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/build-layerx-kernel-and-cli/ ## How to point a wallet or script at Paxeer X chain 125 with Paxeer Monorepo Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pick a public JSON-RPC endpoint for chain ID 125 and read the payments quickstart. **Who it is for:** A developer building a client, script or wallet integration that needs to read from the Paxeer X chain. **The problem:** Clients need the correct chain ID and a working public RPC name, and the README warns the gateway API is not open yet. **The outcome:** A client configured with chain ID 125 and a public JSON-RPC endpoint, with the payments path reviewed. ### Steps 1. Open `docs/site/docs/reference/public-rpc.md` and choose one of the listed public JSON-RPC names. 2. In your wallet or client settings, set the chain ID to 125 and the chosen RPC URL. (inferred, check the README) 3. Read `docs/wiki/PublicRpc.md` for the RPC methods. 4. Read `docs/wiki/PaymentsQuickstart.md` for the wallet, funding and payments path. 5. Read `docs/wiki/CommitmentLevels.md` before relying on a transaction as final. ### Prompt to paste into your agent ```text In the Sidiora-Labs/paxeer-monorepo repository, read docs/site/docs/reference/public-rpc.md and list the public JSON-RPC names available for chain ID 125. Report the names and the chain ID. Verify that the chain ID stated in the file is 125 before reporting. ``` ### Caveat The README says there is no faucet for general use and the gateway API is not available until the limited beta opens. Risk, credentials: Wallet keys and funding steps touch real value on a mainnet beta, so keep private keys out of logs, prompts and shared files. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/connect-client-to-chain-125/ ## How to install agent MCP and A2A transports with layerx with Paxeer Monorepo Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Build the agent daemon and MCP server, then install their transports with the developer CLI. **Who it is for:** An agent developer who wants an AI agent to reach LayerX through the MCP server and A2A transport. **The problem:** An agent needs a running agent daemon, an MCP server and a registered transport before it can act through LayerX. **The outcome:** The agent services built, tested and the mcp and a2a transports installed through the layerx CLI. ### Steps 1. Run `make agent-build` from the repository root to build the agent daemon and MCP server. 2. Run `make agent-test` to run the agent tests. 3. Build the developer CLI in `tools/platform/cli` and place it on your PATH. (inferred, check the README) 4. Run `layerx install mcp` to install the MCP transport. 5. Run `layerx install a2a` to install the A2A transport. ### Prompt to paste into your agent ```text In the Sidiora-Labs/paxeer-monorepo repository, run `make agent-build` and `make agent-test`, then run `layerx install mcp` and `layerx install a2a`. Report the build result, test result and both install outcomes. Verify that the install commands completed without error before reporting success. ``` ### Caveat The README names the install commands but does not show the exact build step for the developer CLI, so that step is inferred. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/install-agent-mcp-and-a2a-transports/ ## How to plan and check a monorepo change against kvx specs with Paxeer Monorepo Repo: [Sidiora-Labs/paxeer-monorepo](https://github.com/Sidiora-Labs/paxeer-monorepo) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Read the kvx workflow and feature spec, then run the public audit and layout checks. **Who it is for:** A contributor or agent about to change code in the monorepo who must follow the project's spec and audit rules. **The problem:** Every change must pass the public audit, and features are planned in kvx specs, so changes made without reading them risk rejection. **The outcome:** A change plan tied to a feature spec, with the audit and layout checks run before review. ### Steps 1. Read `spec/workflow.kvx` for the planning workflow. 2. Open the `spec.kvx` for your feature under `spec/` and note its requirements, acceptance criteria and task list. 3. Read `CONTRIBUTING.md` for how to propose and land changes. 4. Run `make public-audit`, which every change must pass. 5. Run `scripts/ci/layout-check.sh` to check the repository layout. ### Prompt to paste into your agent ```text In the Sidiora-Labs/paxeer-monorepo repository, read spec/workflow.kvx and CONTRIBUTING.md, then run `make public-audit` and `scripts/ci/layout-check.sh`. Report the audit and layout results and the spec file that governs the change. Verify that both commands exit successfully before reporting the change as ready. ``` ### Caveat The README says a local pass is not authorization to deploy contracts, move custody, or handle real assets, so audit success does not approve a release. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/sidiora-labs-paxeer-monorepo/plan-monorepo-change-with-kvx-specs/