Developers — Build on Chakram

01 Why Build Here

Fast. Familiar.
Final.

Three properties that matter most — built in from the start, not bolted on.

~1s

block time

Instant Finality

CometBFT BFT rounds produce a new block every ~1 second. Once >⅔ of validators sign it, it's final — permanently. No reorgs, no confirmation waits.

EVM

fully compatible

Your Toolchain, Unchanged

go-ethereum v1.17 processes every transaction identically to Ethereum. Same opcodes, same gas rules, same precompiles.

Hardhat Foundry viem ethers.js MetaMask

0

reorgs, ever

Deterministic Settlement

PBFT-style consensus means every committed block is irreversible. Build payment flows, DEX logic, or anything that requires confirmed state — no extra safety margins needed.

02 Chain ID

1164

0x48C

One number your wallet needs. Add Chakram once and every dApp on the network is a click away — same addresses, same keys, CHK for gas.

03 Network Details

The spec sheet.

Everything a wallet, client, or deploy script needs. Copy any line or take the full wallet_addEthereumChain JSON.

01 · Connect

Network Chakram

Chain ID 1164 0x48C

RPC URL rpc.chakram.one

Currency CHK · 18 decimals

Block Explorer explorer.chakram.one

02 · Runtime

VM EVM (go-ethereum v1.17, unmodified)

Consensus CometBFT v0.40 · PBFT-style BFT

Block time ~1 second

Finality Instant · single-block

Genesis chakram

Block reward 5 CHK · halving schedule

wallet_addEthereumChain

{
  "chainId": "0x48C",
  "chainName": "Chakram",
  "nativeCurrency": {
    "name": "Chakram",
    "symbol": "CHK",
    "decimals": 18
  },
  "rpcUrls": [ "https://rpc.chakram.one" ],
  "blockExplorerUrls": [ "https://explorer.chakram.one" ]
}

04 Your Toolchain

Unchanged.

Chakram runs unmodified go-ethereum. The only thing that changes is the network entry.

01

Add Chakram to your wallet

Chain ID 1164 — one click above, or manually in MetaMask / any EVM wallet.

02

Point your toolchain at the RPC

Paste the config for the tool you already use — see the snippets below.

03

Deploy and see it final

Your contract shows up on the explorer about one block later — final, irreversible.

hardhat.config.ts

// hardhat.config.ts import type { HardhatUserConfig } from "hardhat/config"; const config: HardhatUserConfig = { solidity: "0.8.24", networks: { chakram: { url: "https://rpc.chakram.one", chainId: 1164, accounts: [process.env.DEPLOYER_KEY!], }, }, }; export default config;

05 Live Chain

Talk to the chain.

The public RPC answers anyone — this page included. Watch the height roll, then send a request yourself.

RPC Playground · rpc.chakram.one

JSON-RPC 2.0

Request · curl

curl -s -X POST https://rpc.chakram.one \ -H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

Response

Click Send to query the live chain →

06 FAQ

Asked.
Answered.

Is Chakram EVM-compatible?

Yes. Chakram runs go-ethereum v1.17 as its execution layer — unmodified. Solidity contracts, Hardhat, Foundry, viem, ethers.js, and wallets such as MetaMask work exactly as they do on Ethereum. No code changes are required.

What are the chain ID and RPC?

Chain ID: 1164 (hex 0x48C). Public RPC: https://rpc.chakram.one. No API key required.

How fast is finality?

Single-block finality, roughly every second. CometBFT's PBFT-style consensus requires >⅔ of validators to sign a block before it is committed. Once committed, the block is irreversible — there are no reorgs on Chakram, ever.

How do I add Chakram to MetaMask?

Click Add Chakram to wallet anywhere on this page — it calls wallet_addEthereumChain and fills in all the details automatically. Alternatively, add it manually: Network name Chakram, RPC URL https://rpc.chakram.one, Chain ID 1164, symbol CHK.

Can I deploy OpenZeppelin contracts?

Yes, without changes. ERC-20, ERC-721, ERC-1155, Governor, Ownable — everything from the OpenZeppelin Contracts library works as-is. The EVM and its opcode set are identical to Ethereum's.

Is there a CHK faucet?

A public faucet is coming. In the meantime, the node dashboard at node.chakram.one — Wallet tab → Faucet — can dispense CHK. You can also reach out to the Chakram team on GitHub to request CHK directly.

Where can I verify contracts?

The block explorer at explorer.chakram.one has built-in contract verification. Navigate to the contract address → Contract tab → submit source code, compiler version, and optimizer settings.

Is Chakram a Layer 2?

No. Chakram is a sovereign Layer 1 blockchain. It is not built on Ethereum, Avalanche, or any other base chain. CometBFT provides its own BFT consensus; go-ethereum provides EVM execution. The network is fully independent.

07 Resources