BKCPost-quantum accounts. Ordinary Solidity.

A Cosmos SDK chain whose accounts sign with ML-DSA-65 (FIPS 204), running an EVM over those same accounts.

Lattice keys, not ECDSA

Every account and every validator signs with ML-DSA-65. There is no secp256k1 key anywhere in the chain's custody path, so a future quantum computer has nothing to break.

The EVM you already know

Solidity, Hardhat, ethers, Blockscout. Reads are standard Ethereum JSON-RPC; writes travel as a signed Cosmos message and come back with an ordinary Ethereum hash, receipt and logs.

One account, two spellings

bkc1… and 0x… are the same 20 bytes. Balances, contracts and the explorer all agree on who owns what.

Tooling that hides the difference

@bkc-network-lib/sdk gives you an ethers Signer; @bkc-network-lib/hardhat makes hardhat run, test, ignition and verify work unchanged.

Testnet at a glance


Cosmos chain ID	`bkc-testnet`
EVM chain ID	`262144` (`0x40000`)
Native token	`BKC` (base denom `bkc`, 18 decimals)
EVM JSON-RPC	`https://rpc.bkc.network`
EVM WebSocket	`wss://ws.bkc.network`
CometBFT RPC	`https://comet-rpc.bkc.network`
Cosmos REST	`https://api.bkc.network`
Cosmos gRPC	`grpc.bkc.network:443` (TLS)
Explorer	explorer.bkc.network
Faucet	faucet.bkc.network — 1 BKC per address per 24 h

Testnet

The testnet is unaudited and is reset from time to time. Balances, contracts and history do not survive a reset. Do not hold value on it.