Ethereum smart contracts
The EVM, Solidity, ABIs, JSON-RPC, events and logs behave as they do on
Ethereum. Hardhat, Foundry, ethers and viem work against Kronex by changing
one endpoint and one chain ID.
kHeavyHash proof of work
The standard kHeavyHash pre-image, byte for byte: the same cSHAKE256
passes, the same 64x64 matrix, the same comparison. Any kHeavyHash miner
mines Kronex with no firmware change.
Five algorithms, one chain
kHeavyHash seals Kronex blocks, but it is not the only way to mine them. Kronex is merge-mined against four other proof-of-work networks, so work already being done on those chains can earn Kronex at the same time.
Five algorithm families means five hardware ecosystems, and none of them has to
stop mining what it already mines. See Mining and
Merged mining.
Why it is built this way
A new proof-of-work chain normally has to solve two problems at once: attract developers, and attract hashrate. Most chains solve neither, because a new VM means rewriting your tooling and a new algorithm means new hardware. Kronex takes neither risk. The execution layer is go-ethereum, so the developer ecosystem transfers directly. The proof of work is kHeavyHash, so an existing industry of GPU and ASIC miners can point at Kronex without buying anything. What is new sits between those two: how blocks are timed, how difficulty retargets, and how rewards are shared and released.What that gets you
Where to go next
Networks
Chain IDs, endpoints, and what differs between testnet and mainnet.
Run a node
Build
krnxd, initialize from genesis, expose JSON-RPC.Start mining
Point an existing kHeavyHash miner at a Kronex node.
Deploy a contract
Hardhat and Foundry against Kronex.
Rewards
What a block pays and when those coins unlock.
RPC reference
Generated from the node source, with a live playground.