Kalyx

Docs

The testnet

Chain id 21520. Two genesis validators. A slot is about ten seconds. Eight slots make an epoch. The public window is testnet.kalyx.si: the explorer, a browser wallet, and a faucet. The node’s own RPC stays on the machine that runs the node. It is not a public API.

Three different doors

  1. Look. The explorer reads the chain and shows blocks, accounts, and validators.
  2. Send a transaction. The wallet on the explorer creates a spending account in the browser. The seed stays in that tab. The faucet can pay test coins to a KAL address. Those coins are for trying the chain. They are not money.
  3. Validate. Someone follows the node page: their own synced node, an ML-DSA-87 key signed for fork version 0x10000038, and a deposit of 40,000 KALYX. The browser wallet does not hold that key.

What stays closed

The running chain keeps its id. 21520 does not get edited into a new network.

  1. The engine port and the beacon port that the local validator uses stay on the machine. Those are 8551 and 4000, on 127.0.0.1. The execution RPC on 8545 stays there too. Those are how a machine talks to itself.
  2. A new node needs the public genesis files and the two lines in bootnode.txt. Peer traffic is TCP and UDP 30303, TCP 13000, and UDP 12000. The files that hold signing keys are not part of that set.
  3. Genesis minted 500,000,000 KALYX. The faucet pays from a funded account, with a daily cap, so one visitor cannot empty it.

What you should believe

Believe the node and the explorer. An empty slot has no block. The base fee burns. The tip, if there is one, goes to the proposer. There is no miner.

Do not believe a page that calls this a public mainnet, a finished audit, or a place to put value. The wallet can publish contract bytecode and call a contract. The node’s RPC stays on the machine that runs the node. The agent standard on the agents page is a rule, not a count of running models.