# AI use cases for Paxeer X Network (Sidiora-Labs/Paxeer-X-Network) Repo: [Sidiora-Labs/Paxeer-X-Network](https://github.com/Sidiora-Labs/Paxeer-X-Network) | Use cases: 4 | Page: https://dedupedai.com/use-cases/sidiora-labs-paxeer-x-network/ Paxeer X Network is a monorepo holding the Paxeer X EVM chain node (paxd, Go) and the LayerX kernel (layerxd, C17), with SDKs, an MCP server and a bridge relayer for agent and payment workloads. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build the LayerX kernel and run its test gate: https://dedupedai.com/use-cases/sidiora-labs-paxeer-x-network/build-layerx-kernel-and-run-tests/ - Build and test the paxd Paxeer X chain node: https://dedupedai.com/use-cases/sidiora-labs-paxeer-x-network/build-and-test-paxeer-chain-node/ - Connect a wallet or app to the Paxeer X chain: https://dedupedai.com/use-cases/sidiora-labs-paxeer-x-network/connect-to-paxeer-x-chain-public-rpc/ - Give an agent LayerX tools through MCP and A2A: https://dedupedai.com/use-cases/sidiora-labs-paxeer-x-network/give-agent-layerx-tools-via-mcp-and-a2a/ ## How to build the LayerX kernel and run its test gate with Paxeer X Network Repo: [Sidiora-Labs/Paxeer-X-Network](https://github.com/Sidiora-Labs/Paxeer-X-Network) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Compile the C17 LayerX kernel and run the local test and CI targets before any change. **Who it is for:** A kernel developer or agent who needs a verified local build of the LayerX kernel before editing src/ or cmd/. **The problem:** Changes to a deterministic execution kernel are hard to trust without a repeatable build and test pass. **The outcome:** A built layerxd binary with kernel tests, contract tests and the full local CI gate reported as passing or failing. ### Steps 1. Clone the repository and change into the repo root. 2. Run `make build` to compile the LayerX kernel. 3. Run `make test` for the kernel tests and `make test-contracts` for the settlement contracts. 4. Run `make ci` to run public-audit, kernel tests, the two-build archive comparison, consensus symbol checks and sanitizer suites. 5. Treat a local pass as a development check only. The README says it is not authorization to deploy contracts, move custody or handle real assets. ### Prompt to paste into your agent ```text Clone Sidiora-Labs/Paxeer-X-Network and run make build, make test and make ci from the repo root. Report which targets passed or failed and the first error from any failure. Verify that no deployment or custody step was run. ``` ### Caveat The README says a local CI pass is not authorization to deploy contracts, move custody or handle real assets, so treat results as build evidence only. Risk, credentials: Do not place deployment keys or custody credentials in the build environment, since the README says a local pass does not authorize deployment. 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-x-network/build-layerx-kernel-and-run-tests/ ## How to build and test the paxd Paxeer X chain node with Paxeer X Network Repo: [Sidiora-Labs/Paxeer-X-Network](https://github.com/Sidiora-Labs/Paxeer-X-Network) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Compile, lint and test the Go Paxeer X chain node (paxd) without changing directories. **Who it is for:** A chain developer or agent working on the Paxeer X chain node, EVM compatibility or chain modules. **The problem:** Chain code spans Go modules, precompiles and consensus, so a repeatable build and lint pass is needed before review. **The outcome:** A built paxd node with lint and test results for the chain subsystem. ### Steps 1. Clone the repository and change into the repo root. 2. Run `make paxeer-build` to build paxd, defined in chain.mk. 3. Run `make paxeer-lint` to lint the chain code. 4. Run `make paxeer-test` to run the chain tests. 5. Run `make paxeer-ci` for the full chain gate before opening a pull request. ### Prompt to paste into your agent ```text In the Sidiora-Labs/Paxeer-X-Network repo, run make paxeer-build, make paxeer-lint and make paxeer-test. Report the result of each target and list any failing test names. Verify that the Go version used is 1.25.6 as set in go.mod. ``` ### Caveat The chain targets come from chain.mk and run only the chain subsystem, so cross-subsystem checks still need make monorepo-ci. 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-x-network/build-and-test-paxeer-chain-node/ ## How to connect a wallet or app to the Paxeer X chain with Paxeer X Network Repo: [Sidiora-Labs/Paxeer-X-Network](https://github.com/Sidiora-Labs/Paxeer-X-Network) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Point a wallet or app at chain ID 125 using a public JSON-RPC name from the reference list. **Who it is for:** A developer or agent that needs to read from the Paxeer X chain during the limited beta. **The problem:** Apps need a correct chain ID and a public RPC name, and the beta has real value with no general faucet. **The outcome:** A connection that reads chain state from the Paxeer X chain over a public JSON-RPC endpoint. ### Steps 1. Read the Getting Started checklist in docs/wiki/Getting-Started-Beta.md. 2. Open docs/site/docs/reference/public-rpc.md and pick one listed public JSON-RPC name. 3. Set your wallet or app to chain ID 125 with that endpoint. 4. Read docs/wiki/PublicRpc.md to see which RPC methods are available and docs/wiki/CommitmentLevels.md for commitment levels. 5. Check docs/wiki/PaymentsQuickstart.md before any funding or payment step. ### Prompt to paste into your agent ```text In the Sidiora-Labs/Paxeer-X-Network repo, read docs/site/docs/reference/public-rpc.md and select one public JSON-RPC name for chain ID 125. Report the endpoint name and the first two RPC methods listed in docs/wiki/PublicRpc.md. Verify that the chain ID you report is 125. ``` ### Caveat The limited beta has not opened and there is no faucet for general use, so approved developers must get test allocations from the team. Risk, credentials: Keep wallet keys off shared machines, since the README states this is a mainnet beta on real value. 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-x-network/connect-to-paxeer-x-chain-public-rpc/ ## How to give an agent LayerX tools through MCP and A2A with Paxeer X Network Repo: [Sidiora-Labs/Paxeer-X-Network](https://github.com/Sidiora-Labs/Paxeer-X-Network) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Install the MCP and A2A transports from the developer CLI so an agent can call LayerX tools. **Who it is for:** A developer whose AI agent needs to call LayerX tools through the MCP server or the A2A transport. **The problem:** Agents need a supported transport to reach the LayerX agent daemon, and setup should not need hand-wired configuration. **The outcome:** An MCP server and A2A transport installed for the agent, pointing at layerx-agentd. ### Steps 1. Build or obtain the developer CLI from tools/platform/cli. (inferred, check the README) 2. Run `layerx install mcp` to install the MCP transport. 3. Run `layerx install a2a` to install the A2A transport. 4. Confirm the MCP server source at services/agent/crates/layerx-mcp and the daemon at services/agent/crates/layerx-agentd. 5. Connect your agent to the MCP server and send one tool call through layerx-agentd. ### Prompt to paste into your agent ```text In the Sidiora-Labs/Paxeer-X-Network repo, locate the MCP server at services/agent/crates/layerx-mcp and the daemon at services/agent/crates/layerx-agentd. Run layerx install mcp and layerx install a2a, then report which transports were installed. Verify that layerx-agentd is reachable before reporting success. ``` ### Caveat The README names the install commands but not the CLI build steps, so confirm how the layerx CLI is obtained before relying on these commands. Risk, remote script: Review the installer and the CLI source before running the install commands, since they set up agent transports on your machine. 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-x-network/give-agent-layerx-tools-via-mcp-and-a2a/