Every block KAURAX produces is published to the Layer-2 beneath it as calldata. If the sequencer vanished tonight, your transactions would still be there — and you could rebuild them yourself, without asking anyone.
Anyone can claim decentralisation. These are the specific places where KAURAX takes the choice away from its own operators.
Every block is published to the Layer-2 below as calldata before it counts as settled.
The acceptance test rebuilds a signed transaction from that calldata alone and checks its hash — so this is a property under test, not an intention.
If it refuses your transaction, submit it on the L2 instead and start a clock.
Miss the deadline and the output oracle rejects every proposal from that point on. One censored user halts settlement for the whole chain.
Getting funds out needs a Merkle proof against a published state commitment.
No signature, no multisig, no operator discretion. The proof either verifies against the root on the L2 or the withdrawal does not happen.
KAURAX is not a fork of Ethereum and not a frontend in front of one. It is a rollup: it sequences its own blocks, batches them downward, and inherits its security from the layers beneath.
Solidity, Foundry, Hardhat, MetaMask, viem and ethers work unchanged. Change the RPC URL and the chain ID; change nothing else.
Your own gas limit, block time and fee policy — not contended by an unrelated mint three blocks ahead of you.
A PostgreSQL indexer behind the explorer and API, so address history and token transfers are queried, not re-scanned.
JSON-RPC and WebSocket, an SDK, a CLI, an explorer, a bridge, a wallet and a backend API — every one reading live chain state.
Each of these reads live chain state. Nothing here is a mockup.
No SDK to learn and no proprietary client. If it speaks Ethereum JSON-RPC, it already speaks KAURAX.
Network name KAURAX
RPC URL https://kaurax.network/rpc
Chain ID 8420
Currency KAX
# or from a script
cast block-number --rpc-url https://kaurax.network/rpcKAURAX is a testnet. KAX has no monetary value and never will on this network. There are no fault proofs, so output roots are trusted rather than challenged. The sequencer is a single operator. No contract here has been audited.
Everything above describes what the code does today. Where a figure is not known, this site says No data available rather than showing a plausible number.