Agents need rails
that leave
receipts.
When an agent changes something that matters, there is a signed record of what it did and what the world looked like afterwards. LayerX is the network that keeps those records, and settles them.
Autonomy without accountability is a liability.
LayerX is a deterministic execution and accounting network for autonomous agents: a Go, C17, and Rust monorepo released under Apache-2.0. An agent that moves value needs what a payment network needs, an order that cannot be rewritten, an outcome that can be reproduced, and a receipt someone else can verify.
Every action leaves a receipt
A state-changing operation does not just happen. It is accepted, ordered, applied, and returned with a signed receipt tied to the resulting state root, so the outcome can be checked later instead of taken on trust.
The log is the authority
The append-only activity log is the record. Database indexes are disposable projections that can be rebuilt by replay, which means a lost index is an inconvenience, not an amnesia event.
The same input gives the same result
Consensus-critical execution excludes floating point, local-clock decisions, and database iteration order. Two honest nodes replaying the same log reach the same state.
Most actions need no chain transaction
An ordinary LayerX action does not require a Paxeer transaction. Settlement happens through periodic checkpoints, so the fast path stays fast.
One way in, one order, one answer.
Every state-changing operation takes the same path through the protocol. That is what makes the receipt mean something.
Signed and canonically encoded
Every state-changing operation enters as a signed, canonically encoded Activity. There is one encoding of an instruction, so two nodes cannot disagree about what was asked.
The actor, and its authority, are verified
The protocol verifies who is acting and whether they are authorized to act, then consumes the account sequence. The same instruction cannot be replayed twice by accident or on purpose.
One global order
The activity is ordered on one global sequence before it is applied. Order is decided once, by the protocol, rather than reconstructed after the fact from timestamps.
A deterministic state transition
Applying the activity changes state by a rule, not by a judgment call. Determinism is what makes the receipt worth anything.
A receipt tied to the state root
Each accepted activity returns a signed receipt bound to the resulting state root. The receipt and the state it produced cannot be separated.
One writer for balances, one place to settle.
402LXP owns the balances
402LXP is the only component allowed to write balances. Balance authority is concentrated in one auditable place instead of spread across every service that touches value.
Checkpoints settle to Paxeer
Periodic checkpoints settle to Paxeer, which holds custody, checkpoint registration, guarantor bonds, challenges, withdrawals, disputes, and emergency exits.
Day-to-day work stays off the chain
Because settlement is batched, an ordinary LayerX action does not require a Paxeer transaction. You get chain-backed finality without paying for it on every keystroke.
The client is not the hard part.
Testnet
A live testnet is running, including an HTTP 402 payment path you can build against.
SDKs
Rust, Python, TypeScript, Go, JVM, .NET, and Swift, so the client is not the hard part.
layerx-mcp
An MCP server exposes the network to agents through the protocol they already use.
layerx-agentd
A daemon for agents that need a standing connection to the network rather than a library call.
Apache-2.0
The Sidiora-Labs/LayerX-Network monorepo is open source in Go, C17, and Rust. Read it, run it, disagree with it in public.
This is the testnet.
LayerX is live as a testnet. It is not mainnet, and we do not describe it as one. The layerx wallet and layerx token CLI, along with the LXT-20 program token interface, are not in the current tree.
What is live
A testnet with the activity path, deterministic execution, checkpoint settlement to Paxeer, an HTTP 402 payment path, seven SDKs, the layerx-mcp server, and layerx-agentd.
What is not in the tree
The layerx wallet and layerx token command-line interface, and the LXT-20 program token interface. Build against what exists, and check the repository before assuming a surface is available.
The code is public. Read the protocol, check the activity path yourself, and decide whether the receipts hold up.
View on GitHubStart with the testnet, read the activity path, and see what a receipt tied to a state root gives you that a log line does not.