Live Chain ID 1164

The chain built for Speed & Finality.

Chakram combines CometBFT BFT consensus with go-ethereum execution. Instant deterministic finality, full EVM compatibility — no reorgs, no waiting for confirmations.

Block — — Validators ~1s Block Time CometBFT + go-ethereum

01 Live Network

Settled in under 1 second.

Every number on this page comes straight from the network as it runs. A new block arrives roughly every second, and once it's committed by >⅔ of validators it cannot be reversed. There's nothing extra to wait for.

Watch it on the explorer

Live · Block height

—

Blocks settled since chakram launched. The count climbs by one roughly every second.

—
Active Validators
~1s
Block Time
—
Total Transactions
1164
Chain ID
● Live
Network Status

02 What is Chakram

A New Kind of
EVM Blockchain

Chakram is a Layer 1 blockchain that cleanly separates consensus from execution. CometBFT v0.40 handles validator coordination and instant BFT finality; go-ethereum v1.17 handles smart contracts and EVM execution.

Once a block is committed by >⅔ of active validators, it is final — forever. No probabilistic finality, no long confirmation waits, no chain reorgs. Your transactions are either in or out, within seconds.

View on GitHub
⚡

Instant Finality

Transactions are finalized in <1 second by CometBFT BFT consensus — no reorgs, no waiting for confirmations.

🔗

Full EVM Compatibility

Deploy any Ethereum smart contract as-is. MetaMask, Hardhat, Foundry, ethers.js — all work without changes.

🌐

Graduated Validator Set

Starts with a permissioned whitelist, then automatically opens to anyone once the network reaches 20 validators, 548 days uptime, or a 66% governance vote.

🔒

On-Chain Staking Registry

Validator registration, stake management, rewards, and slashing are governed by a transparent Solidity contract — no off-chain trust required.

03 Architecture

How Chakram Works

A clean separation between consensus and execution gives Chakram both the security of BFT finality and the flexibility of a full EVM.

Clients & dApps
MetaMask · Hardhat · ethers.js · viem
JSON-RPC
go-ethereum v1.17
EVM Execution Layer
Execution
Engine API · JWT Auth
CometBFT v0.40
BFT Consensus Layer
Consensus
Validator Network
>⅔ of validators sign to finalize
P2P
01

Consensus

CometBFT v0.40 runs PBFT-style BFT rounds. >⅔ of active validators must sign a block before it's committed. One missed round → timeout, next proposer takes over.

02

Execution

go-ethereum v1.17 processes every EVM transaction identically to Ethereum. The same opcodes, precompiles, and gas rules — just different consensus underneath.

03

Engine API

CometBFT drives geth via engine_forkchoiceUpdatedV3 + engine_newPayloadV3 — the same bridge Ethereum uses. JWT-authenticated over localhost.

04

Staking Registry

A Solidity smart contract governs the full validator lifecycle: registration, stake, reward routing, and slashing — entirely on-chain and verifiable.

04 Why Chakram

Built for Real Apps

The properties that matter most — speed, finality, and compatibility — built in from the start, not bolted on.

~1s

Sub-Second Blocks

CometBFT's timeout-driven rounds produce a new block roughly every second under normal conditions — fast enough for real-time applications and instant UX.

Live
0
reorgs, ever

Instant BFT Finality

Once >⅔ of validators sign a block it's final — permanently. No waiting for 12 or 32 confirmations. No chain reorgs. Your users see settlement happen in real time.

PBFT-style consensus
EVM
fully compatible

Drop-In for Ethereum

Point Hardhat, Foundry, or viem at the RPC and deploy contracts you already have. MetaMask, OpenZeppelin, ethers.js — everything works without a single change.

Chain ID 1164
⚖️

Proportional Voting Power

1 CHK staked = 1 unit of CometBFT voting power. Your influence over consensus is exactly proportional to your stake, capped at 100,000 CHK per validator to prevent any single node from dominating.

🏷️

Validator Identity

Validators register a name, institution type (university, company, government, etc.), and website on-chain. Identity is fully optional, stored on the staking contract, and readable by any dApp without trust.

🔄

Auto State Sync & Recovery

On first run the node downloads a chain snapshot so you sync to the tip in seconds, not days. If a node falls more than 500 blocks behind it auto-wipes and resyncs — no manual intervention needed.

📜

Validator Set Governance

Stake-weighted on-chain vote to open the validator set — 66% quorum, 7-day voting window, 30-day cooldown between proposals.

🌐

Permissionless Transition

Validator set opens automatically once 548 days elapse, 20 active validators are reached, or a 66% governance vote passes.

📊

Slashing & Jailing

Misbehaving validators are slashed and jailed by the ABCI layer. Configurable burn percentage; jailed validators must unjail to re-enter.

💎

Delegation Registry Planned

CHK holders will delegate to validators and earn commission-adjusted rewards. Commission rates (0–100%) are already stored on-chain.

🔑

Validator Metadata

Each validator registers a name, website, and commission rate on-chain — readable by any smart contract or front-end without trust.

🔒

On-Chain Staking Registry

All validator registration, stake management, reward routing, and slashing are governed by a transparent Solidity contract — no off-chain trust required.

05 Run a Node

Become a Validator

A single binary — no Docker, no installer. Works on Windows, Mac, Linux, or any VPS. Up and running in under a minute.

02

Run it

# Linux / macOS chmod +x chakram-node && ./chakram-node
# Windows (PowerShell) .\chakram-node.exe
On first run it downloads geth, fetches genesis, generates your validator keys, and opens the dashboard at localhost:8080 — fully automatic.
03

Get your wallet address

Your node generates a unique EVM wallet on first run. Print it with:

chakram-node wallet

This prints your address and private key. Keep the private key safe — it signs your staking transactions.

04

Apply for whitelist

During the permissioned phase, the Chakram Foundation must whitelist your EVM address before you can register. Send your address to the team — once added, the Staking tab at localhost:8080 will automatically show the registration form.

The dashboard polls whitelist status every 10 seconds — no manual refresh needed.
05

Register as a validator

Once whitelisted, stake CHK and register. Two ways:

Dashboard Staking tab at localhost:8080
CLI chakram-node register --stake 1
Min stake 1 CHK
Reward 5 CHK per block

Become a seed node

Seed nodes are well-known entry points that help new validators discover the network. If you run on a VPS with a static IP, consider registering — it strengthens the network for everyone.

Optional · Servers only
1

Get your node addresses

Open your dashboard → Node Info. Copy your Geth Enode and CometBFT Peer addresses.

2

Publish a DNS seed

Add TXT records to any domain you control (e.g. seeds.yourorg.com):

geth=enode://PUBKEY@your-ip:30303 comet=NODEID@your-ip:26656 api=https://your-dashboard-url
3

Register with the network

Contact the Chakram team to add a link=seeds.yourorg.com TXT entry to seeds.chakram.one. Every new node will discover your seed automatically — no binary updates required.

06 Build on Chakram

Chain ID

1164

Standard EVM, no changes. Point Hardhat, Foundry, or viem at the RPC and deploy the contracts you already have. Add Chakram to your wallet in one click.

Developer docs

07 Bridge

BSC ↔ Chakram

Lock BNB or USDT on BSC, receive wrapped tokens on Chakram — instantly and bidirectionally. An off-chain relayer watches for on-chain events and submits the cross-chain proof within ~30 seconds. No custodians, no wrapped tokens stored off-chain.

BNB ↔ wBNB USDT ↔ wUSDT ~30s settlement

08 CHK Token

Tokenomics

CHK is the native utility token powering staking, governance, and gas fees on Chakram.

Emission Model
Halving
Schedule
No pre-mine. All CHK is emitted purely as block rewards. Reward halves every 8,409,600 blocks with a permanent 0.3 CHK tail emission floor — no hard supply cap.
Block Reward
5 CHK
Paid in full to the block proposer via Engine API withdrawal. Halves every ~8.4M blocks; never drops below the 0.3 CHK tail emission floor.
Use Cases
Gas · Staking
Governance
CHK pays for EVM transaction fees, secures the network via validator staking, and participates in on-chain governance votes.
RPC Endpoint
rpc.chakram.one
Use this RPC in MetaMask or any EVM wallet to connect to Chakram. Chain ID: 1164, Symbol: CHK.
ChakramLocker
80 / 20
reward split
80% of every block reward is locked in the ChakramLocker contract (1-year cliff, 2-year linear vesting). 20% is paid immediately to the validator. Prevents early inflation dumps.
Era Block Range Block Reward CHK Issued in Era
Era 1 1 – 8,409,600 5 CHK ~42,048,000
Era 2 8,409,601 – 16,819,200 2.5 CHK ~21,024,000
Era 3 16,819,201 – 25,228,800 1.25 CHK ~10,512,000
Era 4+ Continues… Halvings to 0.3 CHK floor Tail emission forever

09 Roadmap

What's Next

Phase 1 · Done
Core Protocol
  • CometBFT + geth integration
  • Engine API bridge
  • Genesis tooling
  • Docker Compose stack
  • chakram-node standalone binary
✓ Complete
Phase 2 · Done
Staking & Validators
  • StakingRegistry.sol contract
  • Permissioned validator whitelist
  • Proportional voting power (1 CHK = 1 power)
  • Validator power cap (100,000 CHK)
  • Slashing & jailing logic
  • Validator identity & metadata on-chain
  • Governance vote to open validator set
✓ Complete
Phase 3 · Done
Ecosystem & Infrastructure
  • Multi-validator network (chakram)
  • Node dashboard (node.chakram.one)
  • Public RPC (rpc.chakram.one)
  • Block explorer (explorer.chakram.one)
  • Auto state-sync & crash recovery
  • Developer documentation
  • BSC ↔ Chakram bridge (bridge.chakram.one)
  • ChakramLocker — 80/20 vested reward split
✓ Complete
Phase 4 · Now
Delegation & Growth
  • CHK faucet
  • DelegationRegistry contract
  • CHK holder delegation & yield
  • Permissionless validator set
  • DEX / AMM on Chakram
  • Ethereum bridge
  • Ecosystem grants
→ In Progress

Start Building on Chakram

Deploy your contracts, run a validator, or just explore the chain. The network is live and open to everyone.

GitHub → Bridge ↗ Explorer