Skip to content

Releases: kronexnetwork/kronex

Release list

krnxd v1.0.1-testnet.1 (testnet reset)

krnxd v1.0.1-testnet.1 (testnet reset) Pre-release
Pre-release

Choose a tag to compare

View all tags
@kronexnetwork kronexnetwork released this 01 Nov 13:03
v1.0.1-testnet.1
68b0f69

krnxd 1.0.1 for the Kronex testnet (chain ID 5768). Mainnet has not launched.

Testnet reset: resync required

This release ships a new testnet genesis. The testnet has been reset, and every node has to drop its old chain data and sync again from scratch.

Genesis hash
New (1.0.1) 0x897b8851ffa4c494cd51c803273245172a90d18d313cb0578cc85e5402984101
Old (1.0.0) 0x5a114fcc6da436a92cf7bc65fbfa8faeb33c45b45f9f3b14b365d8129a5cba7b

A 1.0.0 node stays on the old chain and no longer finds peers; a 1.0.1 binary refuses to start on an old data directory because the stored genesis does not match. To move over:

  1. Stop krnxd.

  2. Delete the old chain database. Your keystore and node key are kept:

    krnxd --testnet removedb

    Answer y to each prompt. With an explicit data directory, add the same --datadir you run the node with. Also delete transactions.rlp in the same directory (~/.kronex/testnet/krnxd/ by default): it holds pending transactions from the old chain, and the node would otherwise rebroadcast them on the new one.

  3. Replace the binary with 1.0.1 and start the node again with your usual flags. It syncs the new chain from genesis.

With Docker, pull the new image and run removedb against the same volume before restarting the container:

docker pull ghcr.io/kronexnetwork/krnxd:testnet
docker run --rm -it -v krnxd-data:/root/.kronex ghcr.io/kronexnetwork/krnxd:testnet --testnet removedb
docker run --rm -v krnxd-data:/root/.kronex --entrypoint rm ghcr.io/kronexnetwork/krnxd:testnet -f /root/.kronex/testnet/krnxd/transactions.rlp

Balances, contracts and rewards from the old testnet do not carry over. Miners and pools should check that their node reports the new genesis hash before pointing hashrate at it:

curl -s -X POST http://127.0.0.1:8545 -H 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["0x0",false]}' | jq -r .result.hash

Assets

Platform File
Linux x86-64 krnxd-v1.0.1-testnet.1-linux-amd64.tar.gz
Linux ARM64 krnxd-v1.0.1-testnet.1-linux-arm64.tar.gz
macOS Apple Silicon krnxd-v1.0.1-testnet.1-darwin-arm64.tar.gz
macOS Intel krnxd-v1.0.1-testnet.1-darwin-amd64.tar.gz
Windows x86-64 krnxd-v1.0.1-testnet.1-windows-amd64.zip

Docker: ghcr.io/kronexnetwork/krnxd:v1.0.1-testnet.1 (also :testnet), for linux/amd64 and linux/arm64.

Verify with sha256sum --check --ignore-missing SHA256SUMS (shasum -a 256 on macOS). The macOS binaries are not notarized: run xattr -d com.apple.quarantine ./krnxd once if the archive came through a browser.

Build

  • Go 1.26.8, CGO_ENABLED=0, -trimpath. Linux binaries are static.
  • Source commit b925e895de848348029d460e4f29a3f012c85a0b; krnxd version prints it.
  • The node reports 1.0.1-stable as its client version.
Loading