Credentials. Do not place deployment keys or custody credentials in the build environment, since the README says a local pass does not authorize deployment.
Who it is forA kernel developer or agent who needs a verified local build of the LayerX kernel before editing src/ or cmd/.
The problemChanges to a deterministic execution kernel are hard to trust without a repeatable build and test pass.
The outcomeA built layerxd binary with kernel tests, contract tests and the full local CI gate reported as passing or failing.
What you need first
- Git access to the Sidiora-Labs/Paxeer-X-Network repository
- Go 1.25.6 for the Paxeer X chain node (go.mod)
- A C17 toolchain for the LayerX kernel (-std=c17 in the root Makefile)
- Rust 1.91.1 for the agent workspaces (rust-toolchain.toml)
- A wallet that targets chain ID 125 for any public JSON-RPC use
Steps
- Clone the repository and change into the repo root.
- Run
make buildto compile the LayerX kernel. - Run
make testfor the kernel tests andmake test-contractsfor the settlement contracts. - Run
make cito run public-audit, kernel tests, the two-build archive comparison, consensus symbol checks and sanitizer suites. - 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 for your agent
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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page