Chakram combines CometBFT BFT consensus with go-ethereum execution. Sub-second finality, full EVM compatibility, permissionless validators — no waiting, no reorgs.
Chakram is a permissionless Layer 1 blockchain that separates consensus from execution. CometBFT handles validator coordination and instant BFT finality; go-ethereum handles smart contracts and EVM execution.
Once a block is committed by >⅔ of validators, it is final — forever. No probabilistic finality, no long confirmation waits, no chain reorgs. Your transactions are either in or out, within one second.
Transactions are finalized in <1 second by CometBFT BFT consensus — no reorgs, no waiting for confirmations.
Deploy any Ethereum smart contract as-is. MetaMask, Hardhat, Foundry, ethers.js — all work without changes.
Anyone can stake CHK and join the validator set. No gatekeeping, no whitelists — pure on-chain governance.
Validator registration, delegation, rewards, and slashing are governed by a transparent smart contract — no off-chain trust.
A clean separation between consensus and execution gives Chakram both the security of BFT finality and the flexibility of a full EVM.
CometBFT v0.40 runs PBFT-style BFT rounds. >⅔ weighted stake must sign a block before it's committed. One missed round → timeout, next proposer takes over.
go-ethereum v1.17 processes every EVM transaction identically to Ethereum. The same opcodes, same precompiles, same gas rules — just different consensus underneath.
CometBFT talks to geth via the same Engine API that Ethereum's beacon chain uses: engine_forkchoiceUpdated + engine_newPayload.
A Solidity smart contract on-chain governs the entire validator lifecycle: registration, delegation, reward distribution, and slashing — fully transparent.
CometBFT's timeout-driven rounds produce blocks in ~1 second under normal conditions — fast enough for real-time applications.
Once committed, a block cannot be reversed. No waiting for 12 or 32 confirmation blocks. Your users see instant settlement.
Use every Ethereum tool you already know — Hardhat, Foundry, Remix, MetaMask, OpenZeppelin. Zero friction deployment.
Validator admission, parameter changes, and upgrades are decided by stake-weighted on-chain votes. No foundation veto.
Auto-permissionless after launch: stake the minimum, submit a transaction, start validating. No application process.
Misbehaving validators lose stake automatically. Double-sign or stay offline too long and the protocol enforces the penalty.
Token holders can delegate CHK to validators and earn a share of block rewards. Liquid delegation with commission control.
Each validator registers a name, website, description, and commission rate on-chain — discoverable by any delegator.
PBFT-style BFT consensus means the chain never forks after block finalization. Applications can trust the first confirmation.
Anyone can run a Chakram validator. All you need is a server, some CHK, and a few commands. The network is open.
Any Linux VPS with 4 vCPU, 8 GB RAM, and 100 GB SSD. GCP, AWS, Hetzner — your choice. Open ports 26656 (P2P) and 30303 (geth).
Clone the repo and run ./scripts/deploy.sh --mode fullnode --reward-addr 0x…. The script installs Docker, builds the node, and launches consensus + execution.
Your node fetches blocks from peers until it reaches the current head. Monitor sync via /api/status.
Call registerValidator() on the StakingRegistry contract with your validator key, commission rate, and stake. That's it — you're validating.
Ready to start? The full setup guide walks through every step.
Read Deployment DocsCHK is the native utility token powering staking, governance, and gas fees on Chakram.
| Era | Years | Block Reward | Est. CHK Issued |
|---|---|---|---|
| Era 1 | 2025–2029 | 5 CHK | ~4,200,000 |
| Era 2 | 2029–2033 | 2.5 CHK | ~2,100,000 |
| Era 3 | 2033–2037 | 1.25 CHK | ~1,050,000 |
| Era 4+ | 2037+ | Halvings… | Converging to 21M |