Chain architecture

KriptoNyx is a Cosmos SDK chain with an EVM execution layer, built on an Evmos fork. That combination gives it Tendermint's fast-finality proof-of-stake consensus and full Ethereum tooling compatibility at the same time.

Layers

Layer	Component	Version
Consensus	Tendermint	v0.34.26
Application	Cosmos SDK, Evmos fork	v0.46.10
Execution	go-ethereum, Evmos fork	v1.10.26
Binary	kriptonyxd	—

Tendermint orders transactions and reaches agreement among validators. It is Byzantine fault tolerant and gives instant finality — once a block is committed it cannot be reorganised, unlike chains with probabilistic finality.

The Cosmos SDK application holds the modules: staking, slashing, governance, bank, and the EVM module.

The EVM module executes Solidity contracts exactly as Ethereum does, so opcodes, gas accounting and contract semantics behave as you expect.

Consequences worth knowing

No reorganisations. A committed block is final. You do not need to wait for confirmations in the Ethereum sense — though waiting for the receipt is still how you confirm a transaction succeeded.

Validators, not miners. Blocks are produced by a bonded validator set, capped at 64. Security comes from staked KNYX, and misbehaviour is slashed.

Two address formats, one account. See Accounts and addresses.

Network parameters

Parameter	Value
Maximum validators	64
Unbonding period	1,814,400 s — 21 days
Minimum gas price	0aknyx
Genesis time	2026-04-21T02:05:02Z
Genesis SHA-256	b737d821b535482bb20d6c5e95492c4260e715cccef7ddbd2cdc27d95c52dfdd

The unbonding period matters: stake withdrawn is illiquid for 21 days and remains slashable during it for faults committed earlier.

Node interfaces

A node exposes several interfaces. Only P2P is public by policy; the rest are bound to localhost and reached through a TLS proxy where they are published.

Interface	Port	Exposure
P2P	26656	Public
Tendermint RPC	26657	Localhost
EVM JSON-RPC	8545	Localhost
gRPC / gRPC-web	9090 / 9091	Localhost
Cosmos REST	1317	Disabled by default

See Running a validator for how these are configured on a real node.