A payments network that treats its database as disposable

What it does Paxeer X is a deterministic execution and accounting network for autonomous agents — the README’s “Distributed HyperState Machine” translates to an event-sourced ledger that machines can pay into and run code on. Every state-changing operation arrives as a signed, canonically encoded Activity; the protocol checks the actor’s authority, consumes an account sequence, orders it on one global sequence, and returns a signed receipt tied to the resulting state root. Day-to-day activity runs in the LayerX domain (a C17 kernel), while periodic checkpoints settle to Paxeer, an EVM-compatible chain holding custody, guarantor bonds, challenges, disputes, and emergency exits.

The interesting bit The architecture is event sourcing with conviction: the append-only activity log is the authority, and database indexes are disposable projections you can rebuild by replaying it. Consensus-critical code bans floating point, local clocks, and database iteration order — the unglamorous rules that make replay actually reproduce. And only the 402LXP ledger may write balances; every other module emits validated transfer sets and lets the ledger apply them.

Key highlights

• Receipts verify against the sequencer’s public key, batch ID, and the previous and resulting state roots.
• Ordinary LayerX actions never require a Paxeer transaction — settlement happens at checkpoints, not per operation.
• Programs deploy as WebAssembly into a programmable LayerX runtime.
• SDKs for Rust, Python, TypeScript, Go, JVM, .NET, and Swift, plus an MCP server and A2A transport for agent wiring.
• CI gates include a two-build archive comparison, consensus symbol checks, and sanitizer suites — reproducibility is enforced, not aspirational.

Caveats

• The layerx wallet and layerx token CLI and the LXT-20 token interface aren’t in this tree yet, per the README.
• The project itself warns that a passing local CI run “is not authorization to deploy contracts, move custody, or handle real assets” — this is a beta network.
• Ordering runs on one global sequence through a single sequencer (layerxd); the README doesn’t say how, or whether, that’s decentralized.

Verdict Care if you’re building agent payment rails or want machine-native payments with provable receipts. Wait if you need a finished product — the wallet tooling isn’t there yet and the decentralization story is unwritten.